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.
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 and Information we collect.
- Deposit instructions. See Deposit instruction labels.
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.
3. Request production access
Open a request using the Meridian Help Center request form. 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.
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.- Production setup. Meridian configures your program, registers your webhook endpoints, allowlists your IP addresses, and sets up settlement reporting.
- Smoke test. Meridian confirms the configuration with its own test customers: webhooks are delivered to your receivers, and a test payout completes.
- Solutions Engineering sign-off. Your Solutions Engineer confirms the setup with Meridian’s teams and approves credential release.
- 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.