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
- f964d2d9d7bed41e5af2d35c46951204f124ee68a75f424c1cff299a71913480
- request
- dd07ea1637642d3c5ac0c8a2aaf57d0945b4c691096a2513258c7755f5241bdd
- transaction
- 6c3e72a60eea7f90da3362c7d6d6ed8fd3559d7fab08a51c12d3a6c36f8bcd52computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30444
the chainentry 30444
- sealed to the entry before
- 993136d9be8774b6ec0593ef8cf406351b63919f2ed9d50ad57c534a1f26f1df
- this leaf
- 431948447c33d7d180c36e853b00aff7c00ba9fb7db55efdab97f26fbe813b9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ENCqnXCwB+BS/4OZX/GHa96PLldy/cPStDc0tZJfl+lYyjs6Mh+emAUnkr/TgSN20vbJC2zw9CFE2NvUYf1GCA==