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
- 1aaa6f2d2b43487db65e5c80fda10b8de596606f2707460ffebc2ec51d0edfd0
- request
- d81a0bf3312ddff16d4a00a1ac981f94b0f0a0aae4d1dd1c66bf6ed47c3ee683
- transaction
- 472712ed3530c03972f64253a64543804ef8321228f91a4a2a9517f5712d18ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69383
the chainentry 69383
- sealed to the entry before
- be83f6b20cc4a19cb58fb50c375aadc494a1d813c22ee63ee5d581e08706e44e
- this leaf
- 3392800efa94ef03c7e9a03c909dc68ac6dc7c84ca62367ccb7b674078069413
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xBPRhZfRN2AljK45svxmkKS19tzytKxHm1BTRAerkjgTdacYr3NfJr33WgECt+2/cbCZP3Bpix8ZePCkVoAPDA==