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
- 0c4fff90e82155849c73e75fc19c64d55f0c3270b2d10179057c69ca08490e3b
- request
- 9c576f1aadd01e620b71d5af3d4aeaaff03cca3321bc835cc82fd78716dc3a19
- transaction
- db12eff252aae6d58d10f4a41a96f22ac82f6737abc6ede9b8e3b79b4d8c4eedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56625
the chainentry 56625
- sealed to the entry before
- 882dac7f3184a3383ae7f27d1d5e99fb3438cbba006821c804e2ab975d302111
- this leaf
- f449b6b85b5ac68146748215bf66fbb1d2a0783ef8015ca4f7d63c67d9ae4ded
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dv+k17qbElu4ZR/ALUTeeqjuh9TuJ3xJsFJ8DiXX+fJ1HzeFFtQdao3ddzSWR2QSCqsboTEjw2jsq7jGIiKLAQ==