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
- 3dea83229f6e4946047a9181e8d9e23852f5acce0480d359ba85ed0910046084
- request
- 556b46bd7628f83d592e89dab49c2c24461e8b88f4ecde9132b77694b5405e15
- transaction
- 7e057420fa7eabed696963ef953db980ba333f5c918d58a33bf5e25bc89fd1f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11636
the chainentry 11636
- sealed to the entry before
- 045765fe253d3bb6cf0d487e21b78f3b37414d99ea815ee138b1e32cf3cf54a7
- this leaf
- cf82de94985cf7d4b251c7569dc826ecc7ff44122fd5166653e02b57dc92291f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fXmtLq2meoOzrd/zcrqaTIX5wiyhvsb6+dnWRaWqBSSqiFSmBX9GKI+e1/byNYtoXuVRSgl7foJe11wAxvpYDw==