> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gnosispay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sandbox vs Production

> How the sandbox and production environments differ, how to get access, and what you need for each integration type.

Gnosis Pay has two separate environments: **sandbox** for building and testing, and **production** for real users, real cards, and real money. Each environment has its own credentials, data, and base URLs, and nothing carries over between them.

## Sandbox

Sandbox is open to any team building with Gnosis Pay, whether you're exploring the stack for the first time, building a proof of concept, or running a testing phase before launch.

To get access, [contact our team](https://form.typeform.com/to/naN3irHW?typeform-source=gnosispay.com). We'll send you an invitation to the sandbox Partner Dashboard, where you set up your credentials and start integrating.

### What you can test in sandbox

> [accordion] KYC outcomes
>
> Identity verification runs against Sumsub's sandbox, so you can go through the full flow with Sumsub's test templates, without real personal data or waiting for manual review. Test every outcome your integration needs to handle: approved, resubmission requested, manual review, and rejected.
>
> See [KYC Statuses](https://docs.gnosispay.com/concepts/kyc/kyc-statuses.md) for the full list of statuses, and the [KYC testing guide](https://docs.gnosispay.com/embedded-integration/onboarding.md#3-kyc-process) for step-by-step instructions.

> [accordion] Card transactions
>
> The [transaction simulator](https://docs.gnosispay.com/embedded-integration/cards/card-simulator.md) lets you create card transactions in different states, including authorizations, declines, refunds, and reversals, without a live card network. Use it to test transaction handling, webhooks, and UI states end to end before any real card or money is involved.

## Production

Production access requires a partnership agreement with Gnosis Pay. Production credentials are not self-serve.

As part of onboarding, the Gnosis Pay team sets up:

* Access to the production [Partner Dashboard](https://partners.gnosispay.com) and production APIs
* Production credentials for your integration
* The domain configuration your integration type needs (see below)

> [!WARNING]
>
> Ready to move from sandbox to production? [Contact sales](https://form.typeform.com/to/naN3irHW?typeform-source=gnosispay.com) to start the partnership process.

## Comparison

| | Sandbox | Production |
| - | - | - |
| **Access** | Any team, on request | Partners with a signed agreement |
| **Credentials** | Sandbox only | Production only, issued during onboarding |
| **Card activity** | Simulated, with no live card network | Real transactions on the card network |
| **KYC** | Sumsub sandbox with test documents | Sumsub production with real documents |
| **Data** | Test data only | Real users and funds |

## What you need for setting up environment for platform server side integration

The setup differs depending on how you integrate. If you haven't chosen yet, see [Integration types](https://docs.gnosispay.com/concepts/integration-types).

> [tab] Platform Integration
>
> Your backend connects server-to-server through the Partner API. In each environment you need:
>
> * An OAuth token URL, client ID, and client secret, stored only on your backend
> * An HTTPS endpoint to receive webhooks
> * A durable mapping between your user IDs and the IDs Gnosis Pay returns
> * A Safe owner address and chain for each account you create
> * Separate approval before you handle sensitive card data, such as card numbers and CVVs, directly

## Base URLs

Each environment has two base URLs:

| Environment | Authentication | Partner API |
| - | - | - |
| Sandbox | `https://core.sandbox.gnosispay.in` | `https://core.sandbox.gnosispay.in/core` |
| Production | `https://api.gnosispay.com` | `https://api.gnosispay.com/core` |

For example, the sandbox token endpoint is `https://core.sandbox.gnosispay.in/oauth/token`. See [Authenticate your backend](https://docs.gnosispay.com/platform-integration/onboarding/authentication.md).

> [!TIP]
>
> Keep the base URL and credentials in configuration rather than in code, so switching from sandbox to production is a config change, not a code change.

> [!NOTE]
>
> Every endpoint in these docs includes **Sandbox** and **Production** request examples. Switch between them with the tabs on each code block.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.