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
- 42b224307c19b5c926595f10f4565d79acff8ec27c845fa70161045067269870
- request
- 3fd9354594a155ac2490b70c6abccb7e277de656ee3f8149ba3f824772d24d68
- transaction
- d6e7f0bed564f4ade3ee4e703b438a455a435fc14e26eaf4866a068ac87030d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58442
the chainentry 58442
- sealed to the entry before
- 64e7515606d729a8c2c2c0a529e9e3cc605e8b18f90acf1f580afb56b520a47b
- this leaf
- 120936bdd2e7c8562a5bf32c519051bd153d2fa7217a84d3612f404d54807e7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t7k1wojcguBYtiycQcTV/eGaggGGMEs8+iXlxxail14CsNrrUqu6PseSRZ4TWw/uCCFH72O4KrMHasdnYwvgCw==