Embedded signing infrastructure

Signing that lives where your customers already are: inside your product, under your brand, from send to signed.

APIs, webhooks, and native web components for vertical SaaS platforms in insurance, accounting, legal, financial services, HR, and real estate.

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

app.yourcompany.com/policies/PL-2481
Policy endorsement · ready for signature
Sign hereSign
Tamper-evident · full audit trail● Live status via webhook

<verdocs-sign>Web components, not iframes: override any control, style with standard CSS.

50+
countries where signatures are legally valid
60+
jurisdictions covered
1-2
business days to go live
60+
web components in the SDK
Powering signing at
TPS Software
Majesco
MRP Realty
Finys
iBynd
Insured.io
Insillion
Silvervine
Uprise
Pazar

Standalone, integrated, or embedded: the decision, compressed.

Standalone eSign
Your customer leaves your product to sign somewhere else, under someone else’s brand. Fine for internal paperwork; a detour in a customer journey you spent years polishing.
The signer leaves. The vendor keeps the experience.
Integrated eSign
A plugin bolts a third-party tool onto your stack. Separate accounts, separate pricing, vendor branding on the emails, and the customer experience is owned by someone else.
Quick to start. Expensive to scale. Never truly yours.
Embedded signing infrastructure
Signing renders inside your application, on your domain, in your styles. Fields pre-fill from your data, webhooks report every event, and the audit trail lives with the document.
Your brand, your domain, your data. Live in 1-2 business days.
White-label everything

One infrastructure, four surfaces, all yours.

Build

An embedded builder, not just embedded signing

Your users create and edit their own templates and forms without leaving your product. The builder ships as white-label components, the same way the signing does.

Notify

Your name on every email

Send from your own email domain with your sender name, or drop signing links into the emails you already send. In the inbox, Verdocs can be invisible.

Sign

Signing inside your product

Your styles, your domain. Fields pre-fill from your data and the signer never leaves the page they trust.

Prove

Branded evidence, end to end

Disclosures, signing certificates, and tamper-evident audit trails carry your brand from consent to completion.

What your customer walks through today, versus with Verdocs.

Integrated eSign, 11 steps
  1. 1Subscribe to an eSign plan
  2. 2Upgrade CRM plan
  3. 3Find the right app
  4. 4Install app
  5. 5Configure
  6. 6Log in with app
  7. 7Upload document
  8. 8Map fields
  9. 9Sync applicant data
  10. 10Generate envelope
  11. 11Email the recipient
Embedded with Verdocs, 3 steps
1

Your customer clicks Sign in your product. No new tab, no vendor site, no account to create.

2

Fields arrive pre-filled from your data. They review, sign, and stay exactly where they were.

3

Your webhook fires the moment it completes. The signed, tamper-evident PDF files itself.

That is the entire flow.

For your engineers

Send with an API call. Watch it complete with a webhook.

Web components, not iframes: override any control, style with standard CSS. MIT-licensed SDKs on GitHub and npm. Free sandbox, API key in minutes.

// 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)
})
"Now that we have done it, I cannot imagine why a vertical software company would not consider it. There is a big difference between telling customers to go establish an outside account and telling them the capability is already here."
Tom Dawson, Founder and CEO, TPS Software
"Verdocs has allowed us to keep our clients in our environment instead of a disconnected and manual experience through email. By fully integrating document workflows in our application, we have dramatically improved operational efficiency while delivering a modern, branded experience."
Maggie Johnson, Product & Operations, MRPI Realty

And every one of your tenants gets this in their own brand.

agency-one.yourapp.comfirm-two.yourapp.combroker-three.yourapp.com

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.

Signing as a profit line, not a cost line: run the numbers in the ROI calculator

Keep your signers home.

Legally valid in 50+ countries and 60+ jurisdictions.

AICPA SOC 2 sealIndependently attestedAICPA SOC 2 Type Ireport available on request
ESIGN ActUS federal law15 U.S.C. § 7001
UETAUS state lawUniform Act, 1999
eIDASSES and AES · QES via TSPsRegulation (EU) 910/2014
HIPAAcontrols aligned to the Security Rule45 C.F.R. Part 164
GDPRdata processing addendum, applied automaticallyRegulation (EU) 2016/679

Common questions

What does Verdocs cost, and how does it compare?

Pricing is public and starts at $1,500 a year for 1,000 envelopes, scaling to $0.75 an envelope at the top self-serve tier. You pay for envelopes, not seats, so your whole team is included on every plan, and every plan is the entire platform with no feature gates to climb. At volume, platforms typically spend 65 to 80 percent less than on legacy eSign vendors.

What does "embedded" actually mean here?

Most eSignature vendors mean their application shown inside a frame on your page. We mean web components that render in your own DOM, so your CSS reaches every element and your developers control the behavior. Your signer never leaves your product, and the interface is not a black box.

Will our customers’ signers ever see Verdocs?

No. White-label works at the multi-tenant level: each of your customers gets their own logo, colors, domain, and emails on the signing experience. Not yours, and never ours.

How long does it take to go live?

A free sandbox with an API key takes minutes. Teams are typically live in one to two business days, because the SDK ships the whole document lifecycle as components rather than leaving you to build the interface yourself.

Are signatures through Verdocs legally binding?

Yes. Signatures are ESIGN Act and UETA compliant in the United States, with eIDAS SES and AES support in the EU and QES available through qualified trust service provider partnerships. Every document leaves with a PKI-signed, tamper-evident certificate and a full audit trail, and signatures are legally valid in 50+ countries.

What if we need to change how the signing interface behaves?

Change it. The components render in your DOM, so standard CSS restyles anything. If styling is not enough, the SDKs are MIT-licensed with the source public on GitHub and npm, so you can fork a component and change its behavior, not just its appearance.

More questions? The full FAQ lives in the developer docs, from API auth and webhooks to eIDAS signature levels.