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
- 484a91a194e9b27599c13b7fb77111bd35da7a28b48ce3a57f761ff1600e910f
- request
- eba929ca79abdc061e931bef9446d06352cb7a1b39db6c54317d7c5b23b57166
- transaction
- 897340dd54930b9331bb203ef100a6fbf493d157dede3d3b9577f32f2d1f69e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75523
the chainentry 75523
- sealed to the entry before
- 84f8bc73889f83dd540f8f74f1231e86f9dc961abf43d7a8e16645e943369041
- this leaf
- c5a1b9c30a7a630081c82bbbf47cfa3ce7d9f40d57d20d5f293fafe2c777a016
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /so8ewgF3rSepJ1rfHScSB4aW0DSt//BSD9MfwFSoC5Ps9+K9RI+dOdh9AWHwXOXuotVjKB+okuM8HiDbBVIAQ==