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
- 69d05109cb731450097bc2539a2292b0fd45703ac78d6fc00d52d3045c47ea76
- request
- e1b1e4ad47f08479f982a5e2b451342354e11d7b675082e71d13020d39834e8d
- transaction
- aed414eacbed974f10a639ee979fd8e18e5df76066c755c55f707653741e2664computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42232
the chainentry 42232
- sealed to the entry before
- 16e1f90ab429c26e0f1b0615fb6cf3a8183ba09ac36bb6ffeae1fd8760051174
- this leaf
- 85f4a5f15bb73deb2c5448f7464c31a1a16d3bd5c66681db5f72c7b3449c5cd6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WafGuoX6qU9oYec77lzrBgIKDfbpT/yu+MEk5z6JyLaAReAOJAlmAc1BCzckhfS8zHUAyDX2oV6LXbEFA1ISAA==