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
- a8c8e7eda840e072d1961dd1c913972c2668fb76af4bcfcc0cfec38bd4b2d96e
- request
- 95cb11572067f440261a25b7ee2cd0a3e3c2a5ace673482bfbb276fa11aa59a0
- transaction
- b1f49d0379795844fbf8efb79c1045b0ae8b25324192db1ea8db22bdbd3fc628computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15145
the chainentry 15145
- sealed to the entry before
- ec33f8f67207df88032f00eaf932bea54f398841710a3a9775d98d83ae1dd4bf
- this leaf
- 00a1829b2f10243e081927e9adddab0ed510523fd12bbb96d56813f5c299bb65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2IduOjnYsqzvOL74dc2SQDNH/gF0LPGPprbqm+g5SlFUbaObj8xGaE+KxK19EGbNofIvG0ryyXj/KuFz6IErDg==