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
- 9154e245ffc34f4fad8e972d255f709f5a58c3ff65f1fc4cf49fe12ec2108c3a
- request
- d2137f3524014238961f21dbab0c31195075430522bf5a9ead03ac9233b80a52
- transaction
- b38a9f7e2cfa62c7922cdd368837561cc3c3c6635f9b1bc10ec11e9167bc6dc1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6771
the chainentry 6771
- sealed to the entry before
- 2b46edd3f3b27f9132363419a5faee9311dffcb37a306c2344136c75be46e10d
- this leaf
- 3058b665a10c1517ef2b03d31331a736250ac5b1c11332aee20c51b359426f38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TJ1Bw6/F9CkX7j5ReYQrRZCItorHgy7YxFhOvQ7z13vrxU56XIfo+XlGLq+73gvEdHonPLO1o2uxjTrYh2w/AA==