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
- 41d1e0bceee1f757e3367d03acf7ac34c87e59552648967a29544ecd22fd5517
- request
- 2fcc0f735662f7d54eac7fed5090688b8bdd70149a527538b82ee6e92fc1c86b
- transaction
- 934ba7c84195f8193bd2790f65b31b32ebcd0ae55aa4bff13e2dce9892d65807computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21373
the chainentry 21373
- sealed to the entry before
- c12fc1085fe28d7e4dcff95498c1cde9ea27ac718a635df56b5c292941b19802
- this leaf
- 9065b04ba8be960c4da7ee3a5fbd6cba3b18be9dd22a0dc79efb87046af451c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aZvXg7NUsFuKbfhWqCokhEEqt4cY8yCC8NC2FpsYj2yoV1/DYeusTvaPyRYHFMGQDgLHTJgDkawCn+elw2uACA==