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
- a4c4e8c30a64bf5bd1b40d2daeb525ab5165b36d91ac7b2b4e0714e08c096e97
- request
- 531c9735517e4f93abd5eff4336a9e2eb92433b18436b38682f7a832ecdfa054
- transaction
- 3c37fef96d2c23db2488e8a6587ee24570d7d6dabfdfa7cbbc5eeea7f13e42e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35300
the chainentry 35300
- sealed to the entry before
- c59e41feccfc43be60fc6db00e46a0d178de8cffd84609b7c678a674dabcb569
- this leaf
- 35396ef6094147ceb32a368472f1f7618e72bbce8892d9e87ed707dbfe529eeb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NLdGzFgYb8ALt4tsRZBQSgQQvAIn2ocQhA7aruWRA+xYr0P/76rzAiw3oF+krCH30neoRLPbbgSXBpU/OVzyDA==