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
- 213f3ed6c24a4b64385e07fa31f45b3aeca2e6d6efb498bb46e8dd73f57ac8d0
- request
- c037fa6efad612505c621ac1f263a2cccd7359ce06a9567c216bd7eea84955ae
- transaction
- 7096e35407603aef6a5e0c7fffc352c238c2f85734388a5d694aadf1bf053001computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23022
the chainentry 23022
- sealed to the entry before
- a1d79290b342eeb204fbb18a31a136f74587327e4484622cd6f8c7cfc96de719
- this leaf
- 308b613082a2402b97defbf8906ced07c793a03af0d2c4f3c47ab22ccfaef734
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aLRY/9xHRfY4SoA2fNAmS2/dWUqnN8Zd1h341JBrT4xtCK3Imv+0r9ycxf17QMRVUBZzEoXbOYPC6I9ZLQTDCQ==