Call the Socure evaluation API endpoint /api/evaluation to generate a DocV transaction token; include the X-API-Version: 2025-01-01 header and your API key.
Pass the transaction token and your SDK key to the Socure DocV SDK (available for iOS, Android, React Native, and Web) to render the capture interface; the SDK handles image quality detection and direct upload to Socure's service.
Listen for the SDK success callback indicating document capture and upload is complete; do not attempt to transmit raw document images through your own backend.
Configure a webhook endpoint in the Socure dashboard to receive the evaluation_completed event; the payload contains the DocV decision, extracted data fields, and forensic signal scores.
Map the response signals — such as documentScore, faceMatch, and extracted fields like firstName, dateOfBirth, and documentNumber — to your onboarding decisioning logic.
Test edge cases in the Socure sandbox using provided test document sets before promoting to the live environment.
Known gotchas
The transaction token is single-use and short-lived; if the user abandons the capture flow, you must request a new token before retrying rather than reusing the original.
Socure DocV is a standalone product but also integrates with Socure ID+ for combined document, selfie, and database verification; purchasing only DocV will not include the SSN or address database checks.
Webhook payloads must be validated using the Socure-provided HMAC signature header; processing unauthenticated payloads risks accepting spoofed verification results.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp