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
- 3ac3304485abc2804ce5cef0661370a1952fc7f871161d6f0f546c5c2d93f610
- request
- c6bd8e957958ed44741b73f675894675af080b5861c8c4f24810b329b00ed358
- transaction
- e663d86c408b1b88a60374313c651ff4a597a4b9740f4a7be1b1c9455a7ab9decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4311
the chainentry 4311
- sealed to the entry before
- 104351fd3d71afbc9a737b2e1452ad0d7a56d7ffd4410337abf5b8637cec9ce9
- this leaf
- c71d5ca7949766f298b7baf7268c0a618686e3c51ed51242159cdaa9a1e3cb99
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Auyn8A+Bq002cb5yEF474ANvpg9R95U9JzgJCMeYpKpQYedlmWsvzGptu/lem6D2a7jFl0PVyW40/DmM3x+nCA==