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
- d4b8987ffeb6cdd6f3ea16e293e8caac1e9a79b9d132bd3becbeb672859fa6de
- request
- aa369f8c0900975a2abb9a92b78a7aeace97440c664a94473761b02d42877a65
- transaction
- d808237622f3b94f15011d2bf4378a2a0e558faa80e58f31b3cd30a69a5bf5ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53327
the chainentry 53327
- sealed to the entry before
- d5e7f9525c88957e7272e61d2d4d17452480363a6e9396032d1949b6f899966e
- this leaf
- 478063762c2d963b35c975a0d055d4a02048b7a3288d142d41e2b9d078731b31
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0NYr5vNuP47Hy9kYsnAMwomxYlAAnQFCODLzA+LsGOuAxbe0DwfeaNYPV9yBUtgeEsxYAfCptZhvqg65ZqovBQ==