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
- 4fd1470258be0e9e44efd1da38300bb6f686139f9ce5988951bd411292a2e483
- request
- 5ccf1c12a89dfaa229d8d9b3d7e90fc24014810a26be005a309a359cb9e75828
- transaction
- 6eee04bacb8ba580608e60e3ccebe5e0a3d87f50f7ba0558837a35260b22805dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28222
the chainentry 28222
- sealed to the entry before
- df2fe6fb0494d9cbea08b21ca9413effe12ed538e201a07746311c9ebe16381b
- this leaf
- d277d4d4b80ab037408840e94cd4f8528e71bd6c20e7eb14cba85d5af62b05e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- utBBc+8X9NkziOIfUnEhptcmdzjqkI3JNeAQSI/BbKrJDPV8jfC/FG8qlPNNH40vkepMPOuGN9JslKUOX7KeCw==