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
- b32507660af952aedfeb964e040adc13a736643acc7efaea33ce753117e642e0
- request
- bd7e41634b1797820493706dcd3d53f17caa610f4de770e7152f225cf659dcc4
- transaction
- b6e86679bfa3847d9eb3dbc325853df51e769dd92cc4cd0281ec6f3297092627computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36149
the chainentry 36149
- sealed to the entry before
- fb5f907d1b0608186f66203da4c53940c87b555494753181a28e7cc5d8b700b4
- this leaf
- 285bd7a7e9f5ba4d4ca18956ae8f3019ad33d802076d80e85bdf3e6def7ae4e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- caGLI3h0ifJ07/7KwEWaXj01++Npv/FHgbPQTNnGYDR7eIiRQfOJy0qXvngN+X7fAKO3IxeT3HhpT6mJ+WJACQ==