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
- 1a53df7bed3515ead621744df2351a0fb9d990418dd9b7c0676ae3444674bcbe
- request
- 0e2b98e54ac6dbcd4ac9a8a69343cac1409f67088cf9e82cd32d7943025919ee
- transaction
- 300950d90458322925ba7fcc77b564a24034d06bac1384ff4a285a05640ed41ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27844
the chainentry 27844
- sealed to the entry before
- 0041b6470e7e0cc646e3c41bc0f08179c68ca796c74a68758fc9fd08857bd3a3
- this leaf
- fc95a122f08d50bdf274d2dae2e2219624c62d83c83bb622b01d3911d26ce0a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HG/qChscG1iWtJtBTDcVcyEewWcHeNPM6o+MUSNfHr3yifLJpqmKlfL4exUJhR4/Em17LxdAf6+epVSLgItyDg==