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
- b135dc7b711c5d2f9c5882db734255453a1b0e86d839567501844a8a25c6c1c1
- request
- 998b948f2e9a652ff66866fa9f87feea5f1d971af3d1b21cfe636e5ec642ff33
- transaction
- a514b8057b1c822104778069202684560e847acf1fd3d5d2de96b188bcbc6c8ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59999
the chainentry 59999
- sealed to the entry before
- 293b73bb9e6a8e3cafd0c18ff9b5d2ea495d30fa222c294f140a211ceaa49bfd
- this leaf
- a2c1737168efd22f211fc860dab301ef9972c9d5e11a6a289b3c556b42459cde
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2hQVMB6sSEcaKj/GYp0nke5DPtsYt8dS1CYzd0BzMfzzKaLJHPhN+rr1SJXHEpt92J0Zt89dUR9rTCfTmraKCA==