Solutions
A disclosure recorda regulator would actually accept
A mortgage file is mostly required disclosures, each one needing proof that the borrower read it before they accepted it, plus a paper trail that survives an audit years later.
No card to start. Every paid plan includes payments, the API and your own branding.
Mortgage
Where the paperwork actually drags
Each workflow below names the step that slows it down today and how eSignPro closes it.
Required disclosures
Borrower and co-borrower read, consent, and sign; the loan officer counter-signs.
Proving a borrower actually saw a disclosure before agreeing to it is the part most e-signature tools skip.
The ESIGN consent gate runs before the document is even readable, so the record shows consent came before the signature, not after.
Identity on the borrower’s side
Borrower and co-borrower, often signing from different locations.
A signed disclosure with no identity check behind it is weak evidence if a borrower later disputes it.
An email or text code verifies the signer before the fields unlock, and that step is logged with everything else.
The audit trail itself
Compliance, underwriting, or an auditor reviewing the file later.
A mortgage file gets revisited long after closing, and a log that cannot be handed to a third party is not useful when that happens.
Every view and field change is timestamped against the person who made it, with IP and device recorded, and the finished PDF carries an audit certificate.
Proving the file has not changed
Anyone checking the file after closing: a secondary market buyer, an auditor, the borrower’s own attorney.
Emailing a PDF and a screenshot of a log is not something a third party can verify on their own.
The public verification page confirms the SHA-256 hash and the signers with no login, so anyone can check the file independently.
Document guides
Related document guides
How to set up the documents this line of work sends most: who signs, in what order, and every field.
Questions
Questions people ask first
Does the borrower have to accept a disclosure before they can sign it?
Yes. The ESIGN/UETA consent screen has to be accepted before the document becomes viewable, and that order is what the audit trail shows.
Is the borrower’s identity checked before they can fill in fields?
Yes, with an email or text message code. The verification step is recorded in the audit log alongside the signature itself.
Can an auditor check a closed file without a eSignPro account?
Yes. The public verification link confirms the document’s hash, its signers, and its completion time to anyone who has it, with no login.
What does the finished PDF actually carry with it?
The signed document, an appended audit certificate, and a SHA-256 hash on both the original and the final file.
Solutions