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
- 23028eb8b74f143028f1a360ee7d35382d1ec8a9d035d5cf2f3a9ab416fd8f4c
- request
- c7b798f1862cc4b89e119203c379882324335c7184233ed51b47d80b79bc8ce2
- transaction
- d2c91a60b006b24bda88b706eace9cae0008f681b6496c75e6a3364a0e353f09computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75258
the chainentry 75258
- sealed to the entry before
- 63da8acc08f4acf60386f0d795804308a6dd5784e676fa1925eb7db334000093
- this leaf
- dd5b6f7060bd87424e8a4941f0385a130d4e98e3872a43f65ee751f2aac627b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XEmBcqj9VnG8Ri3NnPEZj2d01EFURUhgSrac+Z7tQVmjcLdlwt4i2lfcaeUMikaehbZdFa3HTxprZfPCGfy7DA==