mobile money api
Mobile money agents are the primary point of contact for mobile money account holders. Agents provide a support service where account holders can register for the mobile money service, cash-in and cash-out from their account.
# Use cases
# Introduction
Agent Services comprises of the following:
Cash-in and Cash-out Services
- Agent-initiated Cash-out. The agent initiates the cash-out and the mobile money customer is requested to authenticate the cash-out by the mobile money provider.
- Customer-initiated Cash-out. The mobile money customer initiates the payment by specifying the agent that is to be performing the cash-out.
- Cash-out via Authorisation Code. The customer generates an authorisation code up to a maximum amount. The agent then enters or scans (if rendered as a QR code) the code to perform the withdrawal.
- Cash-in. The agent initiates the cash-in by entering the customer account identifier(s).
Closed loop and open-loop agent cash-in and cash-out are supported by the Mobile Money API. Closed loop cash-in/cash-out occurs where the agent and customer accounts reside with the same mobile money provider. Open loop cash-in/cash-out occurs where the agent and customer accounts reside with different mobile money providers.
Agents can be physical agents, i.e. customers that are serviced by an human, or can be an ATM.
Customer Account Services
- Customer Registration. Agents can register new customers for mobile money.
- KYC Verification. Agents that provide KYC verification services can confirm that they have verified customer KYC.
Further Reading
For further reading, please refer to the following:
- Getting Started. Specifies the design principles, behaviours, and error handling of the Mobile Money API.
- API Service Definition. Documents all Mobile Money API endpoints, fields, objects, and enumerations.
All documentation can be found on the GSMA Mobile Money API Developer Portal.
# Intended Audience
| Audience | Usage | Role |
|---|---|---|
| Mobile Money Providers | To understand how to implement the Mobile Money API to allow agents to perform cash-in, cash-out, customer registration and customer KYC verification services on behalf of mobile money customers. | API Provider |
| Agents | To understand how to implement the Mobile Money API to service customer requests for cash-in, cash-out, registration and KYC verification. | API Consumer |
Use case scenarios
Agent-initiated Cash-out
In this example, an asynchronous cash-out flow is used with a final callback.
sequenceDiagram
participant Agent
participant Mobile Money Provider
participant Customer
Agent->>Mobile Money Provider: POST /transactions/type/withdrawal
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The Agent submits the payment request for processing to
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent Mobile Money Provider->>Customer: Obtain Customer Authorisation activate Customer Note right of Customer: (2) The customer is requested by the MMP to
authorise the cash-out. This can be
achieved through a number of means
including USSD Push and One Time Code.
OpenId can also be used for cash-out
authorisation. Customer-->>Mobile Money Provider: (Authorised) deactivate Customer Mobile Money Provider->>Agent: PUT {Callback URL} (Transactions Object) activate Agent Note right of Mobile Money Provider: (3) The MMP informs the agent that the cash-out
has been successfully completed by returning
the final representation of the transaction. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent Mobile Money Provider->>Customer: Obtain Customer Authorisation activate Customer Note right of Customer: (2) The customer is requested by the MMP to
authorise the cash-out. This can be
achieved through a number of means
including USSD Push and One Time Code.
OpenId can also be used for cash-out
authorisation. Customer-->>Mobile Money Provider: (Authorised) deactivate Customer Mobile Money Provider->>Agent: PUT {Callback URL} (Transactions Object) activate Agent Note right of Mobile Money Provider: (3) The MMP informs the agent that the cash-out
has been successfully completed by returning
the final representation of the transaction. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
Agent-initiated Cash-out Failure
In this example, an asynchronous cash-out flow is used with a final callback that contains the reason for failure.
sequenceDiagram
participant Agent
participant Mobile Money Provider
participant Customer
Agent->>Mobile Money Provider: POST /transactions/type/withdrawal
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The Agent submits the payment request for processing to
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent Mobile Money Provider->>Customer: Obtain Customer Authorisation activate Customer Note right of Customer: (2) The customer is requested by the MMP to
authorise the cash-out. The customer
declines the request or the request times-
out. Customer-->>Mobile Money Provider: (Declined or Timeout) deactivate Customer Mobile Money Provider->>Agent: PUT {Callback URL} (Error Object) activate Agent Note right of Mobile Money Provider: (3) The MMP informs the agent that the cash-out
has failed and returns the error object detailing
the reason for failure. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent Mobile Money Provider->>Customer: Obtain Customer Authorisation activate Customer Note right of Customer: (2) The customer is requested by the MMP to
authorise the cash-out. The customer
declines the request or the request times-
out. Customer-->>Mobile Money Provider: (Declined or Timeout) deactivate Customer Mobile Money Provider->>Agent: PUT {Callback URL} (Error Object) activate Agent Note right of Mobile Money Provider: (3) The MMP informs the agent that the cash-out
has failed and returns the error object detailing
the reason for failure. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
Agent-initiated Cash-out using the Polling Method
In this example, an asynchronous cash-out flow is used with the polling method. The client polls against the request state object to determine the outcome of the cash-out request.
sequenceDiagram
participant Agent
participant Mobile Money Provider
participant Customer
Agent->>Mobile Money Provider: POST /transactions/type/withdrawal
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent submits the cash-out request for processing to
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent par loop activate Agent Agent->>Mobile Money Provider: GET /requeststates/{serverCorrelationId} Note right of Mobile Money Provider: (2) The agent polls the MMP for the Request State until the
transaction is authorised or declined or until the polling limit
is reached. Mobile Money Provider-->>Agent: HTTP 200 (Request State Object) end and Mobile Money Provider->>Customer: Obtain Customer Authorisation activate Customer Note right of Customer: (3) The Customer is requested to the MMP to
authorise the cash-out. This can be
achieved through a number of means
including USSD Push and One Time Code.
OpenId can also be used for cash-out
authorisation. Customer-->>Mobile Money Provider: (Authorised) end deactivate Agent deactivate Customer deactivate Mobile Money Provider opt activate Mobile Money Provider activate Agent Agent->>Mobile Money Provider: GET /transactions/transactionsReference Note right of Mobile Money Provider: (4) The agent can use the objectReference returned in the
Request State to retrieve a representation of the complete
cash-out transaction. Mobile Money Provider-->>Agent: HTTP 200 (Transactions Object) end deactivate Agent deactivate Mobile Money Provider
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent par loop activate Agent Agent->>Mobile Money Provider: GET /requeststates/{serverCorrelationId} Note right of Mobile Money Provider: (2) The agent polls the MMP for the Request State until the
transaction is authorised or declined or until the polling limit
is reached. Mobile Money Provider-->>Agent: HTTP 200 (Request State Object) end and Mobile Money Provider->>Customer: Obtain Customer Authorisation activate Customer Note right of Customer: (3) The Customer is requested to the MMP to
authorise the cash-out. This can be
achieved through a number of means
including USSD Push and One Time Code.
OpenId can also be used for cash-out
authorisation. Customer-->>Mobile Money Provider: (Authorised) end deactivate Agent deactivate Customer deactivate Mobile Money Provider opt activate Mobile Money Provider activate Agent Agent->>Mobile Money Provider: GET /transactions/transactionsReference Note right of Mobile Money Provider: (4) The agent can use the objectReference returned in the
Request State to retrieve a representation of the complete
cash-out transaction. Mobile Money Provider-->>Agent: HTTP 200 (Transactions Object) end deactivate Agent deactivate Mobile Money Provider
Customer-initiated Cash-out
In this example, an asynchronous cash-out flow is used with a final callback.
sequenceDiagram
participant Customer
participant Mobile Money Provider
participant Agent
Customer->>Mobile Money Provider: POST /transactions/type/withdrawal
activate Customer
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The customer's channel (e.g. Mobile Money App) submits
the cash-out request for processing to the MMP. The MMP
will return the Request State object to indicate that the
request is 'pending'. Mobile Money Provider-->>Customer: HTTP 202 (Request State Object) deactivate Customer Mobile Money Provider->>Customer: PUT {Callback URL} (Transactions Object) activate Customer Note right of Mobile Money Provider: (2) The MMP informs the customer's channel that
the cash-out has been successfully completed
by returning the final representation of the
transaction. Customer-->>Mobile Money Provider: HTTP 204 deactivate Customer activate Agent Mobile Money Provider->>Agent: Notify Note right of Agent: (3) The MMP notifies the agent tha the cash-
out has successfully compeleted. deactivate Mobile Money Provider deactivate Agent
the cash-out request for processing to the MMP. The MMP
will return the Request State object to indicate that the
request is 'pending'. Mobile Money Provider-->>Customer: HTTP 202 (Request State Object) deactivate Customer Mobile Money Provider->>Customer: PUT {Callback URL} (Transactions Object) activate Customer Note right of Mobile Money Provider: (2) The MMP informs the customer's channel that
the cash-out has been successfully completed
by returning the final representation of the
transaction. Customer-->>Mobile Money Provider: HTTP 204 deactivate Customer activate Agent Mobile Money Provider->>Agent: Notify Note right of Agent: (3) The MMP notifies the agent tha the cash-
out has successfully compeleted. deactivate Mobile Money Provider deactivate Agent
Customer-initiated Cash-out Failure
In this example, an asynchronous cash-out flow is used with a final callback that contains the reason for failure.
sequenceDiagram
participant Customer
participant Mobile Money Provider
participant Agent
Customer->>Mobile Money Provider: POST /transactions/type/withdrawal
activate Customer
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The customer's channel (e.g. Mobile Money App) submits
the cash-out request for processing to the MMP. The MMP
will return the Request State object to indicate that the
request is 'pending'. Mobile Money Provider-->>Customer: HTTP 202 (Request State Object) deactivate Customer Mobile Money Provider->>Customer: PUT {Callback URL} (Error Object) activate Customer Note right of Mobile Money Provider: (2) The MMP informs the customer's channel that
the cash-out has failed and returns the error
object detailing the reason for failure. Customer-->>Mobile Money Provider: HTTP 204 deactivate Customer activate Agent Mobile Money Provider->>Agent: Notify Note right of Agent: (3) The MMP notifies the agent tha the cash-
out has failed. deactivate Mobile Money Provider deactivate Agent
the cash-out request for processing to the MMP. The MMP
will return the Request State object to indicate that the
request is 'pending'. Mobile Money Provider-->>Customer: HTTP 202 (Request State Object) deactivate Customer Mobile Money Provider->>Customer: PUT {Callback URL} (Error Object) activate Customer Note right of Mobile Money Provider: (2) The MMP informs the customer's channel that
the cash-out has failed and returns the error
object detailing the reason for failure. Customer-->>Mobile Money Provider: HTTP 204 deactivate Customer activate Agent Mobile Money Provider->>Agent: Notify Note right of Agent: (3) The MMP notifies the agent tha the cash-
out has failed. deactivate Mobile Money Provider deactivate Agent
Customer Cash-out at an ATM using an Authorisation Code
In this example the /authorisationcodes API is used to obtain a pre-authorised code. This in turn is presented by the withdrawing customer to the ATM which then initiates the cash-out request. Both flows in the diagram result in a callback.
sequenceDiagram
participant Customer
participant ATM
participant Mobile Money Provider
Customer->>Mobile Money Provider: POST /accounts/{identifierType}/{identifier}/authorisationcodes
activate Customer
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The customer's channel (e.g. Mobile Money App)
submits the request to generate an authorisation code
to the MMP. The MMP will return the Request State
object to indicate that the request is 'pending'. Mobile Money Provider-->>Customer: HTTP 202 (Request State Object) Mobile Money Provider->>Customer: PUT {Callback URL} (Authorisation Codes Object) Note right of Mobile Money Provider: (2) The MMP informs the customer's channel that
the request has been successfully completed by
returing the final representation of the
authorisation code. Customer-->>Mobile Money Provider: HTTP 204 deactivate Customer deactivate Mobile Money Provider Note right of Customer: (3) The customer enters the code into the ATM. Customer->>ATM: Code Entry activate Customer activate ATM activate Mobile Money Provider ATM->>Mobile Money Provider: POST /transactions/type/withdrawal Note right of Mobile Money Provider: (4) The ATM submits the cash-out request for processing
to the MMP. The request will contain the authorisation
code. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>ATM: HTTP 202 (Request State Object) deactivate ATM Mobile Money Provider->>ATM: PUT {Callback URL} (Transactions Object) activate ATM Note right of Mobile Money Provider: (5) The MMP informs the ATM that the cash-out
has been successfully completed by returning
the final representation of the transaction. ATM-->>Mobile Money Provider: HTTP 204 deactivate Mobile Money Provider ATM->>Customer: Notify deactivate Customer deactivate ATM
submits the request to generate an authorisation code
to the MMP. The MMP will return the Request State
object to indicate that the request is 'pending'. Mobile Money Provider-->>Customer: HTTP 202 (Request State Object) Mobile Money Provider->>Customer: PUT {Callback URL} (Authorisation Codes Object) Note right of Mobile Money Provider: (2) The MMP informs the customer's channel that
the request has been successfully completed by
returing the final representation of the
authorisation code. Customer-->>Mobile Money Provider: HTTP 204 deactivate Customer deactivate Mobile Money Provider Note right of Customer: (3) The customer enters the code into the ATM. Customer->>ATM: Code Entry activate Customer activate ATM activate Mobile Money Provider ATM->>Mobile Money Provider: POST /transactions/type/withdrawal Note right of Mobile Money Provider: (4) The ATM submits the cash-out request for processing
to the MMP. The request will contain the authorisation
code. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>ATM: HTTP 202 (Request State Object) deactivate ATM Mobile Money Provider->>ATM: PUT {Callback URL} (Transactions Object) activate ATM Note right of Mobile Money Provider: (5) The MMP informs the ATM that the cash-out
has been successfully completed by returning
the final representation of the transaction. ATM-->>Mobile Money Provider: HTTP 204 deactivate Mobile Money Provider ATM->>Customer: Notify deactivate Customer deactivate ATM
Agent-initiated Customer Cash-in
In this diagram, the agent firstly checks that the depositing customer’s name is correct and will then submit the cash-in request. The final result is returned in the callback.
sequenceDiagram
participant Agent
participant Mobile Money Provider
participant Customer
Agent->>Mobile Money Provider: GET /accounts/{identifierType}/{identifier}/accountname
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent retrieves the name of the depositing customer
and will check that the name is correct. Mobile Money Provider-->>Agent: HTTP 200 (Account Holder Name Object) Agent->>Mobile Money Provider: POST /transactions/type/deposit Note right of Mobile Money Provider: (2) The agent submits the cash-in request for processing to
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent Mobile Money Provider->>Agent: PUT {Callback URL} (Transactions Object) activate Agent Note right of Mobile Money Provider: (3) The MMP informs the agent that the cash-in
has been successfully completed by returning
the final representation of the transaction. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent activate Customer Mobile Money Provider->>Customer: Notify Note right of Customer: (4) The MMP notifies the customer that the
cash-in has successfully compeleted. deactivate Mobile Money Provider deactivate Customer
and will check that the name is correct. Mobile Money Provider-->>Agent: HTTP 200 (Account Holder Name Object) Agent->>Mobile Money Provider: POST /transactions/type/deposit Note right of Mobile Money Provider: (2) The agent submits the cash-in request for processing to
the MMP. The MMP will return the Request State object to
indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) deactivate Agent Mobile Money Provider->>Agent: PUT {Callback URL} (Transactions Object) activate Agent Note right of Mobile Money Provider: (3) The MMP informs the agent that the cash-in
has been successfully completed by returning
the final representation of the transaction. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent activate Customer Mobile Money Provider->>Customer: Notify Note right of Customer: (4) The MMP notifies the customer that the
cash-in has successfully compeleted. deactivate Mobile Money Provider deactivate Customer
Cash-out Reversal
In some failure scenarios, an agent may need to reverse a transaction. This diagram illustrates a reversal with the final result communicated via the callback.
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: POST /transactions/{original transaction reference}/reversals
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent submits the reversal request for processing to
the MMP - passing the reference of the transaction that is
to be reversed. The MMP will return the Request State
object to indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) Mobile Money Provider->>Agent: PUT {Callback URL} (Reversal Object) Note right of Mobile Money Provider: (2) The MMP informs the Agent that the reversal
has been successfully completed by returning
the final representation of the reversal
transaction. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
the MMP - passing the reference of the transaction that is
to be reversed. The MMP will return the Request State
object to indicate that the request is 'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) Mobile Money Provider->>Agent: PUT {Callback URL} (Reversal Object) Note right of Mobile Money Provider: (2) The MMP informs the Agent that the reversal
has been successfully completed by returning
the final representation of the reversal
transaction. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
Register a Customer Mobile Money Account
In this diagram, an agent registers a new mobile money customer on behalf of a mobile money provider.
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: POST /accounts/individual
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent submits the account
registration request for processing
to the MMP. The MMP will return
the Request State object to
indicate that the request is
'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) Mobile Money Provider->>Agent: PUT {Callback URL} (Account Object) Note right of Mobile Money Provider: (2) The MMP informs the agent that
the reversal has been successfully
registered by returning the final
representation of the account. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
registration request for processing
to the MMP. The MMP will return
the Request State object to
indicate that the request is
'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) Mobile Money Provider->>Agent: PUT {Callback URL} (Account Object) Note right of Mobile Money Provider: (2) The MMP informs the agent that
the reversal has been successfully
registered by returning the final
representation of the account. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
Verify a Customer’s KYC
In this diagram, an agent verifies the physical KYC provided by the customer against details held by the mobile money provider and informs the provider that the KYC has been successfully verified.
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: GET /accounts/{identifierType}/{identifier}
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent retrieves account
information from the MMP which
includes the customer's KYC
details. Mobile Money Provider-->>Agent: HTTP 200 (Account Object) Agent->>Mobile Money Provider: PATCH /accounts/{identifierType}/{identifier}/identities/{identityId} Note right of Mobile Money Provider: (2) The agent submits the KYC
verification request for processing
to the MMP. The MMP will return
the Request State object to
indicate that the request is
'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) Mobile Money Provider->>Agent: PUT {Callback URL} (Success) Note right of Mobile Money Provider: (3) The MMP informs the agent that
the verification request has been
successfully processed. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
information from the MMP which
includes the customer's KYC
details. Mobile Money Provider-->>Agent: HTTP 200 (Account Object) Agent->>Mobile Money Provider: PATCH /accounts/{identifierType}/{identifier}/identities/{identityId} Note right of Mobile Money Provider: (2) The agent submits the KYC
verification request for processing
to the MMP. The MMP will return
the Request State object to
indicate that the request is
'pending'. Mobile Money Provider-->>Agent: HTTP 202 (Request State Object) Mobile Money Provider->>Agent: PUT {Callback URL} (Success) Note right of Mobile Money Provider: (3) The MMP informs the agent that
the verification request has been
successfully processed. Agent-->>Mobile Money Provider: HTTP 204 deactivate Agent deactivate Mobile Money Provider
Obtain an Agent Balance
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: GET /accounts/{identifierType}/{identifier}/balance
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) Obtain the balance of the
requested account. Mobile Money Provider-->>Agent: HTTP 200 (Balance Object) deactivate Agent deactivate Mobile Money Provider
requested account. Mobile Money Provider-->>Agent: HTTP 200 (Balance Object) deactivate Agent deactivate Mobile Money Provider
Retrieve Transactions for an Agent
This diagram illustrates use of a cursor mechanism to retrieve all transactions for an agent via multiple requests.
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: GET /accounts/{identifierType}/{identifier}/transactions?offset=0&limit=20
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent requests up to 20
transactions for the account
from the MMP. Mobile Money Provider-->>Agent: HTTP 200 (Transactions Array) (X-Records-Available-Count=40) Note right of Mobile Money Provider: (2) The MMP returns an array of
20 transactions and indicates
via a response header that
there are 40 records
available in total. Agent->>Mobile Money Provider: GET /accounts/{identifierType}/{identifier}/transactions?offset=20&limit=20 Note right of Mobile Money Provider: (3) The agent requests the
remaining transactions for
the account from the MMP. Mobile Money Provider-->>Agent: HTTP 200 (Transactions Array) (X-Records-Available-Count=40) deactivate Agent deactivate Mobile Money Provider
transactions for the account
from the MMP. Mobile Money Provider-->>Agent: HTTP 200 (Transactions Array) (X-Records-Available-Count=40) Note right of Mobile Money Provider: (2) The MMP returns an array of
20 transactions and indicates
via a response header that
there are 40 records
available in total. Agent->>Mobile Money Provider: GET /accounts/{identifierType}/{identifier}/transactions?offset=20&limit=20 Note right of Mobile Money Provider: (3) The agent requests the
remaining transactions for
the account from the MMP. Mobile Money Provider-->>Agent: HTTP 200 (Transactions Array) (X-Records-Available-Count=40) deactivate Agent deactivate Mobile Money Provider
Check for Service Availability
The Heartbeat API is used for monitoring purposes and establishes whether the mobile money provider is in a state that enables a client to submit a request for processing.
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: GET /heartbeat
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) The agent requests the availability
of the service from the MMP. Mobile Money Provider-->>Agent: HTTP 200 (Heartbeat Object) Note right of Mobile Money Provider: (2) The MMP returns the availability of
the service - available, unavailable
or degraded. deactivate Agent deactivate Mobile Money Provider
of the service from the MMP. Mobile Money Provider-->>Agent: HTTP 200 (Heartbeat Object) Note right of Mobile Money Provider: (2) The MMP returns the availability of
the service - available, unavailable
or degraded. deactivate Agent deactivate Mobile Money Provider
Retrieve a Missing API Response
This API can be used by the agent to retrieve a link to the final representation of the resource for which it attempted to create. Use this API when a callback is not received from the mobile money provider.
sequenceDiagram
participant Agent
participant Mobile Money Provider
Agent->>Mobile Money Provider: GET /responses{clientCorrelationId}
activate Agent
activate Mobile Money Provider
Note right of Mobile Money Provider: (1) Using the agent's
clientCorrelationId, a request for the
missing API response is sent. Mobile Money Provider-->>Agent: HTTP 200 (Responses Object) Note right of Mobile Money Provider: (2) A Responses object is returned
containing a link to the missing
resource. Agent->>Mobile Money Provider: GET /{link} Note right of Mobile Money Provider: (3) The Agent uses the link to obtain
a representation of the missing
resource. Mobile Money Provider-->>Agent: HTTP 200 (Requested Object) deactivate Agent deactivate Mobile Money Provider
clientCorrelationId, a request for the
missing API response is sent. Mobile Money Provider-->>Agent: HTTP 200 (Responses Object) Note right of Mobile Money Provider: (2) A Responses object is returned
containing a link to the missing
resource. Agent->>Mobile Money Provider: GET /{link} Note right of Mobile Money Provider: (3) The Agent uses the link to obtain
a representation of the missing
resource. Mobile Money Provider-->>Agent: HTTP 200 (Requested Object) deactivate Agent deactivate Mobile Money Provider
# Ready to explore?
Find our latest API documentation.