The following table provides description for each status of the transaction. You must map the order status using the payment state specified in the Status column of the following table. As Test environment (Sandbox) is a replica of the Production environment, you can push the code in production by just replacing account credentials and URL.
|Auth refers to the transaction which has been authorized from the bank and the amount has been debited from the customer’s bank account, but that amount is not captured at PayU’s end (reflects in your PayU Dashboard).
|The transaction is successful.
|This status is used when a transaction is canceled by the customer.
|When a transaction is not completed by the customer. For example, the customer does not click Pay Now on the PayU Payment page (PayU Hosted Checkout) and forfeits the transaction. In such cases, the transaction as bounced.
This can happen due to various reasons: intent of the customer, Internet issues, etc.
|When a transaction reaches PayU, the transaction is redirected to the respective payment gateway. The payment gateway sends the response back to PayU with the status of the transaction. In few instances, PayU not get any response from the payment gateway. In such cases, PayU marks the transaction as dropped.
|When a transaction gets failed, it can be due to several reasons, such as, failed payment gateway, failed from PayU, from issuing bank of the card, authentication failure, etc.
|When PayU initiates refund for the transaction where PayU got success during reconciliation.
|When the merchant lands on PayU’s page, the transaction status will be initiated.
|When the customer clicks Pay Now on the PayU Payment page (PayU Hosted Checkout) and the transaction is routed to the 3DS page, and then the transaction status will be changed to "In progress".