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

# Go live

> The reviews to complete, what to finish in Sandbox, what to send Meridian, and what happens before Meridian issues your production credentials.

Production access is a gated step. Meridian reviews your designs. You finish and sign off your Sandbox integration, then send Meridian your production details. Meridian sets up and verifies your program before issuing production credentials. This page lists every step and who owns it.

**1. Share your designs for review**

Share your UX designs at kickoff for Meridian's UX, risk, and legal reviews.

**2. Sign off Sandbox**

Run your full test plan in Sandbox and confirm every case passed.

**3. Request production access**

Open a support request with your production details.

**4. Meridian sets up and verifies your program**

Meridian configures production, runs its own checks, then issues your credentials.

**5. Verify in production**

Run an agreed set of live test cases with Meridian on call, then launch.

## 1. Share your designs for review

Once your project kicks off, share your UX designs with your Solutions Engineer. Meridian runs three reviews, and all three must be complete before it issues production credentials. Share designs early, before you build, so changes are easy to make.

| Review | What Meridian looks at |
| :- | :- |
| UX | How you present enrollment fields and deposit instructions |
| Risk | How you collect customer and owner details and documents, and how you show a deposit held for review |
| Legal | Your terms and privacy policy, and how your customers accept them at sign-up |

Include every place these appear: app screens, marketing materials, and emails. Share each one as it is ready.

Your app owns the user experience, so the API returns the official labels to use in it. Show these labels wherever you present enrollment fields or account details, such as deposit instructions:

* **Enrollment fields.** See [Field labels](https://docs.mnai.com/products/meridian-accounts/guides/onboarding-your-customer.md#field-labels) and [Information we collect](https://docs.mnai.com/products/meridian-accounts/guides/kyb-information.md).
* **Deposit instructions.** See [Deposit instruction labels](https://docs.mnai.com/products/meridian-accounts/guides/displaying-account-information.md#deposit-instruction-labels).

Meridian accepts design file links, screenshots, PDFs, and screen recordings. Your Solutions Engineer returns feedback from each team and confirms when all three reviews are complete.

## 2. Sign off Sandbox

Your assigned Solutions Engineer sends a Test Plan workbook with the detailed test cases. Complete it before Meridian issues production credentials. Test these areas in Sandbox:

* **Enrollments.** A customer that reaches `ACTIVE`, and one that is rejected.
* **Deposits.** A deposit that reaches the balance, and one held for review.
* **Payouts.** A payout that completes, one that fails, and a retry that does not pay twice.
* **Webhooks.** Every event you rely on, received and verified.
* **Settlement reports.** A review with your finance team.
* **Partner Portal.** A review with your operations team.

Confirm your sign-off in writing when you request production access.

## 3. Request production access

Open a request using the [Meridian Help Center request form](https://meridian.support.site/inbox/new). The form asks you to log in first.

On the form, set **Issue Area** to **Production Access**. In the body, confirm that Meridian has completed its design reviews and that you have signed off your Sandbox test cases and are ready for production. Include the details below. Missing details are the most common reason a request stalls.

| Detail | What to send |
| :- | :- |
| Organization name | Your legal organization name |
| Programs | Each program you are launching, with its routing policy, auto-sweep (`SWEEP`) or retain (`RETAIN`), the destination account for an auto-sweep program, and the currency pairs it supports, such as USD to PHP or USD to USDC |
| Production IP addresses | The addresses your servers call the API from, so Meridian can allowlist them |
| Webhook receivers | Either one URL for every event, which your system routes by the `X-Meridian-Resource-Type` and `X-Meridian-Event-Type` headers, or a separate URL for each event type. See [Configuration](https://docs.mnai.com/products/meridian-accounts/webhooks/webhooks-overview.md#configuration) |
| Settlement reports | The email address that should receive them |
| Partner Portal users | The name and email of each person who needs Partner Portal access in production |
| Testing window | The dates and times you plan to run your production verification tests |

Meridian's support team checks the request, confirms any missing details with you, and passes it to your Solutions Engineer.

## 4. Meridian sets up and verifies your program

This part is Meridian's. You will hear from your Solutions Engineer at each step, and nothing is needed from you unless a check turns up a gap.

1. **Production setup.** Meridian configures your program, registers your webhook endpoints, allowlists your IP addresses, and sets up settlement reporting.
2. **Smoke test.** Meridian confirms the configuration with its own test customers: webhooks are delivered to your receivers, and a test payout completes.
3. **Solutions Engineering sign-off.** Your Solutions Engineer confirms the setup with Meridian's teams and approves credential release.
4. **Credentials.** Your Solutions Engineer sends your production API key, secret, and Program ID, and your webhook API key and secret, through a secure one-time link, never over email or chat. Meridian issues credentials only after the UX, risk, and legal reviews are complete.

Production uses a different base URL from Sandbox. See [Base URLs](https://docs.mnai.com/products/meridian-accounts/api-reference.md#base-urls).

> [!WARNING]
>
> Production and Sandbox credentials are separate. A Sandbox key is never accepted in production, and your webhook API key and secret are issued separately from your API credentials.

## 5. Verify in production

Once you have credentials, Meridian schedules a testing session in the window from your request. Meridian's Engineering, Risk, and Solutions Engineering teams join the session to confirm your first production payments flow through correctly.

In the session, run a short set of live tests agreed with Meridian in advance. Onboard one real customer, receive one small deposit, make one small payout, and confirm the webhooks and your first settlement report arrive.

Confirm in the support request when your verification is complete. From then on, your account manager is your day-to-day contact, and the [Help Center](https://meridian.support.site) is the place for anything that needs Meridian's attention.
