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
- 895174eb831e3f28202588f1d5fade0baa6127300d7de660a82af11a17906f76
- request
- 312538bc055dbe5815344202efa46d6ad8c904e14c35a58b913ec0fd948eb9be
- transaction
- b11b65b43776195c05fa3dc31750a0b70a418e4ed290bb19feaed297ded8baa5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64408
the chainentry 64408
- sealed to the entry before
- 8ef0d6e591d1168497f3bbd1541154b540928a027499c45bdf22299f5714de85
- this leaf
- f0b2bc4b4083005a0ab36f82470066fb727d9062baf6050e4407b663d7066228
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2zJtXeTR0R/DeI6llTWuhp5IBZggojDFSKyc7JCR/nWH3kA+LHLBqRd0ZU7X7ipXwXupnL05w6+eXmDIdVb2AQ==