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
- 7849816196242176806dec4aa83356ecf0a00de04949a947a111049c5631a251
- request
- fa705e32bb282276c0df101b6e3b12cc9fd7a2ac969947cd8c5f6336c1a98979
- transaction
- cd217af97213f4928b645b94ea0185a4855d27b29ef3fa56a3004e3e96a6825dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29235
the chainentry 29235
- sealed to the entry before
- 09b6972a4f23d8619c9da045a05bd338d641453e8b9ce82fd885f268898e68d9
- this leaf
- ab45f54ae646771641986e339d5cb9ec02a28312c96599bd8b5158ed93222d23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4IOSra980S2RbTanPp9xDDR+Zbp8SyW8tNUs2Dp2Aw2/f62PhWACBRTpmJXqa7sCOBu84fkUjOW55OLJscSdDg==