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
- 7106a7f5bdbbe061209ea1356bf9f4590bd550918e6dc81fe90249e4ad7c5b1f
- request
- f7910214de8bcf1f4014e90027dfd8cd46e0f971aef4f1ebb96fc55c4b1b0ed4
- transaction
- b868acfd177dbc3f4c23bf3e3da60d05cb4373775646320ea4971ad7278f8bbbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40531
the chainentry 40531
- sealed to the entry before
- 047fde66002324853f23fdecfccbccff902f8a094b194fc82ad4e16a10055e56
- this leaf
- d5260c8126c64ed2498cca16e7d1f493fbf8845edfc51a3a793fa8a419f88ac5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3ma5bjXu3Hh44TNBUc1QGUwfMAwOUvY9HOrbzQw24aEaMcmmbpZJ91+VjbK7qlC46xaNMaeWXsxRWhUCXUPWCQ==