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
- 1de465ee9606a18f268cd24583d0ed34967b7e675fde8774578e703b1b5460a3
- request
- b503386c9b4b0474a2f9b0f0048da06a34846a796bb0612f3d36cba6913dd773
- transaction
- 0821489703084e0bc7911cc8c21f305d0e278ef1eec11f1aa62ede82b5956ca5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70869
the chainentry 70869
- sealed to the entry before
- 6a2901719388786ebc8d1e0fe4c2b97c51180fea6ab65a9a8f775f586f25a2fe
- this leaf
- 03758ead1314743d4962fbb1f15b45b7de16fda494ddf5ea70c1b8839669d58c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N62cuJHBORr5K7Wnuozyyg4Y7d9dYatcX7Hz/TDXd3IyvS+2pafaRT+xS24y/75WfN85nEHBMtug/ytiXc1zBw==