Signer authentication
Signer authentication: five checks before a document opens
BoldSign asks each signer to pass a check before the document opens: an email or text code, an access code, knowledge-based questions, or a government ID with a live selfie.
Example with sample data and demo names.
What can go wrong without signer authentication?
BoldSign signer authentication keeps a document in the hands of the person it was sent to, even if the signing link is forwarded.
-
A forwarded link opens the document
Without a check, anyone holding the link can open and sign.
See how signer checks solve it -
No proof when a signature is questioned
An email address alone does not show who opened the document.
See how check records solve it -
One check for every document
A single method is too much for routine paperwork and too little for high-risk documents.
See how per-signer checks solve it
Which five signer authentication methods does BoldSign offer?
BoldSign offers three codes, a knowledge check, and an ID check. The codes show that the signer can open an inbox, receive a text, or knows a shared code. KBA checks that a US signer can answer questions from public records, and ID verification checks a government ID against a live selfie.
- 01 · Access
Email OTP
BoldSign emails a one-time code to the signer, and the document opens only after they enter it. How email OTP is set up
- 02 · Access
SMS OTP
BoldSign sends the code by text message to the signer’s mobile number, tying the check to their phone. SMS OTP questions answered
- 03 · Access
Access code
You choose a code and give it to the signer outside BoldSign, for example on a call. BoldSign asks for it before the document opens. Change an access code
- 04 · Identity
Knowledge-based authentication (KBA)
BoldSign asks US signers questions drawn from public records, after they enter their legal name, address, and the last four digits of their Social Security number. No ID upload is needed. Knowledge-based authentication
- 05 · Identity
ID verification
The signer photographs a passport or driver’s license and takes a live selfie, and BoldSign matches the two through Stripe Identity before the document opens. Signer identity verification
- 06 · Recover
Locked until you reset
If a signer fails KBA or ID verification more times than you allow, the document locks for them until you reset or remove the check.
Can each signer on a document get a different check?
Yes, BoldSign sets authentication per signer, so one document can ask a client for an email code and a guarantor for KBA.
-
Choose a check for each signer
Pick a check for each signer.
-
Pass the check to open
They pass it to open the document.
-
Every check on record
The audit trail time-stamps each check.
Good to know: you can add a check to a signer after the document is sent.
How do the signer authentication methods compare?
The table shows what each BoldSign method asks of the signer, the plan that includes it, and what each check costs. Prices are in USD.
| Method | What the signer provides | Plan | Cost per check |
|---|---|---|---|
| Email OTP | A code emailed to them | Every plan, including the Essential plan | Included |
| Access code | A code you share with them | Every plan | Included |
| SMS OTP | A code texted to their phone | Business plan and above | $0.20 per SMS |
| KBA | Identity details, then answers to questions from public records | Business plan and above | $1.50 per attempt |
| ID verification | A government ID and a live selfie | Business plan and above | $2 per attempt |
Legally Valid.
Fully Secure.
Always Compliant.
BoldSign meets top global standards like SOC 2, GDPR, HIPAA, and PCI DSS. Every signature is legally enforceable under the ESIGN Act, UETA, eIDAS, and global laws. With AES-256 encryption, your data stays protected from start to finish.
IT and procurement teams can read the data processing agreement and the subprocessor list online, and request the SOC 2 Type 2 report. Single sign-on and user provisioning work with Microsoft Entra ID (See features by plan).
View security policyLimits and costs to know before you add signer authentication with BoldSign
BoldSign’s code methods show that the signer can open an email, receive a text, or knows the code. They do not confirm who the person is. Prices are in USD.
- $0.20 per SMS OTP The rate varies by the recipient’s country.
- $1.50 per KBA attempt Charged when the signer starts the questions, pass or fail, and again on each retry.
- $2 per ID verification attempt Each completed attempt is charged, pass or fail, including retries.
Before your first authenticated send
- 10 min life of an email or SMS code After three resends, the Resend button is locked for 30 minutes.
- Plans. SMS OTP, KBA, and ID verification need the Business plan or higher, from $15 per user a month, billed yearly.
- SMS OTP. Works for mobile numbers in 26 supported countries.
- KBA. For US signers only, with 1 to 3 attempts per signer.No free trial credits.
- ID verification. Does not read ID details written in Arabic, Chinese, Cyrillic, Greek, Hebrew, Japanese, Korean, Tamil, or Thai script.No free trial credits.
Switching from another eSignature tool
Docusign templates import into BoldSign at no charge with BoldSign’s import tool, and BoldSign support helps teams make the switch.
- Guide
Import your Docusign templates
Step-by-step help for moving Docusign templates into BoldSign.
Read the import guide - Comparison
BoldSign compared with Docusign
Features and prices side by side, for teams moving from Docusign.
See the Docusign comparison - Comparison
BoldSign compared with Dropbox Sign
For teams moving from Dropbox Sign, formerly HelloSign.
See the Dropbox Sign comparison - Comparison
BoldSign compared with Adobe Acrobat Sign
For teams moving from Adobe Acrobat Sign.
See the Adobe comparison - Comparison
BoldSign compared with PandaDoc
For teams moving from PandaDoc.
See the PandaDoc comparison - Comparison
SignNow and other tools
Every eSignature tool BoldSign is compared with.
See all comparisons
Can developers add signer authentication through the API?
Yes, the BoldSign API sets an authentication type, such as EmailOTP, SMSOTP or AccessCode, on each signer.
Live sending needs the Enterprise API plan, and the free sandbox is for testing. The samples below come from the BoldSign developer guide and send a document with email OTP on one signer.
Read the developer docscurl -X 'POST' \
'https://api.boldsign.com/v1/document/send' \
-H 'accept: application/json' \
-H 'X-API-KEY: {your API key}' \
-H 'Content-Type: multipart/form-data' \
-F 'Signers={
"name": "hanky",
"emailAddress": "hankyWhites@gmail.com",
"signerType": "Signer",
"signerRole": "Signer",
"authenticationType": "EmailOTP",
"formFields": [
{
"id": "signid",
"fieldType": "Signature",
"pageNumber": 1,
"bounds": {
"x": 50,
"y": 100,
"width": 100,
"height": 60
},
"isRequired": true
}
]
}
' \
-F 'Files=@{your file}' var apiClient = new ApiClient("https://api.boldsign.com", "{Your API key}");
var documentClient = new DocumentClient(apiClient);
var documentFilePath = new DocumentFilePath
{
ContentType = "application/pdf",
FilePath = "{Your File path}"
};
var filesToUpload = new List<IDocumentFile>
{
documentFilePath,
};
var signatureField = new FormField(
id: "sign",
isRequired: true,
type:FieldType.Signature,
pageNumber: 1,
bounds: new Rectangle(x: 100, y: 100, width: 100, height: 50));
var formFieldCollections = new List<FormField>()
{
signatureField
};
var signer = new DocumentSigner(
signerName: "hanky",
signerEmail: "hankyWhites@gmail.com",
formFields: formFieldCollections,
authenticationType: AuthenticationType.EmailOTP,
locale: Locales.EN);
var documentSigners = new List<DocumentSigner>()
{
signer
};
var sendForSign = new SendForSign()
{
Signers = documentSigners,
Files = filesToUpload
};
var documentCreated = documentClient.SendDocument(sendForSign);
Console.WriteLine(documentCreated.DocumentId); import boldsign
configuration = boldsign.Configuration(host = "https://api.boldsign.com", api_key = "YOUR_API_KEY")
with boldsign.ApiClient(configuration) as api_client:
document_api = boldsign.DocumentApi(api_client)
send_for_sign = boldsign.SendForSign(
title = "Document SDK API",
document_title = "SDK Document Test case",
description = "Testing document from SDK integration test case",
files = ["YOUR_FILE_PATH"],
signers = [
boldsign.DocumentSigner(
name = "Hanky",
emailAddress = "hankyWhites@cubeflakes.com",
signerOrder = 1,
signerType = "Signer",
authenticationType = "EmailOTP",
formFields = [
boldsign.FormField(
name = "Sign",
fieldType = "Signature",
font = "Helvetica",
pageNumber = 1,
isRequired = True,
bounds = boldsign.Rectangle(x = 50, y = 50, width = 100, height = 150)
)
],
privateMessage = "This is private message for signer"
)
]
)
document_created = document_api.send_document(send_for_sign) <?php require_once "vendor/autoload.php";
use BoldSign\Configuration;
use BoldSign\Api\DocumentApi;
use BoldSign\Model\{FormField, Rectangle, DocumentSigner, SendForSign, DocumentInfo, FileInfo};
$config = new Configuration();
$config->setHost("https://api.boldsign.com");
$config->setApiKey('YOUR_API_KEY');
$document_api = new DocumentApi($config);
$form_field = new FormField();
$form_field->setName('Sign');
$form_field->setFieldType('Signature');
$form_field->setPageNumber(1);
$form_field->setFont('Helvetica');
$form_field->setIsRequired(true);
$bounds = new Rectangle([50, 50, 100, 150]);
$form_field->setBounds($bounds);
$document_signer = new DocumentSigner();
$document_signer->setName('Hanky');
$document_signer->setEmailAddress('hankyWhites@cubeflakes.com');
$document_signer->setSignerType('Signer');
$document_signer->setSignerOrder(1);
$document_signer->setFormFields([$form_field]);
$document_signer->setAuthenticationType('EmailOTP');
$document_signer->setPrivateMessage('This is private message for signer');
$send_for_sign = new SendForSign();
$documentInfo = new DocumentInfo();
$documentInfo->setTitle('Document SDK API');
$documentInfo->setDescription('Testing document from SDK integration test case');
$send_for_sign->setDocumentInfo([$documentInfo]);
$files = new FileInfo();
$files = 'YOUR_FILE_PATH';
$send_for_sign->setFiles([$files]);
$send_for_sign->setTitle('SDK Document Test case');
$send_for_sign->setSigners([$document_signer]);
$document_created = $document_api->sendDocument($send_for_sign); ApiClient client = Configuration.getDefaultApiClient();
client.setBasePath("https://api.boldsign.com");
client.setApiKey("YOUR_API_KEY");
DocumentApi documentApi = new DocumentApi(client);
FormField formField = new FormField();
formField.setName("Sign");
formField.setFieldType(FormField.FieldTypeEnum.SIGNATURE);
formField.setPageNumber(1);
formField.setFont(FormField.FontEnum.HELVETICA);
formField.setIsRequired(true);
Rectangle bounds = new Rectangle().x(100f).y(100f).width(100f).height(50f);
formField.setBounds(bounds);
DocumentSigner signer = new DocumentSigner();
signer.setName("Hanky");
signer.setEmailAddress("hankyWhites@cubeflakes.com");
signer.setSignerOrder(1);
signer.setSignerType(DocumentSigner.SignerTypeEnum.SIGNER);
signer.setFormFields(Arrays.asList(formField));
signer.setAuthenticationType(DocumentSigner.AuthenticationTypeEnum.EMAIL_OTP);
signer.setPrivateMessage("This is private message for signer");
SendForSign sendForSign = new SendForSign();
File file = new File("YOUR_FILE_PATH");
sendForSign.setFiles(Arrays.asList(file));
sendForSign.setSigners(Arrays.asList(signer));
sendForSign.setTitle("Document SDK API");
DocumentCreated documentCreated = documentApi.sendDocument(sendForSign); import { DocumentApi, DocumentSigner, DocumentInfo, FormField, Rectangle, SendForSign } from "boldsign";
import * as fs from 'fs';
const documentApi = new DocumentApi("https://api.boldsign.com");
documentApi.setApiKey("YOUR_API_KEY");
const bounds = new Rectangle();
bounds.x = 100;
bounds.y = 50;
bounds.width = 100;
bounds.height = 100;
const formField = new FormField();
formField.name = "Sign";
formField.fieldType = FormField.FieldTypeEnum.Signature;
formField.font = FormField.FontEnum.Helvetica;
formField.pageNumber = 1;
formField.isRequired = true;
formField.bounds = bounds;
const documentSigner = new DocumentSigner();
documentSigner.name = "David";
documentSigner.emailAddress = "david@cubeflakes.com";
documentSigner.signerOrder = 1;
documentSigner.signerType = DocumentSigner.SignerTypeEnum.Signer;
documentSigner.formFields = [formField];
documentSigner.authenticationType = DocumentSigner.AuthenticationTypeEnum.EmailOtp;
documentSigner.privateMessage = "This is private message for signer";
const files = fs.createReadStream("YOUR_FILE_PATH");
const sendForSign = new SendForSign();
const documentInfo = new DocumentInfo();
documentInfo.title = "SDK Document Test case";
documentInfo.description = "Testing document from SDK integration test case";
sendForSign.documentInfo = [documentInfo];
sendForSign.title = "Document SDK API";
sendForSign.signers = [documentSigner];
sendForSign.files = [files];
const documentCreated = documentApi.sendDocument(sendForSign); Frequently asked questions
What is signer authentication in eSignatures?
A check a signer must pass before they can open and sign a document. BoldSign offers 5: email OTP, SMS OTP, access code, KBA, and ID verification.
Can I sign contracts using SMS verification?
Yes. With BoldSign SMS OTP, the signer gets a one-time code by text and enters it to open the contract.
Which signer authentication method should I use?
For routine documents, email OTP or an access code confirms access, and SMS OTP ties the check to a phone. Where identity matters, ID verification checks a government ID against a live selfie, and KBA asks US signers questions from public records.
Is signer authentication free in BoldSign?
Email OTP and access code are free on every BoldSign plan. SMS OTP ($0.20 per SMS), KBA ($1.50 per attempt), and ID verification ($2 per attempt) are pay-as-you-go add-ons from the Business plan.
What is the difference between signer authentication and identity verification?
Signer authentication adds a check the signer must pass before they can open a document. Identity verification is one type of signer authentication: BoldSign checks the signer’s government ID against a live selfie.
Can I add authentication after sending a document?
Yes. In BoldSign you can add a check to a signer after sending, from the document’s overview page or through the API.