Define the process
Identify the check your agreement needs and when it should happen.
Configure recipient access and the checks your agreement needs. Understand the journey before asking someone to sign.
Compare the journey for each method.
The personal link connects the recipient to the document they need to sign.
The recipient enters the code received on the configured phone.
The workflow directs the recipient to the configured identity provider and records the result.
Access to the invitation
Access to the phone
Identity through a provider
Opening an invitation, verifying a phone and checking someone’s identity are different actions. Choose a method for your process and review the evidence it provides.
Match the method to the document and the signer’s experience.
Identify the check your agreement needs and when it should happen.
Review SMS or identity verification availability in your account.
Consult the verification events recorded in the document journey.
Different situations. A process you can recognise.
The recipient opens their signing link.
A code is requested from the configured phone.
A KYC provider takes part when the workflow requires it.
If your process needs something more, we’ll explore it with you.
Talk to the teamNo. An SMS code checks access to the phone used. Identity verification is a separate process that may require a KYC provider.
It depends on configuration, the provider and service conditions. Contact the team to confirm the journey available for your use case.
An identity check alone does not make a signature qualified. See our legal validity page for signature levels and requirements.
Explore legal validityCheck feature availability and limits in your plan.