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
- a6cfc32eccf55fae89e6ab551a56894fc16b407f1f69b122a0b0dabec52500ce
- request
- 64b4f10797617f1aedd22bc1b4106ab5988d2716a7b95fd428b29ed001ddcbb8
- transaction
- ee79b6b57a3f3c2dbdf01ad590ef181fba4ca6a0c067b1fc6578be88b18192dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18198
the chainentry 18198
- sealed to the entry before
- 96d8e6f0e2e331fef17db9a5aa749c6d6f9ca198b9bfe6f754bcc72cd97cdd6f
- this leaf
- d25c241bfd91cfc4f80d22bf3713f6d0581fa4fa619c7108d5f9e970eb6e67dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sj9eKu5vOoIjAYa6rhbKuMtJler82WLEO4uQ7NNT0ZbOIG8lejutp0Lk0YHsK2roer11s0qiVcpY4rbLYXTkBA==