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
- a0e8dfa8fd65ac441439879145e7221f50b3feee7a754d331356298038278843
- request
- 3963e4f79674df04cb68f85da3853a31b64c282c1c11c5277d2c3d2695deeb41
- transaction
- e34c6e396ce9c3c2385454f946b17bf47705c6211e029b2ceae6df1616351377computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 136
the chainentry 136
- sealed to the entry before
- ddd0f7fb8d597a8d895188dca586464a6733865186d2f798f473ca8806a0808d
- this leaf
- fea87a7f1895a021cc2784781b939dfdfbeff1fe5be4c1b342297616e1194d3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aQswc/zZUyaLn+oEHWF6O3knTxtqoaz8qlzyBKc5flQE43WEfhZghnWZvDGa7u94hO4uekBXZ8XFSIfXw2gUBg==