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
- 1bed891cec4f344a34853836f4c0a184bd88cfeae89add35fff490366f5911ca
- request
- 89be2cfd7b54ff853a8a21cdbdd6af12cf1b6a5afe1530696d7234df94f3cd80
- transaction
- 928d7c950fc6ae318646a85177c4fae6d3cb524bfe26aaf6ef80760a13b8058ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 596
the chainentry 596
- sealed to the entry before
- f65c6e476a5ab32a34aba86d535ba77e43abae77da22ee21d9de1f3d8aa6f4f8
- this leaf
- a888ab09bfae27984255adde1217f8c596c1a20b416b90ff40950be40f938d0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yEUWAY2ZkEz+hZ89xkThNqMLVgr8IZ7ilFmgay9tCDw0Au1ilHDwgoFG7h5pZ87PYH/uB6ZPHjfBEyuposLtAA==