> For the complete documentation index, see [llms.txt](https://coindisco.gitbook.io/coindisco/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coindisco.gitbook.io/coindisco/getting-started/production-access.md).

# Production access

## Production access

Production access lets you use Coindisco with real users, real providers, and real transactions.

Before production becomes available, you need to complete verification and sign the service agreement.

### How production access works

To unlock production, complete these steps:

1. Submit the application form.
2. Complete KYB verification.
3. Wait for the service agreement.
4. Sign the service agreement.
5. Switch from sandbox to production.

Until these steps are complete, you can continue testing in sandbox mode.

### Step 1: Start verification

Open the dashboard and click **Start verification** or **Verify**.

The dashboard shows the activation steps required to unlock production access.

<figure><img src="/files/QjkcCpnv7Sy0ORiisizw" alt=""><figcaption></figcaption></figure>

### Step 2: Complete KYB in Sumsub

After clicking verification, you are redirected to Sumsub.

Sumsub is the verification provider used by Coindisco.

Follow the instructions and submit the required business information and documents.

<figure><img src="/files/fAcJXJz2yEkZtiP07R1c" alt=""><figcaption></figcaption></figure>

When verification is completed, Sumsub shows a confirmation message. You can close the page and return to the Coindisco dashboard.

### Step 3: Wait for approval

After KYB is approved, Coindisco prepares your service agreement.

During this step, you can still use sandbox mode and continue testing your integration.

<figure><img src="/files/mzLN44H9xN7wG3czluK9" alt=""><figcaption></figcaption></figure>

### Step 4: Sign the service agreement

When the agreement is ready, the dashboard shows **Sign service agreement**.

Open the agreement and sign it.

Signing the agreement is required before production access can be enabled.

<figure><img src="/files/NxDF3wCndbHseEDrLcJj" alt=""><figcaption></figcaption></figure>

### Step 5: Switch to production

After KYB is approved and the agreement is signed, production access becomes available.

Use the dashboard switcher to turn off sandbox mode and switch to production.

In production mode, you can use:

* production widget URLs;
* production API environment and public keys;
* production webhooks;
* monitor live transactions activity.

Production transactions are real.

<figure><img src="/files/LJCIJEygqZ91zaz3Eqbo" alt=""><figcaption></figcaption></figure>

### Sandbox vs production

| Mode       | What it is for           | Transactions | Keys            |
| ---------- | ------------------------ | ------------ | --------------- |
| Sandbox    | Testing the integration  | Simulated    | Sandbox keys    |
| Production | Launching for real users | Real         | Production keys |

Always test your widget, API, and webhooks in sandbox before switching to production.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://coindisco.gitbook.io/coindisco/getting-started/production-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
