SDT Engine / Capability
Verify a recipient's government-issued ID inside the same no-login secure session that captured it. The verified result returns through the same callback you already configured. One session. One audit trail. Zero portal accounts.
P2 ID Verification is the SDT Engine primitive that confirms a captured government-issued ID actually belongs to the recipient on the other end of the session. P2 means a single recipient session that hosts multiple secure operations. Inside that session, P2 ID Capture takes the image, P2 ID Verification confirms the identity. Both happen before the data ever leaves the encrypted SDT transport.
The verified result lands in your system through the same webhook callback your application already accepts. You do not stand up a separate identity provider. You do not stitch together a capture vendor, a verification vendor, and an audit vendor. You do not ask the recipient to install an app, create an account, or remember a password. The recipient clicks one notification. The session opens. Capture, verify, and return all happen inside that one session boundary.
Because the verification stops at the session boundary, the verified record is available to your callback before the recipient is finished. By the time your system writes the record to your Customer Relationship Management (CRM), Dealer Management System (DMS), Loan Origination System (LOS), or Electronic Health Record (EHR), the identity is already proven.
Every Botdoc External Automation Project (EAP) embeds P2 ID Verification inside its specific workflow. Same primitive, different verticals, same audit posture.
Self-serve secure transport
Drop ID Verification into any Spark send when the recipient identity matters. Available as a one-click toggle on supported plans.
See Spark →Automotive CRM and DMS workflow
Driver's license verification runs at the moment the customer captures their ID. The verified record writes back to the dealer's CRM or DMS automatically.
See Connect →On-demand secure messaging
Identity verification fires inside the Lite session when a dealer or other operator needs to confirm the recipient before releasing documents.
See Lite →Scan-to-email replacement for regulated organizations
Optional add-on for workflows where an MFP scan is paired with an ID check, such as new-account openings or patient intake at the front desk.
See SecureMFP →Automotive vertical bundle
The full dealer-floor stack. ID Verification sits inside F&I document collection, test-drive intake, and credit-application flows.
See SecureMyDealer →Two paths. Pick the one that matches how much you want to own.
Path 1
Create a P2 container, add the ID capture and verification modules, set your callback URL, send the recipient notification. The verified result comes back on your callback before the recipient finishes the session.
Path 2
If your workflow is automotive, financial scan-to-email, or self-serve secure transport, the relevant Botdoc EAP already has P2 ID Verification wired in. You buy the product, you turn on the toggle, you stop building.
P2 ID Verification runs on the same patented SDT Engine that powers every Botdoc product. The patents that cover the no-login session architecture are granted in the United States, Canada, the European Union, Australia, and Japan. See the full patent portfolio →
P2 ID Verification is the identity primitive that maps cleanly to the identity-proofing language in the regulatory frameworks Botdoc customers operate under.
If you want to build it yourself, the sandbox is open. If you want a working product that already has it, the EAP catalog is open too.