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
- d534aad9bea8c546ca20aa44cce067033e4ed42847b99025ed7d759b9a11dbd5
- request
- b5fda9883c6597385d8cfcc27587ee0055c13581230c926bc75666827869a5ca
- transaction
- 1d1f654b7f90e1e0a4d50e6dcba3640a60560dadee6cd6b1ef819b700565a781computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57406
the chainentry 57406
- sealed to the entry before
- 03f92b6b52ff8c2a646765ebfec29771109008e7eee268388d335ddee2fea393
- this leaf
- f99bacfaba59c2316d06a917fd9c5d1a53818d87421e6f5def0597971fe7881b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QzSeuNrZbQ7uUdtjEe7E1by7ohEH0SyjFqi29oL3s7skOIrSJLFiRy0Bb+XR/455l/0BHZiTtw4AjqoYY58fCA==