This page is here to give you a general explanation of transactions lifecycle.
Transaction Flow
As described on the API Flow Overview given in the introduction, when successful the request will generate a transaction or paywall and return the corresponding status in the response.
If required fields are missing from your request the transaction will be created with the MISSING_INFO status. The form object in the response will contain the missing info form URL to redirect your users. From there they will be able to fill in the missing information and attempt validation again. If successful, the user will be redirected to the payment method's checkout page.
The above only applies to transactions. The missing info form is integrated directly inside of the Paywall page.
If any of the fields value is not valid the provider will reject the transaction and your request will return a return FAILED status. A transaction UID will still be generated if shown in the response received in the uid parameter.
If the transaction goes through normally, you will receive a PENDING status callback. From this point on the transaction will go through different statuses depending on its processing stage. The PENDING status does not mean the transaction will be successfully processed since it is generated before payment is made. If the user does not go through with payment, the transaction will expire after 7 days.
Transaction Flowchart
Payretailers transaction flowchart.
Transaction Statuses
After transactions are created they go through different statuses that reflect their actual state. The system sends Notifications to the merchant's shop only when the transaction reaches a final status ("approved", "failed", "rejected" and "cancelled"). You can find the meaning of those statuses in the table below.
If one of your transactions is stuck on a status that is not final for no apparent reason please open a ticket with our support team.
Payretailers transaction status flowchart.
| Status Name | Meaning |
|---|---|
| FAILED | The transaction was not generated due to an invalid value or the payment could not be processed. |
| MISSING INFO | One or more required fields are missing from the request. |
| PENDING | The transaction was successfully created and is pending payment. |
| EXPIRED | The transaction was not paid on time by the user. This status can change to APPROVED if the payment processing time took longer than the expiration delay. |
| REJECTED | The transaction was rejected by the payment provider. The rejection might be due to client personal information, bank details or the lack of bank funds. |
| APPROVED | The transaction was fully processed successfully. |
| REVERSED | The user's bank confirmed the payment but the funds were not transferred. This could be due to processing errors in the local banking system. Whenever a payment settlement is cancelled or delayed, merchants will be notified by email to minimise the impact of fraud attempts. |
| CANCELLED | The transaction was canceled due to certain restrictions and refunded to the user. |