Loan files signed where the lending happens: in your product.
Embedded signing for loan origination, account opening, and wealth management workflows. Built for fintech and financial-services platforms with identity assurance to match the stakes.
Domain or work email: either way you get a branded account. No credit card, no sales call.
Just need an API key? Create a plain account
The four signing workflows every financial services platform carries
Loan and credit authorization
Capture signed lending forms, disclosures, consents, and supporting agreements inside the origination flow.
Account opening and onboarding
Collect applications, disclosures, and client onboarding documents without sending anyone to a third-party site.
Servicing requests and amendments
Route account updates and approvals to the right teams, in order, with live status back to your system.
Advisory and investment docs
Manage signed advisory agreements and account forms with the audit trail your compliance team expects.
From application to executed, on the record
An applicant starts an action in your product: a loan application, a new account, an advisory agreement.
Amounts, terms, and party details arrive populated from your system of record. No rekeying, no transcription errors.
Authentication steps up to the stakes of the file: MFA, knowledge-based authentication, or a live ID scan before the signature is taken.
They sign inside your product, on your domain, in your brand. No redirect away from the flow you built.
The tamper-evident PDF, its certificate, and the complete event history return to your system, so the file is whole wherever you keep it.
Identity assurance that scales with the amount
A statement acknowledgment is not a six-figure loan note. Layer recipient authentication per document, from a simple emailed link up to MFA, knowledge-based authentication, and live ID scans, with every step recorded in the tamper-evident audit trail.
KBA and ID scan are per-transaction add-ons; see pricing.
Applications, disclosures, advisory agreements: one API shape.
Web components, not iframes: override any control, style with standard CSS. MIT-licensed SDKs on GitHub and npm. Live in 1-2 business days.
// 1. Create an envelope from your template
const envelope = await verdocs.envelopes.create({
template_id: 'engagement-letter',
recipients: [{ role: 'signer', email: client.email }],
fields: { client_name: client.name }, // pre-filled, still editable
})
// 2. Render signing inside your app
<VerdocsSign envelopeId={envelope.id} theme={yourBrand} />
// 3. Know the moment it completes
app.post('/webhooks/verdocs', ({ body }) => {
if (body.event === 'envelope.completed') fulfill(body.envelope_id)
})Multi-tenant white-label, built in
Each institution, program, or brand on your platform gets its own experience.
Every tenant, their own brand
White-label works at the multi-tenant level. Each of your customers gets a branded experience: their logo, their colors, their domain, their emails. Not yours, and never ours.
Own the SKU
Package, price, and sell signing as part of your product. Usage-based platform pricing leaves the margin, and the customer relationship, with you.
Aligned by design
We sell through you, not around you. Your success selling downstream is the business model, so partner support is the product, not a program.
Common questions from financial services platforms
Can we verify signer identity on high-stakes financial documents?
Yes. Layer authentication per document: from emailed links up to MFA, knowledge-based authentication, and live ID scans, each recorded in the tamper-evident audit trail.
Is Verdocs suitable for regulated financial workflows?
Verdocs is SOC 2 Type I attested and HIPAA compliant, signatures are ESIGN and UETA compliant with eIDAS SES and AES support, and every document carries a PKI-signed, tamper-evident certificate.
Can each institution or program on our platform have its own branding?
Yes. White-label operates at the multi-tenant level: each institution, program, or brand gets its own logo, colors, domain, and email sender.
How does electronic-records consent work on a disclosure-heavy file?
Consent to transact electronically, clear intent to sign, association of the signature with the record, and a copy the signer can retain are the four things the ESIGN Act and UETA look for, and Verdocs is built to satisfy them together. Disclosures carry your branding rather than ours, and the signer acknowledgment lands in the same audit trail as the signature.
What is actually in the evidence package?
A PKI digital signature, a tamper-evident seal, a signed certificate recording when and where the document was signed and by whom, and the full event history. Documents are encrypted with 2048-bit RSA private keys held in Hardware Security Modules.
Can we sequence applicant, co-applicant, and internal approvals?
Yes. Parallel and sequential routing supports signers, approvers, and carbon copies in whatever order the file requires, and each party can carry its own authentication level.
More questions? The full FAQ lives in the developer docs, from API auth and webhooks to eIDAS signature levels.
Evidence that holds up.
SOC 2 Type I · HIPAA compliant · ESIGN & UETA · eIDAS SES / AES · GDPR. Legally valid in 50+ countries and 60+ jurisdictions.