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
- f3577b7a4be4f445bcd30ba8bc342f02deaa023e67de59ac81d94bd640cd881e
- request
- 1150335ca7f1cfb8c0bc1974c8e36e8756ccef11372618b25a348dd703d7f358
- transaction
- a509f1d1abb7dfc5662a2972e8105724ab9dfc16a1954cda3f1140abf74cbec5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46838
the chainentry 46838
- sealed to the entry before
- 0428f93de58d2f9e7ffae5772a573648e1713257a0539dd3b220807f028c2575
- this leaf
- fd06630bf7e81fb0738ec2830b45ca59f6858f56d46edde5fed8120806fdabec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +UPFb0wnFqe+KErvHC/M0cqksgS4BLGATJSEdPwM+VN6PdxGZ7sBMmSiC+ThFO0t+sGKjkBtMG96pS9LJyQWDA==