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
- 46d3e74e7930932fd4709becb7d7815d5825a44db2c7a4eafde1b58b00c013ee
- request
- ebf55c7911bafc4d424fe005bc277579147f01b527b4ba8cf0d24c8dfa400edc
- transaction
- 72b43898c35b8318ec9605d50d749c79cad50002d138e7e012d8588c91c26863computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9353
the chainentry 9353
- sealed to the entry before
- d6efb5e401e9b76faa73a7f50cd2ad78139fd640ace5dcc7ec9dccf3b6bf8783
- this leaf
- e196e719c276b6666fcd32565c336e2cc71e94874168266c30fefad181bd413a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LHrmEOJPuewn0XjwruhrTbiPLeexR6O9A+f4cdQwVVIz/5Qpq0iBntSFUWgWGGk1usUckZwmO32WPLHyDq1/AQ==