## Milestone 1: Setup & Preparation

Review the fundamentals of [Socure API requests and responses](https://help.socure.com/riskos/reference) to ensure proper integration.

**Access and manage your credentials** (API and SDK Keys) in the [RiskOS™ Dashboard](https://help.socure.com/riskos/docs/integration-guide-authentication).

Follow the [Integrating with RiskOS™ guide](https://help.socure.com/riskos/docs/integrating-with-riskos) to send an example request.

Learn how to [create and manage users in RiskOS™](https://help.socure.com/riskos/docs/manage-users) as a self-serve process to ensure correct [role permissions](https://help.socure.com/riskos/docs/users-and-roles-overview).

Identify **mandatory inputs** required for your specific workflow and coordinate with your Socure team to finalize configurations.

## Milestone 2: Implementation & Configuration

**Workflow integration**:

Begin triggering workflows using the [RiskOS™ Evaluation API](https://help.socure.com/riskos/reference/postevaluation) within your application logic.

Implement **error handling and retry logic**.

_Add exponential backoff for temporary errors (429, 500, 502). Review our [documentation on best practices for error handling and interpreting API error responses](https://help.socure.com/riskos/reference/errors)._  
Complete **PII data mapping**: Discuss with Socure the PII inputs you will be sending (for example, SSN, DOB, or IP address).

**Webhooks**:

Configure [webhook endpoints](https://help.socure.com/riskos/docs/webhooks) and subscribe to the relevant [Event Subscription Types](https://help.socure.com/riskos/docs/webhook-events) for real-time updates.

Integrate [Watchlist Monitoring webhooks](https://help.socure.com/riskos/docs/watchlist-webhooks-overview) (if applicable) to receive alerts for ongoing monitoring events.

**SDK integration**:

_(Applicable if implementing the Digital Intelligence and/or Document Verification SDK.)_

Set up the [Predictive Document Verification (DocV) SDK](https://help.socure.com/riskos/docs/docv-sdks) in your mobile or web application.

Integrate with the [Digital Intelligence SDK](https://help.socure.com/riskos/docs/digital-intelligence-sdks) to receive device and behavioral signals.

**Testing & validation**:

Perform **integration testing in Sandbox** using test data to validate logic before certification.

**Product settings**:

Confirm [Product Settings](https://help.socure.com/riskos/docs/product-settings) for KYC, DocV, and Watchlist.

**Case Management**:

RiskOS™ includes a comprehensive **Case Management** solution with [GenAI Explainability](https://help.socure.com/riskos/docs/genai-explainability). Learn how to use [Case Management](https://help.socure.com/riskos/docs/case-management-overview) and a [case review process](https://help.socure.com/riskos/docs/case-review-process).

## Milestone 3: Certification

**SDK certification**:

Participate in a **live SDK certification demo** with a Socure Developer Support Engineer for final sign-off.

**Sandbox workflow certification**:

Perform **Sandbox workflow certification**: Send the `eval_id`s of at least 3 transactions that match your production formatting.

**Test webhook connectivity** by performing a manual decision in the RiskOS™ Dashboard to confirm the `updated_decisions` trigger.

**TPS rate limit**:

Confirm the **10 TPS rate limit** is sufficient.

_The TPS is set at our default 10 TPS. Should you expect a surge in volumes requiring additional TPS, please inform us at least one week in advance to coordinate scaling. A commercial discussion may be required for rate increases._  
**Storage requirements**:

Ensure the response parameters `eval_id`, `scores`, and `reasonCodes` are stored locally for all evaluations in which Socure is called.

_Note that Socure is not a system of record for long-term data retention and stores data only for the period specified in your contract._

**Status page and feedback mechanisms**:

Subscribe to the [Socure status page](https://status.socure.com/) for real-time monitoring of verifications and API metrics.

Send feedback data for all transactions to improve fraud capture rates via [Feedback API](https://help.socure.com/riskos/reference/feedbackapi), [Feedback CSV import](https://help.socure.com/riskos/reference/feedbackupdatecsv), or [Manual Feedback](https://help.socure.com/riskos/docs/case-management-fraud-feedback).

**Release notes**:

Review the latest [Release Notes](https://help.socure.com/riskos/page/latest-updates) to stay informed about product updates and enhancements.

## Milestone 4: Production Validation

Once your integration is certified in the Sandbox environment, follow these steps to complete production validation and confirm connectivity with your downstream systems before launch.

**Production validation**:

Change your API Key and Bearer Token from Sandbox to your Production environment credentials.

Ensure your application is pointing to the Production URLs:

- _Production API endpoint:_`https://riskos.socure.com/api/evaluation`
- _Production RiskOS™ Dashboard:_ [https://riskos.socure.com](https://riskos.socure.com/)

Retrieve your [Production API and SDK Keys](https://help.socure.com/riskos/docs/integration-guide-authentication) from the RiskOS™ Dashboard.

Set up all webhooks in the Production environment.

_Note: You must configure [Watchlist webhooks](https://help.socure.com/riskos/docs/watchlist-webhooks-overview) to successfully activate Watchlist Monitoring._

Review and configure your Production [Product Settings](https://help.socure.com/riskos/docs/product-settings) to match your specific business requirements.

Configure [Production IP Filtering](https://help.socure.com/riskos/docs/ip-filtering) (optional but recommended) for enhanced security.

Establish access to the **24/7 Support Department** via [support@socure.com](mailto:support@socure.com).

Request Socure to lift rate limits for **Production** traffic

## Milestone 5: Go Live & Hypercare

**Go Live & Hypercare**:

Launch with Production traffic.

Perform **Hypercare Monitoring**: Post-Go Live transaction monitoring for 14 days to ensure system stability.
