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
- 40e84fdcf3a5d0d3e084bc9f8f6ab2ae2024a9e24635e1086b9bf46c7101b19d
- request
- 92866b32127370417713c89e75015aaf22c74c8de34341df6ba64d8e2338aa48
- transaction
- e033cfb3abd147cdb80cea264a413974381b422faab9c41eb54a6a896999ecfdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70879
the chainentry 70879
- sealed to the entry before
- 38085604384e59fcafa51ff0e3dc9dba21c00f6ded16a3c95c6eb42f2f503863
- this leaf
- f7e7e9a44ae14b9d7846aa3bcf974ddbdd0205881f95ea240a9732d2b1cf6a71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IJTbkIINajuqBTXpjm5xpCSFVbaGqJGKlzjprVBsmMK9Vgi3ZNYmndk9mI0ekNsk+7s4dOwJdjkktYXPYZBxCw==