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
- 32897b7baee16e144e5cf1689b45949b0055bbfed4333519199e3a33a9a06434
- request
- 6f6b3fd4d9fb72d886a91b6c4873d417aff647ae6a85d69f93b125d2ceef1f7c
- transaction
- 38ec199275ea0aec5894d8a245dd47d34f6d022c9967586b096ee7b39dd9f4f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25510
the chainentry 25510
- sealed to the entry before
- b557baba6a04c73957b1df68b6430da35b1a826e91ca254d93045952ac8c8a1b
- this leaf
- fa79d7c738d8923be45b385ca7bf8aa79f600f833ab59f9df319ebce563fd568
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DrC0BvjiOTNjXicE9MhNPx6d7jsq+9zy0gZScUpZ8ppGQn395cppMGCTnU5D74oZLyPy3Vx+epAqiVfYDbBeCQ==