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
- 006913c304c4c157b629007a6300a3163d4f050b292eb81767ef098171a41e19
- request
- a180011f99cc263b27bc5a142e8a5d2b49b8fb6d04db082c2cf193f626d675e9
- transaction
- a9b06dadbbf42e776df60665309a77ef7fe77b41bc02f373bbd2e435e86c9932computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55518
the chainentry 55518
- sealed to the entry before
- b88da305f7377b1eafb59e09ad6383d6c2223251de59ccc2f20001af23b4db17
- this leaf
- 0996aa9438ae8df1a0b4ab6c0e82df4243417629e0400f4dbfe42f7cb1552768
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uTGLPFFdlSOtr0K6LnS0vSui7qEzPmPmteirRDnuzGkMYXZuWw4zIVKKpwb6YtD01/52vrOfdFWIbySJtJqFAA==