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
- c08c92db7434ad7d774afc497c960b7500c1fbd6aaf9cf1ad6aef27c8babea4f
- request
- a1f0a3601091bb2881f4b0ccb44c74fea51168d1805216e50cecc94d6be7b8bb
- transaction
- 84a9d79f5a71114c67745989ddad4f974016a4bc7dcf4bbd7ba6e3506c1d214fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33225
the chainentry 33225
- sealed to the entry before
- 9fb303cfb787837540b750bdb5755ab3cfa81e274e0b75f665b54fcdee9bb19c
- this leaf
- a77ac5cf13d876f2b1c69bb69104029e62645436e8bdeea3e311c57aa24463f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KSkaH8rkMk+y2WzHkqlPSmxvDVcf/Ni8LQ/4K5Tf93hQ3AuUFOowttIRVmEXcA7wIKOZxn9Z/ZGV/44kXZbtCw==