Identity & Signer Verification
via Trusted Providers

Identity verification is not required for every escrow transaction.
But when trust, value, or regulatory context demands it, SecureSign Escrow allows parties to add verification signals to a deal , without turning the platform into a compliance intermediary.

Verification is optional, deal-based, and always handled via third-party providers.

Why Identity Verification Exists in Escrow

Escrow protects funds. Identity verification reduces uncertainty about who is on the other side of the agreement.

Parties typically choose verification for:

cross-border transactions,
higher-value agreements,
corporate or institutional counterparties,
regulated or audited environments,
milestone-based or long-running deals.

SecureSign Escrow makes verification available when needed, not mandatory by default.

Identity Verification Is Optional and Configurable

Verification is never imposed by SecureSign Escrow.

Instead, parties decide:

whether verification is required,
which role(s) must be verified,
at what stage of the transaction,
what happens if verification fails or expires.

This keeps low-risk transactions frictionless, while allowing higher-risk deals to introduce safeguards.

Identity Verification via Signing (Default)

For many escrow transactions, identity verification already happens as part of the signing process.

SecureSign Escrow integrates with BoldSign, which includes built-in signer verification features such as:

email-based signer confirmation,
access-controlled signing links,
timestamped signing events,
signer metadata captured during the signing session.

For a large portion of standard commercial agreements, this level of verification is sufficient and proportionate.

No additional verification steps are required unless the parties explicitly choose to add them.

Signing-that-actually-triggers-execution-img1

How Identity Verification Works

When additional verification is enabled, the flow typically follows this structure:

1. Verification requirement is defined
The agreement specifies whether verification is required and for which participant(s).

2. Verification provider is selected
A third-party identity verification provider is chosen based on deal requirements.

3. Verification is completed externally
The counterparty completes the verification flow directly with the provider.

4. Verification status is returned
SecureSign Escrow receives a verification result (for example: verified, failed, expired).

5. Escrow logic responds
Based on the result, the transaction proceeds, pauses, or follows a predefined fallback.

SecureSign Escrow does not perform identity checks itself.

Extending Verification for Enterprise and Regulated Use

Some transactions require additional or jurisdiction-specific verification beyond signing-level checks.

For enterprise deployments, SecureSign Escrow supports integrating external identity verification providers alongside the signing flow.

This may include:

government-issued ID verification,
biometric checks,
corporate or beneficial-owner verification,
enhanced audit or reporting requirements.

These providers are integrated in addition to signing — not as a replacement.

SecureSign Escrow does not mandate a specific provider and does not aggregate identity data across transactions.

Wallet-based-control-over-escrowed-funds-img1

Third-Party Verification Providers

Verification is performed by independent providers, operating under their own legal and regulatory frameworks.

Examples include:

Sumsub
Onfido
Veriff
Stripe Identity

The choice of provider depends on geography, document types, risk profile, and enterprise requirements.

What Is Verified — and What Is Not

Identity verification typically confirms:

that a real person or entity completed the verification flow,
that submitted information passed provider checks,
a time-bound verification status.

Identity verification does not:

guarantee future behavior,
replace legal or commercial due diligence,
validate contract content,
eliminate all fraud risk.

It provides additional confidence, not certainty.

No Custody, No Compliance Ownership

SecureSign Escrow does not:

act as a KYC provider,
certify identities,
take regulatory responsibility for verification outcomes,
reuse or repurpose identity data.

Verification data is handled by the selected provider.

SecureSign Escrow records verification status and references only, unless explicitly configured otherwise.

Identity Verification as a Control Mechanism

Verification can be used as:

a precondition (for example: escrow can only be funded after verification),
a gate (for example: signing enabled only after verification),
a risk control (for example: higher limits unlocked after verification).

This makes identity verification a configurable control, not a platform rule.

Identity-Verification-as-a-Control-Mechanism

Identity Verification in Context

Identity verification complements other SecureSign Escrow capabilities:

Signing establishes intent
Wallets control funds
Arbitration resolves disputes
Identity verification increases counterparty certainty

Each capability can be enabled independently, per deal.

Identity Verification in Context

Identity verification complements other SecureSign Escrow capabilities:

Signing establishes intent
Wallets control funds
Arbitration resolves disputes
Identity verification increases counterparty certainty

Each capability can be enabled independently, per deal.

Add Verification Only When You Need It

Use signing-level verification by default.
Extend verification only when risk, value, or regulation requires it.

Talk to Sales