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
- e322613a6257f36c252000f957ea23350d9aea4340d6408b8e4f4d5f3ef8a195
- request
- 479690bcbc2dd0053a61a23911e87c2608a92ba4ce6392b61877efb0eec12f99
- transaction
- 4abe1120f1270df69b7406746212da14a8485b8194edcf56b6f7735a50b98d56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54641
the chainentry 54641
- sealed to the entry before
- 1b204af009a3b16e8d7b2df4ff3d00e19ec8489077b16a43d95245594dae47a3
- this leaf
- 0c268294679487ead31994e85fa54eb171ce3244ef5dfdcd3a6f49fdd31752e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m4cXog5JC5qgtks0+lkeGVT0tGPchmCIiPT3i/p7wsk5KjsCFpqGkGQG7WrbRUUIjWGuq3oI3/F2fvxcg17PDg==