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
- 2467b5f26be7867b944b949e143b1a46d8945d31207923a1f6e725e39309e8d8
- request
- b5408fc95ea76f2808851ae5b2a17d301272f3d63f0e30386c5fb94b6f8107cc
- transaction
- e34f11fa455d480199da8c78538f2a426764bc3679496c669e4e660c54655b62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44829
the chainentry 44829
- sealed to the entry before
- 5eb92731b3596298004ea72cbb1410f5f54cbe8ad4045b4ae3f446678e6bf414
- this leaf
- a1a9d6503d9b6605a2881009cfe8db63e804e5cadafa83a2ceb9bd397efbbac4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 28MT5Cg/UE4KkuhyQkcNITvZCttJv4pPxLZpCcwyHmGAD9g1eDk+c/ILFuITfdXivSlmb3+kEPR/0h8ZkaHKDw==