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
- 03fe23dce68c35b9cc480f30167cccd8d3369d0e984c887e1a74f281171975b7
- request
- 6ebf401c1c0a2824c2668747f4fe7edb1d1476f569bd9e98facfd3785d095264
- transaction
- a9dad612da07b548a59ea12b5803c6cc7bb6a717ab4183afb1634c9507992d7acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71818
the chainentry 71818
- sealed to the entry before
- b75b911054b922f1a05dfe67550698125f16398d8ba9dc970ec522de4f0435c1
- this leaf
- 62f02564b11fac2b6ca8c1038a50b46ebd9beef8a8f7516ec486b1f9a91b4e36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d7XXeu5LkuT7zaU3TlP1QTLQ+vXNk/AJM09qH2eKmqmdtY+CyQIDE5geuP7UQFECYJ/2rOhMv+WH9CyoAmsVCA==