Go-live checklist¶

Do these checks before you sell MEGOGO subscriptions to your users. Each item has a link to the page that describes it.

Credentials and access¶

You have the production partner ID, the public key, the private key and the service IDs. See Credentials.
The private key is only on your servers.
MEGOGO added the IP addresses of your production servers to the list of the production partner ID. See Credentials.
Your team knows that it must send the new IP addresses to MEGOGO before a change of the servers. See Operations.

Your code gives the URL of the worked example. See Sign a request.
Your system sends only phone numbers in the international format, digits only. See Activate a subscription.
Your system does not send subscriptions for numbers that can be wrong or new. It sends user/phone first.

You know the renewal mode of each service ID, and your system follows it. See Subscription lifecycle.
You bill the user only after "successful": true.
After subscribe, your system tells the user how to sign in. See Activate a subscription.
When the user stops the subscription, your system sends unsubscribe with the service ID that subscriptions shows.
Your system sends resume only after its own suspend, and it does not send subscribe for a suspended subscription. See Renew, suspend and stop.
Before a retry of subscribe or resume, your system gets subscriptions. See Retries.
Your system reads the code at the end of message, not the text. See Error catalog.
Your system compares its data with subscriptions regularly. See Reconciliation.

Do the full path with the production credentials and the phone number of a test SIM card:

subscribe for the number.
Sign in to a MEGOGO application with the number. A video of the subscription plays.
unsubscribe for the number. subscriptions gives [].

Guide version 1.0.0, 2026-11-02 · Report a problem on this page