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
- 124444abb6dd83a990e633e2014a670212620e831641357095415f631bc9bf9a
- request
- ef4c587ce30da7ebbb8ab5afe66035583750d9bb283cd8205365b01c0f633385
- transaction
- 04d88158e7d86863328f3f1993b62db322a3c61052f362cf9c344eb80087e0a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3290
the chainentry 3290
- sealed to the entry before
- adc66e57ffb8f6b0a76053cf5480114052055d7b7c51816a671733fa00091ca6
- this leaf
- 2886b4616b0ec4df22560548b37ccc7d8387fb9fd2585ff8f3ce5ecf9aa4ee8b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oYz+9J8AISNbcR9z7Zplh002LeD46Atav680XWUukORplO6L76mCJGp7TZza1QUi3zLi2jV7CNAAaz9TZy9kAw==