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
- f42cb37df8a46510d0b23b7d7894144756038d5e839ceb24b3c41ed2946aceba
- request
- f8a753198eff2de2fee238a147223da192e3e7b382de554267262133eb1ebe64
- transaction
- 1499de52e5a36578534aadfdeffdfee4c27c8a712ad58fed307008aa9ae06aa7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9321
the chainentry 9321
- sealed to the entry before
- 871293a1a775b9b2fbf2cc2131409340222c8c89deb7dad122b24eb0b201ffbb
- this leaf
- cb8fa39139dc8320ae626e0a426ee8e0df9e1a5a6f84aa9951b5e22be0c57e23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LN5yPbYeRD8gMRUAnDBwU0B48aLlIjUYNx28F4FR1rzC5mZvikFBOmve8GUPCqAurErw01AI7z9ri9ixuQ3ABw==