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
- d8054c9666cd1718291eb8c0d19d347d3682e6f19ee284c5e38f51c4ef1ef448
- request
- b1d2b09bc11501b71d222280f9e53f307ebd1265f8a7d9819efcdd4a0c1a03d5
- transaction
- 32bef17c5268aca3a8dbc819b1b10590d40d506d21f7eab1b9ed135e37687a87computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47617
the chainentry 47617
- sealed to the entry before
- 4333a4863b6ea06517308ec8702267ab52d33d986b62b0ced3ab9ae543f0bc99
- this leaf
- ccbbd2e170ea6200a6bddc384bab96b7ca0e0abd30c151264742a5002b2a7f6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4nOWa3xBSYFoBb5XQd8q3e94r/m8EK6mx1/PmMqevE4eNT7XO0O1qShlj+AZ87D4s6WvRJTHyaffvPAb68u1DA==