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
- 4bb50c0f907f88810f54ec0afa50685163be75e8a2d513dd5eaa048afdcdd2bb
- request
- 38f15699ef026e80f581b175df54c2d78cdedd04578dded84fdd1f496af5951b
- transaction
- 6c712a6de29b56105b385505624a56fd079e9bc21186faaf4c7eee6c52884f19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39230
the chainentry 39230
- sealed to the entry before
- aeadc6408ea702bf72b07f64bfcf107fadd4c439d89ff5bc0f6c4527e3a085f0
- this leaf
- b71c9f28b8496460bb9770d0049984e5bd4859b8d04ab5ebcb5a2c4bcbdde66d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6uaDaO3hAGKf6QRwjwksy747So355wViWxna2sn5LecL2GI7VU/He6uCt3Ifi+qeUWTpKz8l9rG1t7xc9bF1Dw==