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
- e58644ce541ed47f8bc95b540ac54d0c016397a94d15f9f520f30161fcfce3b3
- request
- 140a09a096d0404708df55e2d6064ce2d2e97749fa383bdaa2217e1b69f840d9
- transaction
- f7dabb0097a5a0ddeb01579d09f7011149cd223091ca022dc35d460e176dedb1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34767
the chainentry 34767
- sealed to the entry before
- e3fffadbe30c1863fa26f3b9be3de62873a7df3d4b527b17db9c254eba22b5d5
- this leaf
- b2de4e8433f3b345aea5276ebc65fc86896f529df9e21d24ead8f47ec7916a50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dfCSyuE8n+18BcYFahnWXfrP5sUjaW6CRsVOI76Z+10sknd319WSVap7YYcwGfJj7a5V5e8e+Lzo1dLuCN2zAA==