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
- 92bd24a33f4500609285884b86d1981e5bfa61405a6bf32432758b26ec64948b
- request
- 764c6e6effe9f0579d0873252851a44ec3b3cef4bcc4c30e536bc0aee9d47e25
- transaction
- a508065b97e4e058e8745caf8e8058bcadd739d2a4039f2c7299a0efdf2e2f68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1620
the chainentry 1620
- sealed to the entry before
- 5524ac7d63b3cc572e9ced3b9c93c9d38e9edb0418de8509665404975ddc11d1
- this leaf
- 1909a5492e5af20b9701c6f500d380b2d102e3797b1588d98842e495c0934871
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jACWpJfh2X4NNAtaBPUoISIMgYg25iisSbAVL8UhoM0EHSr92Q4VBVNYw1PC4FjKNWEV/f0sHYGI79kSOIOSAA==