Skip to content
Start in the sandbox
All connectors
Moniepoint · Monnify logo

Moniepoint · Monnify

Accounting, billing & payments

Keep Moniepoint · Monnify in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

29 ways to read, 3 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.
Moniepoint · Monnify with Nexra

Connected, approved, proven.

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

Top actions

  • Create invoiceinvoices.createApproval by rule
  • Create limit profilelimit_profiles.createApproval by rule
  • Get disbursement wallet balancewallet_balance.getRead

Example flow

  1. Moniepoint · Monnify · Get disbursement wallet balancewallet_balance.getDone
  2. Moniepoint · Monnify · Create invoiceinvoices.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 Moniepoint · Monnify.

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 Moniepoint · Monnify
  • Moniepoint · Monnify'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 Moniepoint · Monnify test account before you go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Nigeria: Monnify collections, invoices, reserved accounts, refunds, settlements, transfers, mandates, paycodes and bills catalogue (read); invoices and limit profiles (write).

Moniepoint · Monnify API docs
Source actions
29
Destination actions
3
Data types
22

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.

banks1
  • List banksSource

    Banks supported by Monnify, with USSD templates.

bill categories1
  • List biller categoriesSource

    Bills-payment categories (airtime, data, electricity, TV ...).

bill payments1
  • Get bill payment statusSource

    Re-query a bill payment by your reference (read only; Nexra never vends bills).

biller products1
  • List biller productsSource

    Products (bundles, plans, fixed amounts) of one biller.

billers1
  • List billersSource

    Billers available for bills payment, optionally in one category.

bulk disbursement transactions1
  • List transfers in a bulk batchSource

    Transfers inside one bulk batch. Read only.

bulk disbursements2
  • Get bulk transferSource

    Read one bulk transfer batch summary. Read only.

  • List bulk transfersSource

    Bulk transfer batches with counts and totals. Read only.

disbursements2
  • Get transferSource

    Read one single transfer by your reference. Read only.

  • List transfersSource

    Single transfers with status, fee and destination bank. Read only.

invoices3
  • Create invoiceDestinationProvider duplicate protectionApproval before production

    Create a Monnify invoice with a checkout URL and virtual account. No money moves until the customer pays.

  • Get invoiceSource

    Read one invoice by your invoice reference.

  • List invoicesSource

    Monnify invoices with status, amount and payment details.

limit profiles3
  • Create limit profileDestinationNot retried automaticallyApproval before production

    Create a limit profile (single transaction value, daily volume and value caps). Moves no money.

  • List limit profilesSource

    Transaction limit profiles that can be applied to reserved accounts.

  • Update limit profileDestinationProvider duplicate protectionApproval before production

    Replace the name and caps of a limit profile.

mandate debits1
  • Get mandate debit statusSource

    Status of a direct-debit collection by your payment reference (read only).

mandates1
  • Get direct-debit mandateSource

    Status, period and amount of a direct-debit mandate by your mandate reference.

paycodes2
  • Get paycodeSource

    One paycode's status, amount and expiry by your paycode reference.

  • List paycodesSource

    Cash-out paycodes by transaction reference, status or creation window (read only).

refunds2
  • Get refundSource

    Read one refund by refund reference. Read only.

  • List refundsSourceIncremental

    Refunds with status and amount, optionally created since a date. Read only.

reserved account transactions1
  • List reserved account transactionsSource

    Collections received into one reserved account.

reserved accounts1
  • Get reserved accountSource

    Read a reserved (virtual) collection account by your account reference.

settlement details1
  • Get settlement details for a transactionSource

    Settlement information and beneficiaries for one collection.

settlement transactions1
  • List transactions in a settlementSource

    Collections paid out in one settlement, by the settlement reference on your bank statement.

sub accounts1
  • List sub-accountsSource

    Settlement sub-accounts and their default split percentages.

transactions3
  • Get transaction statusSource

    Read a collection's status, amounts and settlement amount by Monnify transaction reference.

  • List collection transactionsSourceIncremental

    Read paginated Monnify collections, with currency and provider status, optionally filtered by reference or amount.

  • Find transaction by referenceSource

    Read a collection's status by your payment reference or the Monnify transaction reference.

ussd banks1
  • List banks with USSD short codesSource

    Banks that support USSD payments, with their short codes.

wallet balance1
  • Get disbursement wallet balanceSource

    Available and ledger balance of your Monnify disbursement wallet.

Access and limits

Authentication
Monnify API key and secret
Plans and access
A Monnify merchant account with API key, secret key and contract code. Disbursement reads need disbursements enabled on the account; reserved accounts need the reserved-account product.
Test environment
Use sandbox keys from the Monnify dashboard with sandbox.monnify.com.
Rate limits
Monnify does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries.
Pagination
Spring-style pages: 0-based page/size (pageNo/pageSize for disbursements); responseBody.last ends paging.
Provider events
Monnify posts collection, refund, settlement, disbursement and mandate events to the webhook URLs set in the dashboard, signed with monnify-signature (hex HMAC-SHA512 of the body with the secret key). Flows can start the moment something happens: when a customer payment is received; when a transfer is completed; when a transfer fails or is reversed; when a refund is completed.

Before you build a flow

  • Intentional exclusions: transaction initialisation, card charges, card-token charges and OTP, bank-transfer and USSD payment initiation, refunds, single and bulk transfers and their OTPs, wallet creation, creating, debiting or cancelling direct-debit mandates, creating, revealing (authorize) or deleting paycodes, customer validation and bill vending, invoice cancellation, reserved-account creation, deallocation, limits, payment-source, split and KYC updates (they carry BVN/NIN), sub-account changes and KYC lookups.
  • Wallet listing (filtered by customer email) and wallet transactions (keyed by a full account number) are not exposed because both put personal or account data in the URL.
  • Mandates map status, amounts and dates only; customer names, contacts and bank account details are never mapped. Paycodes never map the cash-out code or beneficiary name.
  • Disputes and chargebacks: Monnify's API (as published in its official SDKs) has no dispute or chargeback endpoint. Disputes are raised and answered in the Monnify dashboard, and accepted disputes are reversed or deducted from a later settlement.
  • Settlement list: Monnify's API has no endpoint that lists settlements (payouts) by date. Read the collections in a settlement with List transactions in a settlement (by the settlement reference on your bank statement), or a collection's settlement with Get settlement details.
  • This uses Monnify online collections; Moniepoint POS terminal control is a separate product and is not implemented.
  • Customer names, emails, BVN, NIN and transfer recipient account numbers are not mapped.

Developer reference

  1. Create the Moniepoint · Monnify credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Moniepoint · Monnify, 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
Moniepoint · Monnify docsAPI referenceMoniepoint · Monnify docsAuthentication

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