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
- 6c2ba58c3203e6cffceb9ddcf9241a36798f01cc09712daa6c36e887270ad588
- request
- 070f959f358335e838db5013d7c3903cc6e43e8ab5af1b45093ca82771efbebd
- transaction
- 11a3e8f1be5ec649773143e58ae26c67c6dbf5a5e608ab1ca07133ae42f22a67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18101
the chainentry 18101
- sealed to the entry before
- a305f7d91313b3fd95a78acba00b444f9ce35180773b127828b275c38f217317
- this leaf
- f5af16854580e1db2936a80b14ff0d59aac5baf201d1b9c52b751dba8d3dbd20
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rlK3poFZfQ6yZLljqjfucLmNo5yWMlpPTzhmNBTibpUl5yu5Z+E1K7QKLvjGEnFxWlAhTn1qcsvi3KWgGo1ZBw==