Knowledge Based Authentication (KBA) verifies a signer’s identity and supports compliance. Ask a few dynamic questions and allow signing only after successful verification.
Send a signing request
Create your document flow once, then invite signers by email or shared link.
Verify with KBA
Ask knowledge-based questions and decide access based on the result.
Capture proof
Record verification status and signing events in an audit-ready trail.
KBA is an identity check based on information the signer is expected to know. It is commonly used to reduce impersonation risk in remote signing flows and to satisfy compliance requirements for forms like IRS Form 8879.
Extra identity signal
Add a verification step before signing, without requiring hardware or in-person checks.
Verify identity
Verify identity inline and limit attempts to reduce guessing. Set rules that match your policy.
Audit-ready trail
Keep a clear record of verification and signature events for internal reviews and compliance.
KBA is a practical middle ground between basic email verification and higher-friction identity proofing. Use it when you need an extra checkpoint, but want signers to finish in minutes.
Reduce fraud with minimal friction
Add a quick verification step before signing, so only the intended recipient can proceed. KBA fits naturally into remote workflows and can be enabled only for documents that need it.
Better confidence in signer identity
Use verification when agreements are sensitive, high value, or time critical.
Fast for recipients
Verification happens inline, so signers do not have to switch tools or schedule a call.
Configurable policy
Set pass thresholds, retry limits, and fallback options that match your risk policy.
Keep evidence you can act on
When disputes happen, you need more than "signed". DocuSeal is built around traceability, so your workflow can store verification status alongside the signing timeline.
Consistent audit trail
Track who accessed the document, when verification occurred, and the outcome.
Automate downstream checks
Send verification and completion events to your systems via webhooks.
Clear reporting
Review verification outcomes across templates and teams to improve processes over time.
Add an extra layer of security to your documents with our simple, transparent pricing.
Ensure the identity of your signers with dynamic, knowledge-based verification questions.
Answers to common questions about Knowledge Based Authentication in signing workflows.
What is KBA?
KBA is an identity check that asks the signer questions based on information they are expected to know. It is used to add confidence that the person opening the signing session is the intended recipient.
Is KBA the same as SMS or email OTP?
No. OTP verifies that the signer controls a phone number or inbox. KBA checks knowledge. Many teams use both, for example OTP to validate access and KBA for a second identity signal.
Is it IRS 8879 compliant?
Yes, KBA meets the identity verification requirements for IRS Form 8879 (e-file authorization) and other tax-related documents that require higher identity assurance than simple email verification.
How many questions should we use?
A short set is usually enough. The KBA workflow can be tuned based on your risk level and signer experience. Add retry limits to reduce guessing and provide fallbacks for legitimate signers.
What happens if a signer fails KBA?
You can block access to signing, require an alternative verification step, or route the request for manual review. The best choice depends on your security policy and how sensitive the document is.
Does KBA make a signature legally binding?
KBA is not a signature type - it is a verification step. Legal enforceability depends on the signature method, audit trail, and applicable regulation.
Please contact support@docuseal.com to enable Knowledge Based Authentication for your account.