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
- 9563571967c86abc6631193cb01bfc298e61508f4d1c561867ccf38902cac3f7
- request
- d97d2e2706bc47e084f691da487945ad622d0b24455a4e4ed940b14d05198017
- transaction
- b36cf9c4fa7eed2a4dd4b851be31d834da8177f824b753e18f78ad0f97fc4b01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60164
the chainentry 60164
- sealed to the entry before
- d89100bd1b6a07a881c4296c31a36fb7be49afae50c73c39323e0bf0653ccef5
- this leaf
- 609c9e29fe7ab6d6061450776c2677c78382420c7d4b9f76c031005175eeeda6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VH0Z5frjQIjc5Z5fbwkRkkshco+DyGA+OBxD9v6syBC1wC+ayLefSBtFEN66stCYil7LGZyN8g2dIDM1JS7JDQ==