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
- 183f665778079f82db1da149abcab31d78f3b6692b630c6c660c18fdbd94e931
- request
- 8f4b60820b0563b2547ca6b29592d071aac068512783836d4113895aec06933e
- transaction
- 2efbca8bdb4e81966ebc113a7f0ba9d35fbdc614a656b489b007ba4151e3809acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70709
the chainentry 70709
- sealed to the entry before
- 1cb815591b5920ea6d10f1eacd5721245aa395ad2f934a18a8db246ac02ff7bf
- this leaf
- a205e5c47800b2fb4457b238403bef283ce73eeea904287f590899001d4c8387
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CN2XKKI0KwV5yztv8XF9Bl8DwOYxc0UgJ3am0/lfznUqgHevI/Pe3jK0yIoO0tg/GYZ7pC0Kx0IXa2GBfg9OAw==