CT Signature white-labeling

White-label e-signature your customers see as yours.

Embed CT Signature in your product with full white-labeling. Per-tenant sender brand, signing UI colors, email domain, and email templates — your customers see your brand, not ours. Multi-tenant from day one with strict per-tenant isolation. ESIGN/UETA compliant. Pay-as-you-go pricing.

Get API credentials How white-labeling works

Per-tenant brand: Each customer's own brand
Custom email domain: Signature requests from your domain
Multi-tenant: Strict isolation

What white-labeling covers

Every signer touchpoint, your brand

Signers should never see CT Signature in your white-label flow. Every touchpoint — email, signing UI, completed PDF — reflects your brand.

Sender brand and logo on signature requests
Signing UI primary color and logo
Email-from domain custom per tenant
Email templates configurable per tenant
Signed PDF brand attribution

Per-tenant

Each customer fully isolated

Custom domain

Email-from per tenant

Multi-tenant

Database-layer isolation

Pay-per-envelope

Pass through or absorb cost

Why this matters

If signers see another vendor's brand in your white-label flow, you're not actually white-labeled.

When a SaaS or OEM partner embeds e-signature into their product, the test of whether the integration is truly white-labeled is what the end signer sees. Some vendors stop at hiding the brand on the signing UI but leave their domain in the from-address of the email; the recipient sees 'donotreply@othervendor.com' and the white-label illusion breaks. Some hide email branding but leave their name in the completed PDF's footer. Either way, your customer's brand isn't fully delivered.

CT Signature's white-labeling covers every touchpoint. The sender brand on signature request emails is your customer's brand (configurable per tenant). The from-address email domain is your customer's domain (with proper authentication setup during onboarding). The signing UI's primary color, logo, and supporting copy reflect your customer's brand. The completed PDF's footer attribution is your customer's brand. Signers never see CT Signature in the flow.

Multi-tenant from day one means each of your customers operates in their own isolated tenant on the platform. Templates, envelopes, and audit history are isolated per tenant. White-label settings are per-tenant. Strict data isolation at the database layer ensures one customer's data can't bleed into another's, regardless of application bugs. The white-labeling is per-tenant; the isolation is per-tenant; the audit trail is per-tenant.

What real white-labeling delivers

Email-from custom domain — signature requests from your customer's domain
Signing UI brand — primary color, logo, supporting copy per tenant
PDF footer attribution — your customer's brand on the executed document
Per-tenant isolation — templates, envelopes, audit history scoped per customer
Pay-per-envelope — cost flows through to your usage model however you handle it

White-labeling capabilities

What CT Signature delivers for embedded use cases.

Sender brand on signature request emails

Each signature request email displays your customer's brand and logo (configurable per tenant). The signer sees your customer as the sender of the request, not CT Signature. The from-name reflects your customer's brand.

Custom email-from domain per tenant

Configure each tenant with their own email-from domain (with proper SPF/DKIM/DMARC setup during onboarding). Signature requests come from your customer's domain, not from CT Signature's. The deliverability and brand authenticity are preserved.

Signing UI custom-branded per tenant

Primary color, logo placement, supporting copy — all configurable per tenant. The signing UI signers interact with reflects your customer's brand entirely. CT Signature's name doesn't appear in the signer flow.

PDF footer attribution per tenant

The completed PDF's footer attribution shows your customer's brand. The audit certificate references your customer's brand. The artifact signers and your customer's customers receive shows your customer as the issuing platform.

Per-tenant template, envelope, and audit isolation

Each tenant operates in an isolated environment: their own templates, their own envelope history, their own audit trail. Database-layer isolation ensures one tenant's data is genuinely separate from another's. Your customers can't see each other's data, can't share templates accidentally, can't confuse their audit trails.

Pay-as-you-go pricing flowing through your usage model

API access is on a subscription tier; volume scales with envelopes per tenant. SaaS partners typically either pass per-envelope cost through to their customers, fold it into their own pricing tiers, or absorb it into their margin. Either model works; the platform doesn't dictate.

What it looks like in practice

A few ways teams use this.

Property management SaaS embedding lease signing

Property management SaaS serves 50 property management companies. Each PM company has their own brand, their own tenant base, their own lease templates. Embed CT Signature with per-tenant configuration: each PM company configures their own brand, their own from-domain, their own signing UI colors. Tenants signing leases never see the SaaS or CT Signature — they see their property management company's brand. The white-label is complete from email to executed PDF.

Healthcare SaaS serving independent practices

Healthcare SaaS serves 200 independent practices. Each practice has its own brand and patient base. Multi-tenant CT Signature with per-practice white-labeling: each practice's patients sign consent forms in the practice's brand, not the SaaS's brand or CT Signature's. BAA covers the HIPAA-aligned controls. The platform is invisible to the patient.

OEM channel partner reselling under their brand

OEM partner resells e-signature under their own brand to their customer base. Full white-labeling means their customers experience the product as the OEM partner's offering. Pricing flows through the OEM's tier structure; CT Signature is the platform partner, not visible in the customer-facing experience.

Frequently asked

Common white-label questions.

Can the from-address domain be fully custom per tenant?

Yes, with proper email authentication setup. During tenant onboarding, the tenant's domain is configured with the SPF, DKIM, and DMARC records that authorize CT Signature's infrastructure to send on behalf of that domain. Once authentication is set up, signature requests come from the tenant's domain with full deliverability and authenticity.

How is per-tenant brand configuration managed?

White-label settings are configured per tenant via the API or admin UI. Logo upload, primary color hex value, signing UI copy customization, and email template customization are all per-tenant. Updates apply to future envelopes; existing in-flight envelopes preserve their original brand at time of send.

Can multiple tenants share templates, or is everything isolated?

By default, templates are tenant-isolated — each tenant's templates are private to that tenant. Some white-label scenarios benefit from a 'master template' that all tenants inherit (e.g., your customer's standard NDA available to their customers); these patterns are configurable but not the default. Strict isolation is the default; sharing is opt-in.

What does the audit certificate look like in a white-labeled flow?

The audit certificate references the tenant's brand as the issuing platform, with timestamps, IP addresses, device fingerprints, and cryptographic hashes per the standard format. The certificate is independently verifiable. CT Signature's name appears in the certificate as the underlying technology provider (similar to how 'Powered by Stripe' appears on payment receipts) but the issuing brand is the tenant.

How does pricing work for white-label / multi-tenant scenarios?

Pricing scales with total envelopes sent across all tenants. Volume discounts apply at higher aggregate usage. SaaS partners typically pass per-envelope cost through to their customers (transparent line item) or absorb it into their own pricing (fold into existing tiers). Either model is supported.

What happens to a tenant's data if they leave the SaaS partner?

Data ownership and migration is configurable per partnership. Standard pattern: tenant data is the SaaS partner's customer's data; if the tenant leaves the SaaS, the SaaS partner can export the tenant's templates, envelopes, and audit history for delivery to the customer. The platform supports clean tenant-level data export.

Embed signing your customers see as yours.

Get API credentials and we'll walk through your specific white-label scenario — per-tenant brand setup, custom domain configuration, template isolation, pricing flow.

Get API credentials Back to CT Signature