Nexra
Start in the sandbox
All connectors

MTN MoMo

Mobile money

Connect MTN MoMo to the rest of your business, with the right person approving what changes and a record of every action.

8 ways to read, 5 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
MTN MoMo with Nexra

Connected, approved, proven.

The things teams do most with MTN MoMo, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Deposit to a walletdisbursement_deposits.createApproval by rule
  • Refund a paymentdisbursement_refunds.createApproval by rule
  • Get collections balancecollection_balances.getRead

Example flow

  1. MTN MoMo · Get collections balancecollection_balances.getDone
  2. MTN MoMo · Deposit to a walletdisbursement_deposits.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches MTN MoMo.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to MTN MoMo
  • MTN MoMo's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect a MTN test account before you go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

MTN MoMo Open API: request payments from customers' phones, check payment, payout, deposit, refund and remittance status, and read balances; governed payouts, deposits, refunds and remittances.

MTN API docs
Source actions
8
Destination actions
5
Data types
8

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

collection balances1
  • Get collections balanceSource

    The available balance of your MTN MoMo collections account.

disbursement balances1
  • Get disbursements balanceSource

    The available balance of your MTN MoMo disbursements account.

disbursement deposits2
  • Deposit to a walletDestinationNot retried automaticallyApproval before production

    Deposits money into a MoMo wallet from your disbursement account. Moves money: governed exactly like other payouts.

  • Get deposit statusSource

    Whether a deposit is pending, successful or failed, with MTN's transaction ID. Use it to confirm a payment before booking it.

disbursement refunds2
  • Refund a paymentDestinationNot retried automaticallyApproval before production

    Refunds a successful collection back to the payer from your disbursement account. Moves money: governed exactly like other refunds.

  • Get refund statusSource

    Whether a refund is pending, successful or failed, with MTN's transaction ID. Use it to confirm a payment before booking it.

disbursement transfers2
  • Send a payoutDestinationNot retried automaticallyApproval before production

    Pays a MoMo wallet from your disbursement account. Moves money: governed exactly like other payouts.

  • Get payout statusSource

    Whether a payout is pending, successful or failed, with MTN's transaction ID. Use it to confirm a payment before booking it.

payment requests2
  • Request a paymentDestinationNot retried automaticallyApproval before production

    Sends a payment prompt to the customer's phone. Money moves only when the customer approves it with their MoMo PIN.

  • Get payment request statusSource

    Whether a payment request is pending, successful or failed, with MTN's transaction ID. Use it to confirm a payment before booking it.

remittance balances1
  • Get remittances balanceSource

    The available balance of your MTN MoMo remittances account.

remittance transfers2
  • Send a remittanceDestinationNot retried automaticallyApproval before production

    Sends an international remittance to a MoMo wallet from your remittance account. Moves money: governed exactly like other payouts.

  • Get remittance statusSource

    Whether a remittance is pending, successful or failed, with MTN's transaction ID. Use it to confirm a payment before booking it.

Access and limits

Authentication
MTN MoMo subscription keys, API user and API key per product
Plans and access
An MTN MoMo developer account with a product subscription (Collections, Disbursements or Remittances) per product you use. Live access is granted per country through MTN's go-live process. Disbursements and remittances need MTN to allow your server addresses.
Test environment
Subscribe to the products on momodeveloper.mtn.com, then create a sandbox API user and API key with MTN's provisioning API. The sandbox uses EUR and moves no real money.
Rate limits
MTN does not publish rate limits. HTTP 429 and Retry-After are honoured with bounded retries.
Pagination
MTN MoMo has no list endpoints: every payment is read by its reference ID.
Provider events
MTN sends one unsigned callback (PUT or POST) with the final status to the X-Callback-Url of each request, on the callback host registered for the API user. There are no retries. Flows can start the moment something happens: when an MTN MoMo payment or payout succeeds; when an MTN MoMo payment or payout fails.

Before you build a flow

  • Money movement is customer-governed: payouts, deposits, refunds and remittances are the highest risk tier and are refused until money movement is switched on for the workspace and the action, with approvals and limits.
  • Payment requests ask the customer to approve on their phone; nothing moves without their PIN.
  • Payouts and settlements: MTN MoMo has no settlement or payout batch API; each payout is read by its reference ID.
  • Refunds: refunds are made and read through the disbursement product.
  • Disputes: MTN MoMo publishes no dispute API.
  • Fees: MTN MoMo reports no fee on a payment's status; fees appear only on MTN's own statements.
  • MTN MoMo has no list or date-filtered reads. Reconciliation looks up each payment by the reference ID your ledger records, and the MTN MoMo trigger delivers results as they happen.
  • Callbacks are sent once and are not signed: confirm a payment with Get payment request status before booking it.
  • Phone numbers and e-mail addresses are masked in every result. Account-holder checks are not offered because MTN puts the phone number in the URL.
  • MTN MoMo PSB in Nigeria is a separate service and is not covered by this connector.

Developer reference

  1. Create the MTN credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose MTN MoMo, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
MTN docsAPI referenceMTN docsAuthenticationMTN docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/mtn-momo and the Connections API.