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
- ffda7e08308081569026750eafee25230948645bf081306dedf9f09bc4ec84a6
- request
- 2386424d8e6989ba419a1a420695d4be42d00682f0465efd1c2d6898315943a8
- transaction
- e2e8b348647f77653d644cf7fb77527c87d3819214806cb3a08a34f2c65fd761computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1415
the chainentry 1415
- sealed to the entry before
- acacfd12400c3f1227db766fb0cf437475c972bc8a091318360284d0e45f319a
- this leaf
- c4917be48bb2f99461a28b8e5cc1a9407a5d7ee86da1d62bd92f0258e0ff608a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H/kma8LlHZz7s6EPqsX6VOtejrk71f1gH2BIo/nCA9Oesl40Eoa4l7ZrST/sxcv2lXdfScsfZpL0KXI2fNirDw==