> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.id.me/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.id.me/_mcp/server.

# Launching in production

> Learn more about launching in production

Learn how to make a smooth transition from development to production. Whether you're launching a new integration or updating an existing one, this section covers everything you need to prepare for a successful deployment.

## Migrating from sandbox

This section will cover the ID.me sandbox environment and the key variables that must be tested prior to switching to production.

### Sandbox environments

ID.me offers sandbox environments that allow developers to test integrations before going live. These environments simulate production behavior and help ensure your application is functioning as expected.

#### Sandbox for credential validation

When you create an [ID.me developer account](https://api.id.me/en/session/new), it automatically defaults to the credential validation sandbox environment. This
allows you to test:

* [OAuth 2.0](/guides/o-auth-2-0/overview)
* [OpenID Connect](/guides/oidc/overview)
* [SAML](/guides/saml/overview)-based credential validation flows

For integration details, see the [OAuth 2.0 guide](/guides/o-auth-2-0/overview).

**Test credentials**

By default, you will be able to verify using the test user assigned during your account creation. If you need additional test credentials for a specific group, contact your ID.me solution consultant or email [partnersupport@id.me](mailto:partnersupport@id.me).

#### Sandbox for identity verification

This is an additional environment for testing identity verification workflows such as:

* [Knowledge-based authentication (KBA)](/guides/learn-more/digital-wallet/knowledge-based-authentication) replacement
* [Fortified identity](/guides/learn-more/digital-wallet/fortified-identity)
* [eRx / EPCS](https://www.id.me/business/epcs)

**Test credentials**

Work with your ID.me solution consultant or email [partnersupport@id.me](mailto:partnersupport@id.me) to request access. Once granted, you can test user accounts that allow you to walk through the entire verification process. You may:

* Use any fake or real email to create an account
* Upload any image file between 40 KB and 16 MB (real identification documents are not required)

### Testing your sandbox integration

Before requesting production access, please complete the following to ensure your integration is fully functional:

* The user can verify through the **authorization endpoint** (like the "Verify with ID.me" button)
* The **authorization code** is successfully captured by the client
* The **authorization code** is exchanged for an **access token**
* The **access token** is captured and stored by your backend
* The **access token** is exchanged for **user attributes** via the **attribute endpoint**
* The **JSON payload** is stored properly (such as in your CRM or database)
* The user is redirected to a confirmation page with success messaging
* The integration follows ID.me's [brand guidelines](/brand-assets/brand-assets/brand-guidelines)

> **Note**
>
> This checklist reflects the OAuth 2.0 authorization code (explicit) flow. If you are using OpenID Connect, an OAuth implicit flow, or an ID.me-hosted landing page, the checklist may vary. Please reach out to your ID.me solution consultant for more information.

## Enabling production mode

Once your [End-to-end walkthrough](/integrations/deploy-and-monitor/quality-assurance-testing) session is complete and approved, your ID.me solution consultant will enable production access. You will receive an email confirmation once your environment is live and ready to process credential validations.

### Credential validation

If you are integrating with ID.me for **credential validation**, you can begin validating users in production immediately after receiving confirmation. No additional setup is required beyond what was tested in your sandbox.

### Identity verification

For **identity verification**, you will need to update your configuration after receiving production access to the following values:

#### OAuth 2.0 integrations

* Authorization endpoint
* Token endpoint
* Attribute endpoint

#### OpenID Connect integrations

* Authorization endpoint
* Token endpoint
* Attributes endpoint
* Well-known endpoint

Also ensure you have updated your:

* **Client ID**
* **Client Secret**

> **Important**
>
> These credentials **MUST** match those assigned to your production application in the [ID.me developer dashboard](https://api.id.me/en/session/new)