DocV Sandbox Testing
How Sandbox works:
- Sandbox returns predefined DocV results; it does not run full production models.
- If you do not pass a
transaction_token, DocV returns Accept with static fields and reason codes, regardless of the images captured. - To retrieve images in Sandbox, include the Socure Image Request enrichment and add a WAIT (10 seconds) transformation step before it. Without the wait, downloads often return
400 "No Documents Found".
Sandbox environment
Point your integration at the Sandbox base URL and use a Sandbox API key:
| Resource | URL |
|---|---|
| Evaluation endpoint | https://riskos.sandbox.socure.com/api/evaluation |
| Download documents | https://riskos.sandbox.socure.com/api/evaluation/{eval_id}/documents |
For Sandbox testing, confirm your workflow steps are in this order:
Input → Document Request → Document Verification → WAIT (10s) → Image Request → Decision Logic → Decision
The WAIT (10s) step is required in Sandbox to ensure images are available for download.
Troubleshooting
| Symptom | Cause | Resolution |
|---|---|---|
| Always Accept | No transaction_token was passed. |
Expected. Add a token from the table above to simulate other outcomes. |
| 401 / 403 | Wrong key or base URL. | Use your Sandbox API key and the Sandbox base URL. |
| 400 "No Documents Found" on download | Missing image step. | Ensure the Socure Image Request enrichment exists and a WAIT (10s) step precedes it. Confirm the correct eval_id. |
| Workflow never completes | Missing DocV steps or error handling. | Verify DocV steps are present and that error handling returns resubmit or cancel. |
Verification checklist
Confirm each step of your integration in Sandbox:
- Evaluation creation returns
decision: "REVIEW",status: "ON_HOLD",eval_status: "evaluation_paused", and aSocureDocRequestenrichment. - Your backend extracts and stores the
eval_idanddocvTransactionToken. - Verification launches (SDK or Hosted Flows) and presents the correct flow.
- Capture completes and your endpoint receives
case_notes_addedprogress events. - Your endpoint receives the
evaluation_completedevent with a final decision. - Your application routes correctly on
ACCEPT,REJECT, andREVIEWdecisions.