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
- 40345ce4eeb75ed817bfe0df4f5b789822500d7a12ff790c0b2f23a99c3e5a31
- request
- 24ae894b9a8f5fbe3570c1ea66ba690f763bf9051acc7b9bbdcb3fda7fac7837
- transaction
- 13ec44be91a1197762e483775eb9481cd872b27fa7ddab5b89aadaa43f2d1f73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33901
the chainentry 33901
- sealed to the entry before
- 1591f2c08844860c812fd6cd71072024d4f07473bf66a448d47f1bbac0bdc320
- this leaf
- 167082c45ffdd6d6c05d6bcf28883bccc759466abfbdfc71d2c0e9ffcd236086
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SQAX+8ndBmeRNFcjZyNaQ4tKj5txXNG7/H61TxSk3e7H+aYtu0ad3CDHyiTA3I1M/z1+WhsSEYow8JkD8h2ZCw==