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
- adf3a0821d8c38fba148479635d63c900ee43a13452c64638af4653eee33cd5f
- request
- 7f58ea81c820b8bfb367778de3435b98f6ba6fda703f25f5a081a16ec9003db2
- transaction
- 2a9a65072ba91cd1beffb041139ec960465b5d4ba36100e8061b950d031a710bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32928
the chainentry 32928
- sealed to the entry before
- c3bc6629171904442e3eb3edd0b60e041778230dd99126e061a96971293ea2e5
- this leaf
- e323af800a3920e17f7afbf8c0c4ba86707bb1519674c9a15a89aeff24a17c5d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G1TznArA4zwt9GNDMkALlXM3ELzvfrJs+xaYFfWEGPh6xoITIDze8Pie47ISGZbtMr44uKOzp9yLVMUk8tXBBw==