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
- e93682691bb0f2aca55243893a3c136e0b49fd149b7e8c4948f8abf2c989d08b
- request
- a8ee0188c372794364dcc69dd1daaa04a3cdeca4c77959cb5be2fae135436f8a
- transaction
- b0e54e5616818cd235d8cb80035966e2ef514100c040e78ea6387ae47ffd9d64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47475
the chainentry 47475
- sealed to the entry before
- 884a08f89bb7bc67eaef665762aea0b97459506066c58f88fc194faaa9094645
- this leaf
- 4232f271899467021a8a21c4b8bde97ec63a803b31433e1d4dded80fd295d9f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a0oLnBb8hICYr3Ig/Afld/zx3uHF6DaZBhUJjTndhXXzSxAApp1nzNXy4tBYYqymagL7yBxCdiMYyrVXVpG2Aw==