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
- 8ee93ca791b9fa2d77e550983310b242d442777acb4c5589e8c0237565408a5e
- request
- 54c0ad8c79549f3d152b3031ed3a0faf58822fc35d37656bea9669960b029436
- transaction
- 5e38046ba5457170ef475ca3f2ecada1e675b2517118e0b095bd5628787446b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50363
the chainentry 50363
- sealed to the entry before
- 21676d5caa8e3ae14ec640ef73ebcc404a9286a81c5dd13d041dd8518e46f2d1
- this leaf
- fd1c34cebc2e3363c793ad7bad346053d6c0cf096f441e92ba1add95141dc097
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DstrJdsB6/5HRdYl+260ddXfqF5T4bASQSXvnbRaaKCA9ejt3mdynUaUHy84LAUs+miGRzomQf+dRgcQ4fUtDA==