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
- e8db59cb22da52ffc16675a5f32a6ec216bbdd8b9721a9b53aff50f5d532bc9b
- request
- 83041325082009025005f888739e9f5686ae49fa7ff8776838bf81c41d9a6716
- transaction
- cfe297f3a25baa5a910bf3029979f87e646599c7ae54446b1811c6e119469398computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62869
the chainentry 62869
- sealed to the entry before
- 10c118d2278e9c02f94d980240744a1dafa0f6cec8425af3db0bf40a23fa9aa5
- this leaf
- 22bae0b870e0cafe1ac4a21ecf2eaf956482d4730f0f0ff8a1054c9219c923a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wEjA/cSB2PO1L6zZUx2+nW3MKNSmoEmnmpCJtbkv3tvSle3Je6Lk9ZtcCLZI5xunL10EEC8ciqCpKUWhFW/tAA==