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
- b24004568881f7da0b84c907975a307c0292d28b05d7a75fe1565720774a68ad
- request
- 12e94810c5888caf9979c122f74c6291ee643b6c063e4e8cfc14ba90e61811aa
- transaction
- 4d0d3ea7ceb9e1bde5965b8cb18834e431fb898629031c290087f2a379333c8fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64201
the chainentry 64201
- sealed to the entry before
- e68e2cda403a03603fc3f031276bd999430828745b5b48184ad61f49f4b395a7
- this leaf
- 2c7ea629c8a6d989704f7f890593d166a8ff5eca6f360d9bf866f972e062bb2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TwwJmn+Y/lScIZ+P49uiEn5Gd1Wtua2pWy11qaVOl50TeUnDYvNCc6sMW0fIXEv5jFzyQKTYAtjMB9SLt0ChAA==