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
- 1eebf150242c73f8b6485be57b5dc95ac3819e7d3e2c056be1005c833e156e85
- request
- 52f64802e6921882fa5922fc650c79bb5e544931507b4f950a684e6e93245c00
- transaction
- 15c5514ac3338050731f9fde15de7525c60d9b719e75da39fcbef7a78e5b8ac9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37231
the chainentry 37231
- sealed to the entry before
- a364096f5acccba5c88dcb530d873466be540ecc388fc89778a99975c0f17c45
- this leaf
- 6cc3c56c58596cb8a00bef5c33993abfdf3ccda426d6b010ff0e30584e0297c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M9EZbdWxImThfck04rSDvwP/mHBKxl1jbRh9/xU6dzrm5aWP7QH/DOfTkduES8Y4Nses0eSdmLHttLvnSESeAg==