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
- 60d6badb4ff063368d95b35d73b43df83fe034f6c1c0c62f5b8dc1aff3678292
- request
- e45ab1b483c60f6ae1bdcf59389bb31ad66229e5abb950c6f30e4064e71f5c7d
- transaction
- 82a79e85057f7f1f6ae2aeb79ae54284558cf6fbdecc00c20d6ec2cefb776c7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44079
the chainentry 44079
- sealed to the entry before
- dde466554fc0c8444b4ede22f1f47420a7e0033741334f4b20c473928ca25eb6
- this leaf
- 24c3a7f97abc6e3ec66e6cd6edc27761e3889c9dc280aeb0b26e3f86db7dd9cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f4/7uJmo++TrY099q1Rced7gp8HCmyOhglAUNTYZWRUnc1MsP8zcmI1ZC5JMeTzuKf8r/oY/QTw13g6evVZ6AQ==