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
- b9248182d3cb26a3f2709ac63e412c5a52c9c92bebfaeeeba4718828c63a60a4
- request
- e0ac73ff0758b06e1406867609a8765244f2af3747b35de7ecc739d9d9bc4b2b
- transaction
- 28fbad3094999cd47713f57166465d4c856dc8b6642d34aff3075eb983293526computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25259
the chainentry 25259
- sealed to the entry before
- d2d9dd2d342f7421b1548959006f302e7593a07c2ee30aaed839885982f226e8
- this leaf
- a5e0a0fe4933568b71d89017a3c1945affad94abae28735feee65d99b0cfeb85
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rxYEmL0nI9Ly1fjpB/0XckZdDynKSc3AT4WV09TQ45pd38oorGJXHHdoGDmx0VsHft/TvYBtv8kMsYM2/AV/Ag==