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
- acaf9a0f583e8d1bd8cf33e0e08fcecf77b798fd370114db99f71c7e6d1c7f0d
- request
- d70ca230986ab9b972dc4af77b79b39b55ff782e5e7e5fd52ed5ba6fdd3bab9b
- transaction
- 12a3263d0e22df766beee9aa28d01ddab6d203e8cd5d9c17fd45cf68355b6649computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54464
the chainentry 54464
- sealed to the entry before
- e3106f488ba21a9e50bc89f5cc6abe78b4d526b04165179cbc606db86ed423c3
- this leaf
- d760f056047dce9ccaa06bfcc630d44c11d20134a02bb7ef1b4a404fd935e721
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- USWbgHds8COEJfPLriAzXiSutDCGmURAsekjlHRNCr5gQhrVUwUaARWWr1Nq1V0olTmOMJlpyZZenUqLL1MWAQ==