How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MTN Payments V1

This is the Payment API for MADAPI. Handles payment use cases such as spTransfer, Debit request, Payment request, and related financial transactions. Provides comprehensive payment processing capabilities including merchant payments, customer payments, transaction status queries, payment history, and reverse payment operations.

MTN Payments V1 is one of 119 APIs that MTN Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, Benin, Cameroon, Congo, and Côte d’Ivoire. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 15 operations across 15 paths, organized into 2 resource areas. It is described by OpenAPI 3.0.1, at version 3.0.0.

Requests are made against a single base URL, https://api.mtn.com/v1.

15 operations 15 paths 0 schemas 7 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3.0.0
Base URL
https://api.mtn.com/v1
Authentication
OAuth 2.0, HTTP Bearer
License
Resource Areas
2

Authentication & Security 2

MTN Payments V1 declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • Bearer — Bearer token received from OAuth2.0 authentication with the MADAPI

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 7 GET, 8 POST. They span 2 resource areas: Payment, Consent. Each is listed below with its method, path, parameters, and response codes.

Payment 13
POST
/payment-link
Provides the ability for a consumer to generate a payment link for account payment
Payment_post_generatePaymentLink_paymentlink 4 params body → 200400500401403404502503
POST
/payment-agreement
Generate payment agreement (Promise to Pay)
Payment_post_setPaymentPromise_paymentagreement 1 param body → 200400500401403404502503
POST
/reverse-payment
Reverse payment
Payment_post_reversePayment_reversepayment 3 params body → 200400404500401403502503
POST
/payments
Process payment to service providers
Payment_post_payment 8 params body → 200400404500401403502503
POST
/merchant-payment
Process merchant payment transactions
Payment_post_merchantPayment_merchantpayment 4 params body → 200400401500403404502503
GET
/{correlatorId}/transactionStatus
Get payment transaction status
Payment_get_getPaymentTransactionStatus_correlatorIdtransact 11 params → 200400404500401403502503
GET
/status/{transactionid}
Update payment status to processed
Payment_get_updatePaymentStatus_statustransactionid 1 param → 200404500400401403502503
GET
/details/{transactionid}
Get payment by transactionId
Payment_get_getPaymentByTransactionId_detailstransactionid 1 param → 200404500400401403502503
POST
/fee
Calculate payment transfer fees
Payment_post_feeCheck_fee 4 params body → 200400500401403404502503
GET
/{id}/history
Get a list of payments made on a reference or by a customer id
Payment_get_paymentHistory_idhistory 21 params → 200400404500401403502503
GET
/payment-agreement/eligibility
Get eligibilty status.
Payment_get_aggregateGetEligibilty_paymentagreementelig 2 params → 200400401403404500502503
GET
/reverse-payment/{id}
reverse payment history
Payment_get_reversePaymentHistory_reversepaymentid 5 params → 200400404500401403502503
GET
/reverse-payment/history
Get reverse payment transaction history
Payment_get_reversePaymentHistory_reversepaymenthistor 16 params → 200400404500401403502503
Consent 2
POST
/payments/ussd/consent
Process user consent via USSD for payment authorization
Consent_post_receiveUserConsentFromUssd_paymentsussdconsent body → 200400404500401403502503
POST
/payments/sms/consent
User consent via SMS
Consent_post_receiveUserConsentFromSms_paymentssmsconsent body → 200400401403404500502503

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mtn-group-payments-v1.yml Raw ↑

Other APIs MTN Group publishes across the network.

MTN Account Decisioning
MTN TMF Customer Bill Management - TMF678
MTN Loans
MTN Subscriber Details
MTN Subscriber Type
MTN Provisioning
MTN Unified Balance V1
MTN TMF Resource Inventory Management - TMF639
MTN Sales Lead
MTN Service Activation and Configuration
MTN Service Ordering
MTN BSS TT OAuth V1
Where this information came from

This is an independent, third-party profile of MTN Payments V1, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.