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
- ee825f310422c6a7068b7ca9b8c537f4ff34b785fb1450afd0936e26576fc298
- request
- b5b7fcdc344944adcfae39520e385c53dd21941e9efefa540209c7a1d997df22
- transaction
- 6d886020ca5b2a109b4a690240cf360bf70fb2cef3de44833371ddb5bfa39c4ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2085
the chainentry 2085
- sealed to the entry before
- 5e72c65299e1566d20c64a9738fcc2de6df59e6709792a938316506344358851
- this leaf
- 0936ae8bd60ef2781fd4b6e0574368aa85c0689f737381f13d47731e69c1ea4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Osi8HOs27QzV0Imxv1x55PaS96Vq0wdolM4nCI8JjoW6z1c31VZNG8gDkIsSxJD3+ODniSyq1y0EjWla5MPaBQ==