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
- d69d2ee8b1a2e5533ffab37957cf4efc0644f1a396e38e085c2de5373a13e75e
- request
- 21f1e9a2e485a4834ca46df3555806a463d4fd5c599ddb33d8d0536861cb870d
- transaction
- d837688a18d58f7df23c63c11254830172343facc7df7c40d88ff02e0d4007efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62094
the chainentry 62094
- sealed to the entry before
- fc131cb3c9db7327912f1827048ad35c536480fdc7ca4b0a3e975c967cdb7682
- this leaf
- fb9714b8e1773fe831c79b643311fa3dae8d673402900e73b5e50cb38524be10
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8QwuYS9LByE3MVivLccvKZlofe5sow67QTIyD7RDQLLHzox4sEPilnkkeDyJvnuiEbZgDgGrE5IDcu5+iLjwCg==