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
- f689f051a963b89d5b25fc76fc15c7cc2e9520b6febf87f9cd5d8c3a38017615
- request
- 28f38f383edfb6e8867c3b203c32bd440e20c34b3cea9dd55a60674614e7ca9a
- transaction
- e668621e7950ab17b96a35ad49a8c3f13682745c0d7450cd580c10e6abdb8946computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9713
the chainentry 9713
- sealed to the entry before
- b69507dc84af059d89528ee1306fa318a88e520735f6f493eb18c040f416c47c
- this leaf
- 3d47f022dada394d1a84d51c7165c6e4f0e38778310bac6ba104f9790608e142
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fHJgzv6MS125CsRfupB2nCvgIDM3iNdlfZ003FySGlX+iGXrXo9hMqz+bhYewNfrsHj+YeVa06kbwP17d1JYAQ==