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
- ab10db112734077a18fa3848b9009de7ca5cb0bf06247befd39aade7a056859a
- request
- aff0db51a9d4ad2b728be4ac9813b8eeaf07cf13b9189d1e5167cb69ccb5c447
- transaction
- 4c4c112e0c3d0312abe61edfdd9e931f4d4504d511f93117a98766ebb33823dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11490
the chainentry 11490
- sealed to the entry before
- 6d3b06ee432de950dddd5f45185fc6ac2db1c196868a9ffa5759b5b1b0b29eb0
- this leaf
- 9868770adc4a83ccb19bda7c923eb8c8a686d3cafd3a44330db63b8cba803d7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2wfwEqwILj1OEUO8oj74H7k5EKnMt8fQeT13mmkJudh8ieC3k2XMGZPTGbsNwarkJGLzg3UNiUvdH6xyQTUMBQ==