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
- c6e0c913ed766d267a35e09921d1caf589b84f346910dd667ba64b07697b3dfc
- request
- 0f17953057d610fa3640c02ee1aa2b6a211e98bf185969dce60fc1550cadc03e
- transaction
- 4bc0698f6d2a65a9ae2b255abe29265991a497a25c08693b2b2a4b4eadaf7e0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72399
the chainentry 72399
- sealed to the entry before
- 5f6eea05fb7a2caa0a51cf2fe8b8afd9ae61662ed527bd87007c19ba262ffef4
- this leaf
- c6ea5989bb94e4b388f2d39e17a7ceb28911633f98aafa46ffb70bc31a80f2f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bHFMi1AZqYnnSo3NaCWqoj+/CZQdLtlbUT2FtDeIlKxHy3A854+F+/5uBDQxTXk8Vmp7wDVPWPrVqiweeq01DQ==