All API requests may return any of the following status codes;
|This status code indicates that the request was processed successful.
|This indicates that the request has been received and is queued for processing. A webhook callback will be sent once processed or status query can be called to check on status
|This status code is returned from the call-back notification to indicate that a payment request received a partial payment (if permitted by initiator).
|Returned whenever there is an error processing the current request
|The payment request has been expired.
|The payment request has been cancelled.
The following payment request methods are currently supported;
|Temporary NUBAN Account Number is generated on Paga for the payment request. Payment of the requested amount to this NUBAN with fulfil the payment request
|This allow's payer to pay with thier bank's USSD. Payer's bankID must be added to the payment request payload.
In addition, if the payer is a registered Paga account holder, the following payment options may be exposed;
|Payer can authorize the transaction and pay from their Paga wallet simply by dialling the returned USSD short code.
|Payer can authorize the transaction from their Paga wallet using either web or mobile app channels
|Payer can authorize the transaction and pay from their Paga wallet for a using the paga payment link.
A payment request may be in any one of the following states;
|Payment request has been received and is awaiting authorization/fulfilment from the payer.
|Payment has been received and payment request can now be consumed.
|Payment request charge completed.
|Payment request has expired.
|Payment request creation failed.
|Payment request was cancelled
When a payment request is fulfilled, it is set to CHARGEABLE which means that it is funded and can be processed (the funds are remitted to the payee’s account or bank account). When this “second-leg” processing occurs, then it set to CONSUMED. If something happens to cause the payment leg to fail, it can remain on CHARGEABLE until the payment leg completes
Here are the different operations categories
|This is for requesting payment
|This for creating persistent payment accounts
Here are the different actions and the operations they are subcategories of:
|This is when you create a new payment request by calling the /paymentRequest endpoint
|This is whenever a payment comes in for a created Payment Request
Here are the different statuses
|Action was successful
|Payment successful but settlement not done
Here are different callback events:
|The payment made with respect to a particular payment request by a payer is the same as the amount in the request.
|The payer carried out a part payment of the payment request amount
|The payment request has expired.
|An error occurred during the period of fulfilling the payment request. This means the payment was unsuccessful
Updated almost 2 years ago