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
- 9b5d69e3abe33ba6ab1d0afbab9c6c8db60b12e48d2cf1485f51122f1387198b
- request
- defeb32280451b25b98fb37b0a6a9121194485ae1a90524ca57199004451fe4e
- transaction
- 3cc0952632a6e6253f91073a935a6cbcf5926517a5adbacc1b3f77c24642243bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63369
the chainentry 63369
- sealed to the entry before
- ed1ef9d81d8cbb977829b827755005b47be0e8f14868289bcbef13aa97fc08d6
- this leaf
- e06568aa4030773408dcf6e983acb015920a33091aa32dbf8eb386c4e9b05ba3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PKAir0KsjuRm1VdhpSu9SJLJLx2NyAVXu4hDL8zvIPVXp1eiXrhwXnl99MeQMeQb1A7fbmdJ2O6O9IFLt/J1Dg==