lending and fintech
One application. The whole closing package.
The borrower answers once, and Mezdoc fills the note, the agreement and every addendum your rules call for, from the documents your counsel approved.
Fields that know what they hold.
- SSN
- Checked for a valid format before the form submits.
- EIN
- For business borrowers and guarantors.
- Currency
- Amounts formatted the same on every page.
- Percentage
- Rates held as numbers, not text.
- Calculated
- A value worked out from other fields.
- IBAN and SWIFT
- For international accounts.
- VIN
- For auto and equipment loans.
- Signature and initials
- Drawn, typed or uploaded.
Rules your credit policy already describes.
Your policy manual is full of conditions. Put them on the workflow once, and the package stops depending on whether someone remembered the exception.
| When the application says | The package gets |
|---|---|
borrowers > 1 | The co-borrower addendum |
repayment == "autopay" | The ACH authorization |
collateral == true | The security agreement |
amount > 100,000 | The personal guaranty |
state == "CA" | The California disclosure your counsel provides |
The paperwork this covers.
Bring the documents your counsel approved. Mezdoc fills and assembles them; it does not write or review your legal language. An amortization schedule is a loop over the payment rows your system sends.
- Promissory notes
- Loan agreements
- Commitment letters
- Security agreements
- Personal guaranties
- ACH authorizations
- Amortization schedules
- Payoff letters
- Adverse action notices
- Amendments and extensions
Written for an examiner, not just a borrower.
When someone asks what went out on a loan, the answer is already recorded: the version that produced each document, the signature details captured and a hash that shows it has not changed.
Read the security pageEvery version kept
A note signed under last quarter's wording renders from that exact version.
Safe to retry
Idempotency keys mean a retried render never makes a second document.
A signature record
The signer's email when an email code is on, the IP address, device and time.
A SHA-256 of every PDF
Recompute it on the file you hold to show it is the one that went out.
Questions from lending teams.
- Does Mezdoc decide what we must disclose?
No, and you should be wary of anything that claims to. Your compliance team decides which disclosures belong in which package and writes them as rules. Mezdoc applies those rules the same way every time and records what went out.
- Does Mezdoc verify identity or pull credit?
No. Mezdoc fills and assembles documents. Identity checks, credit decisions and underwriting stay in your own systems, and their results can fill the documents through the API.
- What about two borrowers on one loan?
Each submission has one signer. Send each borrower their own link: each one fills and signs, and each submission becomes its own PDF with its own signing record and timestamps.
- Can it run inside our origination flow?
Yes. Your loan system calls the API and stores the PDFs it returns, with a signed webhook when a workflow run finishes. A single form, such as an ACH authorization, can also be embedded in your portal on the sites you allow.
Bring one closing package.
Free plan, no card