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
- 436c3fcd81c8f3f8b56c590aabe44e4ebb73936fa30ca57329e99c0e4e31f590
- request
- 366adfbb96deb280ebc87b6663b1487b1c399486375504830d96853343d1268d
- transaction
- 584c083c181d416dd7cfdd013cf53c3c166be59b98ec46f310b632c7ab36bc0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21352
the chainentry 21352
- sealed to the entry before
- 6fe5279f53fa19543bb3a016d64b8e7bd1c1bdae633c480401f1e8a34ffdc0a3
- this leaf
- 5f1a31f359141f42ccbd100ebaf0efd098d8eb9b9bfb9978f5c62f671f917543
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 823sGFU1pD4ifkSntUhwBqrkYY7Vl0ns9tzF9mdyp1AsG/HTatEOoppb4SmhkmS5p+jHNMv+/FeB0MGhZzMyCw==