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
- 65a066b9e673456fab3e72c3c62d86d1c1298838edf738dcf69bd287e9b3bc4b
- request
- a1101ca7513eb202da626a8687e09b4015d8050219a867dbeacf53d483a03c86
- transaction
- 3952068dc22a2d990e7f873fd4e45e1382d27f66ffe24bec55acf19d84ecb633computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66610
the chainentry 66610
- sealed to the entry before
- 297d04cec53dc33f24c89de94efbef0dd4d3732bd548e52e27591e6008a7a26b
- this leaf
- 806e5d816b848d91647ff364316de19c409eb7ff0be1f9278c49dcb6e6873624
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y5wiuYagchm48kgDXNNiFROeu8hl7CfZ4pPjRJ94uEp26BxtKAylGUiq86dlXwHUzwVAqxCizb4QIw1R4g+RCw==