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
- bd978103133633e304359906588721c239786e9f3b62fdd1ab08f8f7e77a891f
- request
- 27aee8afe83d8b1813d72bb77fa7b2d2c8cf457298a6ef22c16d0897b0462885
- transaction
- be649db2db5fabed58c12a406564355c65f115896bc5e204b206ad8289fcd003computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47954
the chainentry 47954
- sealed to the entry before
- 730ba1a7407518aad23eba5cf82310f6db686d6a8f108f6a652906d839bb441c
- this leaf
- ec6349922ffec46996fd0c4cfbbc6cdffe0b18aecc62092e0f82b49011a57630
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fufCzTSB6OkT3cQaI3NLIMCVH+7RfJT1yMcqLF01/Gl3HQg1ELzBVN6H8TOd+cfePbqnGNTSYHc9CjuXxThuBQ==