Callback for PG Load API

When a transaction is completed via the PG Load API, the result is communicated back to the merchant through a callback mechanism. The response parameters are sent to the surl (success URL) or furl (failure URL) that was provided in the original PG Load API request.

Callback Flow

1. Merchant initiates the load request using the PG Load API with mandatory fields like clientTxnId, surl, and furl
2. Customer completes the payment on the payment gateway page
3. Upon completion:
   • PayU redirects the customer to the surl in case of success
   • If the transaction fails, the customer is redirected to the furl
4. Callback parameters are sent to these URLs for final status tracking and reconciliation

Callback parameters

Sample callback response

When the transaction is completed, PayU sends the following parameters to your success or failure URL:

status=SUCCESS&AccosaRefNo=12321234&accosaTransactionId=1487&responseCode=00&responseMessage=Success&merchantCode=Vb007&clientTxnId=2023LOAD10000000003&txnAmount=1000&checksum=900a98e04b4abc610bd0cb5623a470a4b0d821d85551ae3baa41011536cfe6b9&loadAmount=4100

Checksum verification

To ensure the integrity of the callback data, a checksum is included in the callback parameters. The merchant should validate this checksum to confirm the authenticity of the response.

The checksum is calculated using the same algorithm and salt as used in the request hash calculation.

Success and Failure Handling

Success scenario

When a transaction is successful:

• The customer is redirected to the surl provided in the original request
• The responseCode will be "00"
• The status will be "SUCCESS"
• The wallet will be credited with the amount specified in loadAmount

Failure scenario

When a transaction fails:

• The customer is redirected to the furl provided in the original request
• The responseCode will not be "00"
• The status will be "FAILED"
• An appropriate error message will be included in the responseMessage parameter