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
- ad04d62ca1ef9a6aa66674718606a96e0d33180c68d58d91900f4999ccaf7312
- request
- 65d586f7e99799f29906491be489ba41dbf01a7e19c6e78074131028eb38ce07
- transaction
- 320d3419329ec4f661fd0d1157e8d9b74aeaaf4c5c11163aec6e49209e5d9cbfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27402
the chainentry 27402
- sealed to the entry before
- 3a93a48ea1f83bec687df98b3942c3dca5aa899c937990cd6f48144d5f9cbee4
- this leaf
- ac94935aced529cb6e710861461518cfd0b74802dd76cc911662e53fa12baf21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CeuUXrVJv9x8fa7lE+fKgW0s48CHrtr1p1qL1sG85hvLymd1YdFv4Q+Cb01qjQlKGgu4XN/DAAhJNlVTQNR9DQ==