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
- a7173c6c1470044c690b34e538e83302f2da4b12ab76d476a1188b09388c8f57
- request
- ac86df7c0efbafb3c44b43557b4071f1a1907db0db2dc3c7bb6b8bf87238dcce
- transaction
- 56a73672e53842f2fb9061e653f2bcb15678228b2b0f6272a456f33a9337512ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37144
the chainentry 37144
- sealed to the entry before
- 8dd15e2560a1c09f8cf7f944acff29be1209b928b6fff3fbb8411e4c30c57763
- this leaf
- 8252e02f7df2f6e0441180f1343cbc6df1417281e01a4a9c69c1240445653ed9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JI883BgXol/bWHOq3iseMlkfJFCPctz9JHcbpqzVvaLqOEWT8ro9FUxmPtlOoHNM0vjsMvthtnwUsop+qryECQ==