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
- a94e726c46e1d3b044317e5f5c137c4965e205d929e37a85125d359d73a0062c
- request
- 8cb78b02880401e2f760aa2bcf742264b512ec004ed04bd637057a20f1508cfd
- transaction
- b1229f7c299368da9d78ec0efe7d2f71e4b1eb280ceef02dabc6ced1bf2745d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14644
the chainentry 14644
- sealed to the entry before
- 76111a5a34c9cd8587165b256ece97084e6cad3af24f05c8f7047ec369d795ad
- this leaf
- 600aea3c9445a9c246ca25374066413a8964c3d492c5bbb12f75e40fe214ffab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xdwJCrhy7KiVk+GU5euBNBdxXCzDOxGkLhZkL9W25jk/4P3lqftJbvJrg3mCp7qOYpU7/H9YIdcH11a7QUsaDA==