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
- edb05790a0bf82dc88419c416b34ae9b8221b47e9f2d734ce63120f59ee0174e
- request
- 21a0c0169c3a5023635a9113c74fd3f016b13fbd5cad81f017ffb7452e4fabe1
- transaction
- 7baabac567ebf6f3a4b22931eb5f5ed5109693c1d6119d795c104f0755f76330computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50506
the chainentry 50506
- sealed to the entry before
- 497fdda4f9db1c6a1f5688ed9042eb3165cd1197587fe530a6acdab2dabc7f07
- this leaf
- ab7170e42be49151b2b486111fdcbcb88b11823ad6285108ae494ca07fe6ced3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Tq0PRN4FnEFXk9QxVxNwqFpFEjGzy55PkaOdbJlYBhYjfZIWyWhwRUgYTZuSADiazzptXc23xD3iM52Ux+djBQ==