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
- c14dd43f2d035e62b121928ea889e1a5175317128c362892f54be69f8349712f
- request
- a1638336a901f125695019d3675bcbd288ed5bad9f4b720b695223bebdca67e2
- transaction
- a6f4d06eef07a51b83f343e8e32a94e18b8d80c8063e4cfad77e05b9fb2a82b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46805
the chainentry 46805
- sealed to the entry before
- e94a2f26fe1063a1297291fbd35f24f734eab33be6e0d3108b5d10bca59e7fdc
- this leaf
- 1b0b24e679d2846611ae26d4c75b30211cec2b31d5170a3e4b228ecb314a1eff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M5+tLYZ6D2IQL8GVoxNu85amh2ncdDdxF9yLFlPecVnVmPxY+fKuFbYEDUay/VsW/NYlfp2Za7jflF3iG65wDw==