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
- 9619831d87ad631bc56f98420a2b86dc1de019ea6f99ac4c3bb8304589c6e91f
- request
- 1bd0b24f79babd510a04029ea3c65e3172bcf614fdbbe60cc96da465dbb0b70f
- transaction
- 7beb3b5d42df4075451bcf31d56576590d39c770e844afc4c39e97593326b74fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30806
the chainentry 30806
- sealed to the entry before
- e8beba582cecaaccc388aa5b8e61b3e9c3eed39f0d7def9c1cee843bdbf185e5
- this leaf
- a65c0376bef394ac6a1bcc21d97bc035718afd52b89600e8da41fb2aa5fc227f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ef9kECTAoyQno/erOEujGkfKu3M90k+ZgfHzDYeUvIc3gaS8OAktmvblZBcMpb6sZVvhD9B29FOlpGXjFQLYAg==