As you move from the Sandbox testing environment to the Live Production environment, we want to make sure you cover all necessary technical and configuration steps.

Mamo’s Sandbox and Live environments are designed to work almost identically, so moving to Production is usually as simple as switching your API keys and updating your base URL.

If you built a custom API integration (or worked with a developer), take a moment to review the checklist below before going live.

This checklist outlines essential tests, alongside pro-tips and recommended best practices, derived from successful previous integrations.

These steps are essential to make sure you’re ready to start processing traffic and payments from the moment you go live.

You can also download this Go-live checklist for easier usage.

Sandbox testing and verification

Before switching to Production, ensure all payment flows have been fully simulated and passed in Sandbox.

Here's the Sandbox environment: https://sandbox.dev.business.com/

Flows to test

Successful payments
Failed payments
Refunds

→ Here's a complete list of test cases to be covered.

The sheet is AI-friendly; you can share it with your preferred AI tool to give you test cases.

Suggested AI prompt for test validation

You can paste this into your favorite AI assistant:

I am integrating Mamo's payment API in my Sandbox environment. Below is a list of test cases I need to validate.

For each test case:

Explain what I should simulate
Provide a working code example (API request or SDK call)
Add an assertion that verifies the expected outcome — don't just call the API, confirm it actually worked
Explain the expected response
Highlight common implementation mistakes
Suggest debugging steps if it fails

Then generate a test runner that executes all cases in sequence and prints a pass/fail summary with the failure reason for any test that does not pass.

Here are the test cases: [Paste test cases here]

The test cards needed for each scenario are included in the sheet above.

Assume I am using [Node.js / PHP / Python / etc.].

Keep everything practical, runnable, and implementation-focused. Where a test cannot be fully automated (e.g. Apple Pay, manual ops checks), explain the manual verification steps clearly instead.

UX and UI

Before launch, verify your checkout experience is production-ready.

Clean UI: Make sure your checkout page is frictionless, and Mamo is embedded on your website without redirection in way that aligns with your brand.
Mobile responsiveness: Test the full checkout experience on mobile devices to ensure everything looks clean and works without any redirects.
Error messaging: If a payment fails, customers should see clear, helpful messages (for example, “Payment declined”) instead of technical or raw JSON errors.

Security & API configuration

Secure API keys:

Make sure your Live API keys are stored securely, like in environment variables or a secrets manager, and never expose them in client-side code.
For detailed guidance, check out our best practices for storing your API key.

Get your Live credentials:

Log in to your Mamo Dashboard.
Navigate to the Developer section and select the Keys tab
Create and copy your Live API Key.

Update Base URL:

Switch all backend API calls from the Sandbox URL to the Production URL:

Prod Base URL: https://business.mamopay.com/

Apple Pay verification (web & app integration)

For web integration (Domain verification):

Make sure your production domain is verified for Apple Pay.
If you haven’t done this yet, email [email protected] to get the Apple Pay verification file.
Upload the file to your domain here:
https://your-domain.com/.well-known/apple-developer-merchantid-domain-association
Once the file is live, notify Mamo support so they can complete the verification.

For app integration (Direct verification):

Make sure you have a production Merchant ID.
Ensure your processing certificate is verified.

Webhook setup

Register your production webhooks:

Register your production webhook endpoints via API.
Make sure your server is ready to receive live events, such as charge.succeeded or charge.failed, at these URLs.

Verify webhook security:

Check that your endpoint validates the Authorization header (if auth_header was provided on POST /webhook) or confirms the request is coming from Mamo to prevent spoofing.