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
- af04acb6f33a6add85b4ff42f6f627d0b3392cdb3af85be84c48ebaa64f529a2
- request
- 45f2232afd329679da82991e4faf842fcfa357a3958c22833f80773b5ff87f65
- transaction
- c217e9808330d940f4e3afe7ca345924def42f60364d007a28c433cd602d80c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33384
the chainentry 33384
- sealed to the entry before
- 0ec53ff585b20381714f60bc7d64f90ec07ef2785729d6f371357e3a9e5b9089
- this leaf
- 994c1354c2a55a0bb2bec5b1cbdf573c0930f95dab8c22c427115ee8eda72655
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pKcr5j+B5QXRJT6UJ62AsGlUWT/QMCaC4CAZ9D5IjfsgiErH/PqZnqD8jvVYtT4tuyyF8fiQF7dG/fGspOT2BQ==