Guides
Going Live checklist
Everything to check before you take real payments.
This checklist takes your app from Test mode to Live mode. Each mode has its own app ID, keys, catalog, webhook URL and data, so most of what you set up in Test mode doesn't carry over. Work through this list in Live mode before you take real payments.
1. Verify the team owner's email
Live mode works only once the team's owner has verified their email. Until then, Live requests return 403 with code email_unverified, and customers can't pay. Test mode works without it.
{
"code": "email_unverified",
"error": "the team owner must verify their email to use live"
}2. Choose how customers pay
In Live mode, your app takes payments through your own MeSomb, pawaPay, Notch Pay, Flutterwave or Fapshi account. In the dashboard, connect it as a Live account on your team's Provider accounts page. Then, in Live mode, open your app's Settings, then Payments, click Choose account, and pick it. You can also click Connect a new account there.
Provider accounts belong to your team, so several apps can use the same one. If another of your apps already uses a Live account, you can choose it here too, and its provider webhook URL is the same.
No provider account? Choose Abuna payments in the same Payments settings instead. Abuna collects the money for a 3.5% fee and pays it out to your mobile money number each morning, so you can skip the rest of this step and step 3. See Abuna payments.
Use production credentials. If you tested with your provider's sandbox, those credentials don't work here: Notch Pay sandbox keys and Flutterwave test keys fail with code provider_live_credentials_required, and pawaPay refuses a sandbox token with provider_credentials_rejected. pawaPay creates a token only once a callback URL is set, so set a temporary one first, then replace it in step 3.
For MeSomb, connect an application MeSomb has approved for live payments. MeSomb uses the same keys in test mode, so Abuna can't catch the wrong one. A Live account with an application still in test mode collects no money, and Live mode refuses MeSomb's test numbers. Leave the Webhook signing secret empty for now: you add it in step 3.
For Fapshi, connect your collection service's live keys, and make sure Fapshi has turned on Direct Pay for your account. Until it does, Fapshi refuses your Live payments. See Get your credentials.
Until your app uses a provider account or Abuna payments in Live mode, checkouts and payments return 422 with code not_accepting_payments.
{
"code": "not_accepting_payments",
"error": "this app isn't accepting payments yet"
}See Connecting a payment provider for the credentials each provider needs.
3. Set the provider webhook URL
This step is required with your own provider account. After you connect, the account shows a Provider webhook URL. Paste it into your provider's dashboard, so payments update as soon as customers approve them. Until it's set, payments may not update in Abuna, and paid invoices can stay open.
- MeSomb: open Developer settings, add a webhook with the URL, and copy its signing secret. MeSomb shows it only once. In Abuna, choose Replace keys on the account and paste it as the Webhook signing secret. With it, MeSomb payments confirm within seconds. Until then, they still confirm on their own, usually within the hour, but some can take several hours.
- pawaPay: open System configuration, then Callback URLs, and paste it as the Deposits callback URL, in place of the temporary one.
- Notch Pay: open Settings, then Webhooks, add a webhook with the URL, and turn on the payment events. If Notch Pay then shows a different hash key for the webhook, enter it in Abuna as the Webhook hash key.
- Flutterwave: open Settings, then Webhooks, paste the URL, and enter the same Secret hash you entered in Abuna. Tick Enable webhook retries and Enable webhook for failed transactions, then save.
- Fapshi: open Developers, then your collection service. Paste the URL as its webhook URL, enter the same Webhook secret you entered in Abuna, and save.
Then, on the account, tick I've added this URL in your provider. For MeSomb, saving the signing secret does this for you. No payment is needed: once this step and steps 1, 2, and 4 are done, the dashboard opens your app in Live mode. Your first real payment (step 10) brings the first update from your provider. See Set the provider webhook URL.
4. Add a support contact
Your app takes Live payments only once it has a support email or a support URL. In the dashboard, open Settings, then General, and fill in Customer support. Test and Live share it. Until it's set, checkouts and pay links return 422 with code not_accepting_payments.
While there's no support contact, nobody is canceled for not paying, and renewal invoices stay open. Once you add one, customers with an unpaid renewal get their full days to pay from that moment.
5. Switch to your Live app ID and key
Your server picks the mode by the app ID in the path and the key it sends. Change both together: the Live app ID, and a secret key that starts with sk_live_.
curl https://api.abuna.app/v1/apps/Q7mKp2Rt/products \
-H "Authorization: Bearer sk_live_..."- Abuna shows a secret key once, when it's created. A team owner can create more keys under Settings, API keys, and revoke one that leaks.
- Keep secret keys on your server. Never put them in a browser or mobile app.
6. Create your products and prices in Live mode
Live mode starts empty. Create your products and prices again in Live mode, and store their Live IDs. Test IDs don't exist in Live mode.
Or copy them from Test: in the dashboard, open Products in Test mode, or use the API. See Copy products from Test to Live.
7. Set up your Live webhook URL
Each mode has its own webhook URL: Live mode doesn't copy yours from Test. In Live mode, open Webhooks and set the Webhook URL. It must be a public https URL.
- Use the Live signing secret, which starts with
whsec_live_. Your Test secret won't verify Live events. - Verify
X-Abuna-Signatureon every request, accept anyv1that matches, and reject atmore than 300 seconds off. - Click Send test event and check that your server answers
2xx. - If one server handles both modes, route on
environmentin the signed body, not only on theX-Abuna-Environmentheader.
See Receiving webhooks for the full setup.
8. Check your Live settings
Your app's name, support contact, and terms URL are shared by both modes. Its redirect URLs, days to pay and webhook URL are set per mode. In Live mode, open Settings, then General:
- Customer support: a support email or URL, required before your app takes Live payments. It appears in every customer email, and on your hosted checkout, pay links, and customer portal.
- Redirect URLs: where the hosted checkout sends customers back. Each one must be an absolute
httpsURL. Thesuccess_urlandcancel_urlyou pass to a checkout session must behttpsin Live mode too. AlocalhostURL that worked in Test mode returns422. - Renewals and days to pay: how many days before a paid period ends the renewal invoice goes out (0 to 7, 3 by default). And how many days customers have to pay a renewal, from 1 to 14. If a renewal is still unpaid after that, Abuna cancels the subscription and tells the customer. Both apply to invoices issued after you change them.
- When customers cancel: whether a customer who cancels in the customer portal keeps the subscription until the end of the paid period (the default) or loses it right away. Test and Live mode each have their own setting.
9. Check your team's plan
Only Live mode counts toward your team's plan. The Free plan allows 20 subscribers and 1 app, and the Free teams you created share that app. At the limit, new customers can't subscribe, and your checkout tells them you aren't taking new subscribers. If you expect more, move to a bigger plan before you launch.
10. Make one real payment
Subscribe to your own product with a small price, through a checkout session, and pay it with your own mobile money wallet. Check that you get the receipt email, that your server receives session.completed, invoice.paid, and subscription.paid, and that the money reaches your provider account. The Payments page should then say Receiving updates. With Abuna payments, the money reaches your mobile money number with the next morning's payout, once your balance is above FCFA 100.
Next steps
- Connecting a payment providerConnect your own MeSomb, pawaPay, Notch Pay, Flutterwave or Fapshi account, or use Abuna payments.
- Receiving webhooksReceive events on your server and verify that Abuna sent them.
- Plans and limitsWhat each Abuna plan includes, and what happens when you go over a limit.
- Test mode and Live modeBuild against Test data with the Abuna simulator or provider sandboxes, then switch to Live with the same code.