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
- e7a2b6cf8241ab0953aab21cdeee8d7314629aab180c571c71d189ab331e798b
- request
- cd87412df64a5dea38fe84021be19eef5005ad8e486c16fd4736190f1a1c789b
- transaction
- d9ced21c8167f94dbb250fc5f0c52e00a572d8d92de6f3e6280b1331b4f3e476computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17570
the chainentry 17570
- sealed to the entry before
- 5e22789b27500efc42a758fc99ce85580dadd340f4e9dc582d41381ebad5fcf4
- this leaf
- 732869deeeb3c2c5c017999ef11430ca48d13a736332b10fd221b22e51b89f30
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KAEvgryO+KG1QSagnTbqnUqWGSil5Was9LGqvhfxZBoQyeE/4M7THL/vapJikhcX+cnB3PibK8D+IfNvZjlSCw==