why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- c0703954a161c68815b4ae680ad249669b677a4e10d8c27a8fd2595a3a5ddbb9
- request
- 082ab0fee441bdcda4df0015e3599f8980348c71f54807ac24115c475ba84655
- transaction
- 82d9cb7c6aff2f6ddf102c6f602ea11bd17a1f645b48b922793ae28f884ebe00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65807
the chainentry 65807
- sealed to the entry before
- 782d7261c767f7a2b550e55f16bd2c4da8f6254d7f97cf090c459d777a72dfe7
- this leaf
- bb1d0ae7c46447290a2dbf9ed3dd761dccea041a3ed5a470b9b580f65b61b105
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bGZnHQ/ZSCISJJNx6FK8DDdixHj8UMzGaTb9A4NOlQR8FsII91tP2MrgH6BbIb5wu1A6evteE0gbsVGKpDcqCQ==