For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
API StatusPartner Portal
HomeGuidesAPI ExplorerSDKsGitHubSupport
HomeGuidesAPI ExplorerSDKsGitHubSupport
  • Introduction
    • Welcome to Monite
    • Monite account structure
    • Postman collections
    • Support
  • Get started
    • Step 1. Get your credentials
    • Step 2. Implement server side
      • Glossary
      • Supported currencies
      • MoniteScript
      • Go-live checklist
      • GDPR DSR
LogoLogo
API StatusPartner Portal
References

Go-live checklist

Follow the steps below to ensure you are ready to go live with Monite.
Was this page helpful?
Previous

GDPR Data Subject Rights

Next
Built with

If you have tested your integration in Sandbox and want to go live with Monite, please ensure that you have implemented all necessary controls and meet all the requirements from Monite.

Below is a high-level checklist that should help you make your launch with Monite as smooth as possible:

  • You have a signed contract with Monite, whose content matches your real use cases, agreed pricing, responsibilities, and liabilities.
  • You implemented an authentication system for your users, and call Monite API either from your backend using the partner token, or from your client code using entity user tokens.
  • You have a working and tested integration that currently connects to the Sandbox Monite API (https://api.sandbox.monite.com/v1) using your company account created with the Sandbox Partner Portal.
  • You created a new company account using the Production Partner Portal (either EU or US) and invited relevant people from your organization, assigning them appropriate roles.
  • You created a new pair of API client ID and client secret, and store this secret securely on your side.
  • You have a production environment of your product which connects to https://api.monite.com/v1 (or https://us.api.monite.com/v1), not to https://api.sandbox.monite.com/v1.
  • You set up production webhooks for important asynchronous flows, if you have such flows expected in your integration.
  • You set up a unique mailbox domain for the production environment, different from the one used in the sandbox, to prevent conflicts and ensure proper management of production communications.
  • You updated your Privacy Policy and Terms of Service to include relevant information about Monite services, if necessary.
  • (Optional) You’ve shared your staging environment with Monite, where Monite QA and Security engineers can run their tests and provide you with their findings.
  • You informed Monite at least 5 days in advance about the date you are planning to go live, including specific hours, expected system load (number of users or required resources), countries, and any other information that might be important to monitor.
  • You have your own logging and monitoring system in place, which helps you debug production issues when needed.
  • You are familiar with Monite tech support levels and incident escalation, as described in Support.
  • You go live and let Monite know about the results.

We try to make this list as complete as possible. However, there might be more different tasks that are specific for your integration and use cases. To clarify them, please contact your Account Manager at Monite.