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
- a148159a54d5f51dc17cbc653a3aafbea708ed194bfaf3761ccabc6619c512c1
- request
- 616b91c4867c2ac5dacfdd2e9776cde495a882a205b6f4cdeaa9496995ee3d6d
- transaction
- 0ae153a30404b7ca900a9d19a8576a8b3c71b8e77fa9f06933090f9094823c26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20697
the chainentry 20697
- sealed to the entry before
- 78d45c1df09e69cc57c4f9f5f05814e5fb6657822ee43163ae5e795d66e96e6b
- this leaf
- 8bcdcf78bce712964dda9f47c2361df49f96439f99365ce27793df1092e67ee0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U7xO6dgGF2+swu4jiTdi36exij69rnfJm67WLsvBuVezeOS8wZLIRBpNnUHf1Kevly02ergiX6jHPHv0PBb5Ag==