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
- 1e7514f00ffbb02448c608eb53d8e92d2270a2645a4e1e0521657e02be6a709d
- request
- f0c7731fdbd1bcaecc09a307d44e16fa89536c7bdae714425d4b03dc8a9d9d39
- transaction
- f15ea48c95da06372079037f873da247f3de86fc343b3e3ecd407f0976e75083computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1745
the chainentry 1745
- sealed to the entry before
- 07179c792f9aa903ea317017317d5c2aac0ec6acc216586d51199a19172747b8
- this leaf
- 58110c54f54c440e0535cd804ae942e6eafc64eecda7e673039956a2e42d0411
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SRdhyZ4utEAIkFMfFGflCcZLVxNF7+/xXdHJ7CeHmTU053qRe6Q4Aq37sLFiq4+YtKVXbNoO7lk8AlvsYA5NDw==