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
- 9e0625824749ff7657a7d95f18cf9eb2b8f22b6a623e7cbc0350b8a2b2ea5532
- request
- 4785c532c95d87aa9258f65417f3333c6e17d120bf52cc8b3f04b40669379b0f
- transaction
- 0656c884fed84ff7ae7ab91aefa48a70d63974559f6ce688d41f397e642c2346computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60691
the chainentry 60691
- sealed to the entry before
- e534a17ef2ea3b51fac231cbf8c6b8083bd563de3f495df34b15eab95a301e0f
- this leaf
- 4d6d6ce4beafddbefde734fe83a45999fcdeda1d09aa8981dfb7f65718424c01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +GZoiLeNXwuwzDnAvYoTbgXnAnjcM9kMUrRFUngPFKKFGyrIwxllBw06PfSenovrmM2HCWBnWYgqfOMMQFqTBA==