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
- 3d05d806de89e773b0b924e1c23ab03f52bdaef3a1565447d296744716bf8fbf
- request
- 09bb338e95089714e6cfcf10efb6d28551ac1f49bbd68ccb6afa5b4ff916c03d
- transaction
- fc329f73c9becfae99479698c4684517ea7d3d90b9a686b6b61fe11afd21f252computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70477
the chainentry 70477
- sealed to the entry before
- e9f18089fd66e847a701fb124b0d0a6ca1d9014e7dea58d8fbe8ebcf4d7b5040
- this leaf
- e2af852abf0acddceef8161f13a6e737df7f9838366b2b4611eba46be1dc832d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9BKKW2cxKJcV74OPlvRZMt1/jjRIPnlr7HWYvwScEIx7o/gDX+DFp12x7Ai9qTmyXgYA+NpVFMf7SFO04ECmAA==