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
- 3aef2d8ac8bd1d9c905c19b39f23389ff614d9ec49eb6c312f3e68ffa186fb4b
- request
- 046e8cbf028d4fd7f33bea30dc36155a074666e8e96e487fb551810936ec2378
- transaction
- c940ae120ab511a7f2dcb163e951d2dff650afbe2335fa629725bf1f51887da4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46200
the chainentry 46200
- sealed to the entry before
- 98e2e3d5fa78d0f14707d0ce948504750a204afc1eb16db7cb69241bc2c2aadf
- this leaf
- 0e8ce536d3836d7d19ced93cddc0048b2cfdf45796d21c4c7d8236f1f3accb91
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VLbsDfL7AjLseUaT6R9+sR5Mz1CPK8h89HVQ/iQVMBTRJRQNSN3kuQRTxaBFbcVFfnTGsgkb38633V/NFcOSCQ==