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
- ed2e66585ce7efa320bfa996708f44f9cc87e46d18200d1d935f975f42e41331
- request
- d3967f36287328424bfedd92faa726033992b3bf6fe32c4ba0ff2e7fd202788b
- transaction
- a88dbe6c8e0934ea63c8dbf509040ff8c9567493473fe2faa38cf88f63926e99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6810
the chainentry 6810
- sealed to the entry before
- 9aa88d99ac3a5aa489a4f748ebe3b7fb9d8362ef1bfc528fdb713c17cfb00aec
- this leaf
- 254377e1f3999eb15f968cac9bb5bf941548ee47bacaa6edca895ea4e484686e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1+hmC//fcKxjPK3W1xbPmspbpMuhub4EDQ0L79wBIrjk3o/F+1xZAd8RoMOQgIrROsgyTporBqYuXXEJ86ezCQ==