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
- 5e55cdd3b0710803a8fc467360bb7dfcf2067afacbd6ab14c16df70e9ca5400b
- request
- 8132df88968c9fda812a180e87a7d82a04998b7b5406640936d30ded6dcb4907
- transaction
- 8ee839b3a1fc33055c819fc0d265711487308afb2ad171548393c3d8cd9e3c16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38484
the chainentry 38484
- sealed to the entry before
- cb27b6d0d745483fb17172811a8ef3279a3ce4e1c8666c125f57ec1cc66918a6
- this leaf
- 19a6ea5273f095ebe80a36228616b3d6d6aab521a4295065e32f1b70528c25f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y1eBNxdf0CY0j1YRT0iAiAOFIbrF3zXBuOb5RWSXcHdHUEhQbVf8JPl9FpeEHlooTVujZAswysm1wF7GD34lAA==