Learn how to integrate Nkwa Pay’s mobile money payment infrastructure with our asynchronous API design, webhook system, and MNO stability features.
Nkwa Pay simplifies integrating mobile money into your payment flows across Cameroon. Our API supports both collections (customer-to-business) and disbursements (business-to-customer) in an asynchronous, high-performance environment designed for reliability.
The following sections introduce important aspects of mobile money integration and working with Nkwa Pay’s API to help you build a high-quality payment experience.
Our 24/7 payment operations team monitors all Mobile Network Operators (MNOs) on our platform for instability and downtime. We automatically stop accepting payments to those MNOs if the success rate drops below acceptable thresholds. This information is accessible from our availability endpoint, which you can poll to adjust your application’s behavior accordingly.
Sometimes MNO systems experience degraded performance. When that happens, their APIs might have trouble returning the final status of payments (stuck in pending). In such cases, Nkwa Pay ensures these payments are reconciled manually. This means that when using Nkwa Pay, all payments are always reconciled to their final status. This reconciliation process takes a little longer than processing during normal operations but guarantees payment status integrity.
Nkwa Pay’s API is fully asynchronous. This design is necessary to provide high performance and reliable payment infrastructure across unreliable mobile networks.
When you create a payment (collection or disbursement), you’ll get an initial response that confirms whether the payment was accepted for processing. There are two ways to determine the final status of a payment:
Configure a callback URL in our portal to automatically receive notifications when a payment reaches its final status. You’ll need to implement a callback handler in your application that can receive and process these notifications.
Use the corresponding Get payment/:id
endpoint periodically to check if the payment has reached its final status.
While simpler to implement, this approach is less efficient and may introduce delays in payment status awareness.
When implementing your callback handler, consider the following best practices:
[ip1, ip2, ip3]
200 OK
/availability
regularly (e.g., once per hour) to detect MNO degradations and adjust customer messaging accordinglyBy following these implementation guidelines, you’ll create a robust and reliable mobile money payment experience for your customers using Nkwa Pay.
Learn how to integrate Nkwa Pay’s mobile money payment infrastructure with our asynchronous API design, webhook system, and MNO stability features.
Nkwa Pay simplifies integrating mobile money into your payment flows across Cameroon. Our API supports both collections (customer-to-business) and disbursements (business-to-customer) in an asynchronous, high-performance environment designed for reliability.
The following sections introduce important aspects of mobile money integration and working with Nkwa Pay’s API to help you build a high-quality payment experience.
Our 24/7 payment operations team monitors all Mobile Network Operators (MNOs) on our platform for instability and downtime. We automatically stop accepting payments to those MNOs if the success rate drops below acceptable thresholds. This information is accessible from our availability endpoint, which you can poll to adjust your application’s behavior accordingly.
Sometimes MNO systems experience degraded performance. When that happens, their APIs might have trouble returning the final status of payments (stuck in pending). In such cases, Nkwa Pay ensures these payments are reconciled manually. This means that when using Nkwa Pay, all payments are always reconciled to their final status. This reconciliation process takes a little longer than processing during normal operations but guarantees payment status integrity.
Nkwa Pay’s API is fully asynchronous. This design is necessary to provide high performance and reliable payment infrastructure across unreliable mobile networks.
When you create a payment (collection or disbursement), you’ll get an initial response that confirms whether the payment was accepted for processing. There are two ways to determine the final status of a payment:
Configure a callback URL in our portal to automatically receive notifications when a payment reaches its final status. You’ll need to implement a callback handler in your application that can receive and process these notifications.
Use the corresponding Get payment/:id
endpoint periodically to check if the payment has reached its final status.
While simpler to implement, this approach is less efficient and may introduce delays in payment status awareness.
When implementing your callback handler, consider the following best practices:
[ip1, ip2, ip3]
200 OK
/availability
regularly (e.g., once per hour) to detect MNO degradations and adjust customer messaging accordinglyBy following these implementation guidelines, you’ll create a robust and reliable mobile money payment experience for your customers using Nkwa Pay.