Why VYAX Sometimes Rejects a Signature Before It Reaches a Document

    Last verified: October 1, 2026

    A signature that's too faint to read, cut off at the edges, or a blank canvas someone accidentally submitted doesn't do anyone any good once it's embedded on a filed return. VYAX checks the image itself before it ever reaches an official document, not just whether a box got clicked.

    What actually gets caught

    A signature can be rejected for being empty, too faint to read, too low-resolution to hold up once printed, too large for the space it needs to fit, or carrying a background that would interfere with the document underneath it. Each case gets its own specific, clear error — not a generic "signature invalid."

    A clean background matters more than it sounds

    A signature pad naturally produces a transparent background, but a photo of a signature on paper doesn't — and a visible background can obscure the text sitting underneath it once embedded. Catching that before signing is complete, rather than noticing it on a printed return later, is the point.

    Save it once, reuse it without re-checking every time

    A client can save a signature that's already passed the check, so future documents reuse it directly — the quality gate runs at the point a signature is created, not as a repeated obstacle on every single document afterward.

    Try the signing flow for free →