API status
Check the transaction path before you repeat a request.
When a transaction does not return the result you expected, the safest next step is not always to send it again.
Use the reference, documented transaction state and available status information to understand what happened first.
Start with the transaction reference
Keep the reference returned for each request.
When investigating a transaction, this is one of the most useful pieces of information for connecting the request in your system to the corresponding TopupNaija record.
Understand the state
Your integration should distinguish between states documented by the API.
A transaction that has failed is different from one that is still being processed.
Do not assume that the absence of an immediate success response means nothing happened.
Avoid duplicate requests
Blind retries can create a worse customer experience if the first transaction is still being processed.
Before repeating a vending request, use the documented status flow and any available query mechanism to determine whether another action is appropriate.
When contacting support
Provide enough information for the issue to be investigated without exposing secrets.
Useful information can include:
- Transaction reference
- Approximate time of request
- Product or service involved
- Your own non-sensitive internal reference
- Relevant error or status information
- Description of the expected and observed behaviour
Never send private API credentials in a support message.
Something does not look right?
Check the documented state first. If you still need help, contact support with the transaction reference.