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
- acf9f86dc3010067aac6f3ceccf7c406384bfeb4e3ae75a8be878fb6b7ad9e6f
- request
- 9948492ac0bc9f3a296588a271a15d4204a407fb08c1b185c1da5c42fe9e22f0
- transaction
- 93d430fffac7f2fe07021b609e1e4c82d26c5a3978c603b09f1a93da7a335c9fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 922
the chainentry 922
- sealed to the entry before
- a12ffb7e09f99ebbfd94406623520a3b2c2ac830509311c90d49cf976e8a068c
- this leaf
- 90d7f44d7a485f4469704af08e84d9acca946dbf2ac44cfce8a829f61d8b7e18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BMld66vzOsLVrRDDxl5ygfwFRRhV4J/1lAJJgNQ2dfjwumgiw23cDyU0xjb4Gcb44Hefh81Lu3nMEtrtnedUAQ==