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
- ff84d6edd65f2fd36fb4f623b810d4320e8a602bcb6cfe7e6202687076d80c36
- request
- 7c0bf005647c1faa09b63e0d139a3b507222d08cfae87fd8c56390181622c6e3
- transaction
- 55fcedde68fb666e05730fda6a51c2fa702ec8caf60054f830f08c26a64186d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49060
the chainentry 49060
- sealed to the entry before
- 7880dd13417f889f0ee9f9fdab785fab44d665c792eeebe3dad9e45ada3291e2
- this leaf
- 4eec0a14eade9e068b063c6491461412c9e86d6dfed94680083e493728e7cf80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hRaGW9/M7MAdB66oIRuxN8dIsa3oppSMI/i86Tpr5+G5MR815Q+nOpWb4k85o6y9L2ozdQGSG3GJ4VZ3CU+tDA==