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
- e77acac4458c46b69e01e61a3e980358e260a14acc79de9516dc675057a6e41a
- request
- ba9359eb6de9af0aaeafa7a76655447c20f5bfb6ad0aa759dc423694d795a9af
- transaction
- fd9c9df776f6c73f98f5235f64b1c784132a153d65b10adb53e185889d300483computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71270
the chainentry 71270
- sealed to the entry before
- 6beee05293f71a0c250620a5e4d95e593aa080a6c131eab8b021f3f3c339bfa4
- this leaf
- c34b0b015be53f6b7976ba8b95976fe0d2853e25ddb11292bf7a619c30d3e4b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YoVQO9F1mSInDkyTb550mmfbrqWlajcCKnZhaXwdJDYJ/ey3wVyC0BFAp1ff9l1GBrb2uhmUgf/VQbIjYSRWAA==