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
- 6fe7d09d534eea4f33e413c8970a5daca27e018e644d4f4afe6565a9912ae817
- request
- aa582faaefb5995c28f2652c59512e91851421597603e34b5c3823aba02ab9b4
- transaction
- 8134af59e164ba2b3982320bff0bd3ea67800a223ebda5c4df0e033e9deee5a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65764
the chainentry 65764
- sealed to the entry before
- fce1e70ac27d924364a51ed4dc28944d4be32facbea57760b758750da1ea6e1c
- this leaf
- 536643a0b9571b48d918ff751a87cbb83b718416c4ace32e46e727f5242cd559
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mv18GoBbo0lw5KILgcDcJtv+Yi6lyOxhjxqyfbaXSxmRsMPSmFUxK7Am6SrOxCMsKR15ZPhuUXPf4lSzi55CDg==