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
- e7af504c217da370dfb2cca4286538e2880ca8c870cdde52fe69a56899b84515
- request
- 51ad8d271cedf21d762fbe67c54835076ab83a9eb65df01d717e0113424084ba
- transaction
- 1a08fff164a1a87844b1682bd8e1733f6cb1d3b8b1916e6a896369631b8bb947computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2590
the chainentry 2590
- sealed to the entry before
- d709915612713d51eb301e3a37bc8e452ec7a5767569df1a52838e2c19de5bc6
- this leaf
- 0654330d1cc47942af5976ca7ec3a05a0017e13685a098925584e2ced2d0e6d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EnUwVs4c7gyqIiXz9YW11uLsjQi9y6ogqdOviIdV1FeI0lOGtpNvQR1GrG1E19ioxSmRS1n1NlHC9u5lsDQkBw==