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
- 839166fa36669f6c6a1c11d5d2594d0a135c31e6397b5a03f58d634b5a84fa18
- request
- f8f1c6a6503c17e1f2cfafdd5fdee04f258d054562fd4086684587b9b68280b4
- transaction
- 77db91e56124ab8679b132ad36c870dd9892d3ba9e3ffbf529b2212fad75227bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28837
the chainentry 28837
- sealed to the entry before
- 253d8b5b5d3e543d2fa0c862f878c2de7d4f61ab5031b30edd9bdfe37c121e83
- this leaf
- 7fb665d7e0d935f133fea398f1f79138b4ef513bb5417fb68f8177401df6ca2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sx7ay0YkcJCfxH9I8CjKZAAg0VRMckL7lqe7sXZXgC119rTIa6PyH28F/xfL4qesaK5mf9Ew/QCQtU2ZPJmjCw==