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
- 9ac903377f3c42f812ed60536f1d0961028743ccca24b19dd9f0e2113e828d71
- request
- 2896e2ad6b3316e0391a2864143a7c96cb7047f609f46df5d2b69009ff18eac6
- transaction
- 11f40fc21e084f8f6e4925c7729ea9a6451958ad5c08dd676bf844f8d209369bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2505
the chainentry 2505
- sealed to the entry before
- d5e4f3a827297e71e5f2e6bca70dfe26115d15419f0c519364804de5689292b0
- this leaf
- 5164cb3b5b3b423d37adf4155ea0b02152f29f98fea787d6b554b7cade1b0155
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SwH2OfvcZ3bLJSZOIZnTShY3hEyR23PSjfy21PU+TNwjFqUko1GN8+NuZHQOrgHrC2H28F27n9Q8tcUdO8HkBw==