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
- 5105ffb1d68700804254020755f261cb95f61b7d414eb0303bfed8e2ef9b0048
- request
- 5710d1d98c44715e40e596a4479014074373f7263b28773f178791b3acdadd73
- transaction
- 5d95aa9fefb12517e4815c2ed8845916eeda22abface0b72773435e9f115844dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54893
the chainentry 54893
- sealed to the entry before
- 251e2da6c21edbd6f2db1116d4ba1af3ee42d1f44ce44fa63a995c957351e2eb
- this leaf
- 50dd1e538908c902b620285a7113d14dfa6452d8a1ecee6be57d2c0ec7a05341
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QGsAsdDshpMijrnnsBzTYN9St/92TJu98a20h40iZke6hUfhLFQXcQYVzb+fQkZu/0bG0wuOUjaCEsM6su5gAg==