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
- 1c32db078a479dd0375624c36403bd595a227af8470e52cd95504db470c51aca
- request
- df68f43c0e8e5786a4e844197c17608fd67846f2e7e7e3c36db0d39470ff0eb8
- transaction
- 217c1311028701a264752f3f5b168d28ebd4bc1299f2535c5f8896b56e25bb36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47227
the chainentry 47227
- sealed to the entry before
- c7e0ad9f1288167df594d3fa85ddbe846205561537a2de5ab8ff1956f95c4a3e
- this leaf
- ec4c4091995adea660292f90dfc1ead1a84985f46e212014bbc7fe07e0afad33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ixwZV/IvcN2At9ObWbbGrb2W/SjYv7FotfoIUQ7RgXDKOb26/y0/RVrsXi4y4+toBfU7A99RzFk4Bxvp0F5bCA==