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
- 37906bb874cc389f23269e32dcccb4f9c12df33115c2f35de6f6ff1e4139bbb0
- request
- 21e1620272638ed81249355c6f591762fd0e2411ca11564b074538ca50af578a
- transaction
- 4e7ccd9c99d63573164fa12b52e4199abc30c62c1623c7ded29dceaed0a6ae85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21228
the chainentry 21228
- sealed to the entry before
- 327f41599f08491810d62ad5028b76e829289a851402b38ca43595af2a0d6f51
- this leaf
- 470a895f432eb0df01b18804ed82ee9a9e2330d7faccdcedad390aaf741f5b13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- puBuSWeoWMUI5+ERDslW1IKu0jPg39SHDPj62aYjIp3yhgFCKT1eobu9+SRvAFAg9cCj+s5LFcOvvTJz97OpDg==