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
- 5a11eef68dd49b44e65adfa067d7663fe3d77f26841615c6f2234824bb2d6fa7
- request
- 04907d9abdf6c37ff9b5ed5607b37cc8894caa42c2573c299bfea15bffe82d98
- transaction
- 312c316b9c5846897b9b851d5fb8bd593614e749eefedb9c93880cb1dc300aa4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67689
the chainentry 67689
- sealed to the entry before
- 5c91d64a5e1daad306104e47194d60e418083337fb250db7871d7a26373859ec
- this leaf
- 762c3a6d89eaf969a9b848bc41571106a70dc4a7988d6eaba5393f2fd1a2f8b1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Sd5jtmVgkBEA7CVIGLYR04FcxyIncvI9MPPb6ThrZbuAqhYUMa03+vap1FqrhM8vgPrEHSWHv9nOTvtqjhfUDQ==