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
- cea3ba0a7aa940585d03ad39118554aab44a02e70eb654f07de3b086a48d0eaf
- request
- 004029e99b61e0e59cafd05ae907f8288f243502b5b939d9b0fd9ab3e0d46116
- transaction
- 74f90188d1731c773a9bdc1b04da4d9d40814e2284332e185f30f85434f8b681computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33440
the chainentry 33440
- sealed to the entry before
- 2b029f677b8f987b341b76ce9428b92c27779d34580023c1cae31b981506c6d3
- this leaf
- 96326785ff5490b6b5bae4299f93b7b052f3725a8de7679014dcb8694a70e356
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vb1gPEFtm1H5opTmhyqJAFpSS3W8IkIXTJL8L/z4GCFIBucHewdcy9HZxDC7AnEjQqrEoLwrU3v3Szz5ZIFBCQ==