DocV Sandbox Testing
Validate your Predictive DocV integration in Sandbox using transaction tokens to simulate decisions, then run the verification checklist before going live.
Before you go live, validate your integration end to end in Sandbox. Sandbox lets you simulate specific DocV decisions and reason codes without using production data, so you can confirm each step of your integration behaves correctly.
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".
Testing real government-issued IDs:
Sandbox doesn't verify real documents — it returns predefined results regardless of the images you submit. To verify real IDs with full production models, use the Production environment. See the Go-Live Checklist.
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.
Simulate a specific decision
Sandbox returns predefined results. To force a specific outcome, pass a test docvTransactionToken value when you create the Document Request. If you omit the token, Sandbox always returns Accept.
Need more scenarios?
Your Socure team can add custom Sandbox tokens for edge cases. Contact your Solutions Consultant team.
Troubleshooting
| Symptom | Cause | Resolution |
|---|---|---|
| Always Accept | You didn't pass a transaction_token. | Expected. Add a token from Simulate a specific decision to force another outcome. |
| 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 a SocureDocRequest enrichment.
Your backend extracts and stores the eval_id and docvTransactionToken.
Verification launches (SDK or Hosted Flows) and presents the correct flow.
Capture completes and your endpoint receives case_notes_added progress events.
Your endpoint receives the evaluation_completed event with a final decision.
Your application routes correctly on ACCEPT, REJECT, and REVIEW decisions.
Related
Updated 9 days ago