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
- be92d23e5115731b0d16251511b3fb65525219a7bbb95eaabe8dc106ef066c26
- request
- c7f681a113a711102183e4761f5802c6eab2f3c8952c244fb55a2495c78041fc
- transaction
- 4befc9009e14d213dfdcec9d409a3dd80a6751323621a25ae8603ebc0b29973dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30917
the chainentry 30917
- sealed to the entry before
- 9e8c6d1c6839301a0851ac3b3ccd09121489247eb760d4c75ec335e37240df20
- this leaf
- 44f76ed72b7cb3f4ddeac78a91d9da9581ea6e7d37fc4b3f314a936d38546511
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bmCTXjdF8pozdQndcQLSKh8hOY8VB0Cnobc0kpD/A0XP5GGepxL83D0Q0Q65KRoKLrHrFHh3oQtINEUGIDdKCA==