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
- 6fe8d730f350a38e813903c70e3202300f74eb4491859ac1271b847f26518150
- request
- a77e287f294f5b76e962976577054be7efe68b3750183bd0ad441d13dfaf9fa8
- transaction
- 8bdab12b6d4df4794523207b4f74ecc4bdddae2e71823f7dc909a7da41f8a754computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70445
the chainentry 70445
- sealed to the entry before
- e89c0456b25c61a117473d769a61de0604389db1dbea32178f00f49f2d4fb8cc
- this leaf
- 90918307c2d565ac2ae1817426e1a6356cd25f9401133dd12c778418652a3068
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fi5onpejoSVwz5DEbYVmaqUtx5Sk7tZSGWjpRl6UUjrJogBS6Eu5dt6rjbXbVAaU1d7+IW+D4JnxWkmCl26fAA==