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
- 4cfdf2b5463866da7808de69e7cc16d4364ac71c3471115303f24017c6998373
- request
- cbb6f30583526846bd36126f181d1277e3c96b0cc5c6aaf9b291cc555f1e8305
- transaction
- 7f19cf66ddcb3c18c6d9d1bb734c1b6867507afe8ec67fd2344c30416b443572computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26036
the chainentry 26036
- sealed to the entry before
- 3ca1c52f98ee0ea111143e00335f0d33ae167cf46832e37b9ad0e3dd959220eb
- this leaf
- 05f785586bf243828ecd00a4848da3cef0c1b5079b961c0af316680a08d503b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aQdfy4LWzfEE0aDFLm9uESoPuYShBVdZJcxcMCU7BcRf5BK8ZtZDbF1JDOfmfHQ5vUEffAuoIXCGdQp0UzfjDg==