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
- 115158af820917aa113778afa591ad55ed98c276955c471abf88616dbb7bd467
- request
- cf6560a58633cdb415a58f3441a83a77e9cef09cdca6fcf1da149c649284d669
- transaction
- 90e48af28211033c369652072a9ec265b6eb26a911b24e9802140268b2be41abcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 998
the chainentry 998
- sealed to the entry before
- ab4db1f93461b5f079aba520e785548fafe672da115c4ef5e6058ace46fd0233
- this leaf
- 352b271dc4eb669da7b48df4ba6c79bce0e8985989be7c196c307ad79bd98959
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uZZkk67u03qs/oonC79fhYZCF5LoJcSGP3N/M58bco3aAI4ptyPohELZzofqy8bysbGBg57VGGh2dQ7sgWV4Ag==