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
- f63ceaf33c381dd47714ca5394b814421aac5566ec16d1bab54f3e3978a64226
- request
- 0dd4bc039675b30c1185be9b0350aedff7a22073f8c087a352512c5096200e2d
- transaction
- 8cf351566aa6ee7678e6d311032f31341613a55d1f913ed9f80840ee646fa3f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54755
the chainentry 54755
- sealed to the entry before
- f26cb2fa00f421e004bfd854f86530e800f200044841538b6183e27876d98a6d
- this leaf
- 840c38cac66fae7def77a13596c1bcfba3a9ae0282eed204b87f7559f6c342da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lfKSLUY46uEOepDhdarvIBqzoKolbbXOppzfz+qCCEQD/qkewDp2bkM9XKSmtE5Z72nVw9EwwbOIR7sMtmD0AA==