capabilities.work

DocV Verify And Poll

A 5-step recipe with Socure. We can help you get access.

Recipe · 5 steps

DocV Verify And Poll

with Socure

Run a full DocV transaction from creation through a polled decision.

  1. Create a DocV transaction by passing the docvTransaction module, returning the transaction id and the hosted session URL.
  2. Upload the captured document image against the device for this transaction.
  3. Upload the selfie image against the device so liveness and face match can be evaluated.
  4. Finalize the transaction to trigger document and selfie verification.
  5. Retrieve the transaction and confirm a terminal decision value has been produced; loop back if the decision is not yet present.
What you'll need to have ready
  • apiKey: Socure API key presented as `SocureApiKey <api-key>`.
  • deviceId: Device identifier the captured images are uploaded against.
  • documentType: Document type to verify (license, passport, or residence_permit).
  • documentUploadType: Upload image type for the document (license_front, license_back, passport, or residence_permit).
  • documentImage: Binary document image to upload.
  • selfieImage: Binary selfie image to upload for liveness and face match.
  • country: Issuing country of the document.
  • webhookUrl: Optional callback URL for DocV session lifecycle events.
For your developer

Arazzo workflow socure:docv-verify-and-poll, 5 operations: createDocvTransaction → uploadDocvDocument → uploadDocvDocument → verifyDocvDocument → getDocvTransaction. Specs on APIs.io.

More recipes with Socure

Bank Account OnboardingContact Risk Then DecisionDocV Then IdentityFraud And Device Risk ScreenIdentity Decision BranchKYC Watchlist EnrollMonitoring OffboardWatchlist Alert Triage