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
- d89de735ebefcb9bc22778b4a6ec1ae2482c2df1c1f25cc3ddc2cec16c0f8898
- request
- 220049fcdc014290fa1ebf8b09374398588ef558e3c315d2222715d8728e98f2
- transaction
- 8d0fac656a3f9acf12ac7b78e54bf2c21d9c6355e3856d04cf28773f1241d74acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73026
the chainentry 73026
- sealed to the entry before
- 85166b4afd3f0e6a9cbc8fa08f8e6a3871eea5121bdefa6ec6c7c4a175162334
- this leaf
- b5989febf7389381f8cb3f3b0d246c30335cd6dffc65d560fff9e6fe54d2b874
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +D9R6sTzlMV+AxWDJABUKZS1uouhRUo8CIehQeHwSqm0XUJZ6D1IVrrn7Ti16RvHHXiDYe+gPp4ar0LFCrBhCQ==