Webhook Events and Sample Payloads
List of webhook events along with sample payloads.
You can accept customer payments using PayU products. By subscribing to payments webhook events you can get notified about payment state changes.
List of Webhook Events
The table below lists the available webhook events.
| Event Name | Event Type | Description |
|---|---|---|
Successful | Payment | Triggered when a payment is successful. |
Failed | Payment | Triggered when a payment is failed. |
Refund | Payment | Triggered when a payment refund is successful and failure. |
Dispute | Payment | Triggered when a dispute is raised for a payment. |
Sample Payloads
Given below are the sample payloads for webhook events.
Watch Out!
- The payment successful and failure payloads are in the Form POST URL Encoded format.
Payment Successful
mihpayid=27553369917
&mode=SBQR
&status=success
&key=rZ1fX4
&txnid=T2603041446091822117753
&amount=40.00
&addedon=2026-03-04+14%3A46%3A14
&productinfo=Static+QR
&firstname=
&lastname=
&address1=
&address2=
&city=Gurgaon
&state=
&country=
&zipcode=122001
&email=
&phone=##########
&udf1=
&udf2=
&udf3=
&udf4=SoftQR
&udf5=BFL0000006601446
&udf6=
&udf7=
&udf8=
&udf9=
&udf10=
&card_token=
&card_no=
&field0=STQ9IUFeqlafg78815827
&field1=PRIYA+SHANKAR+PUSNAKE
&field2=995486
&field3=_mobilenum_%40axl
&field4=bajajpay.6879729.d2m9cckd%40indus
&field5=AXLd36cfcd317f243b5b3a2d62bc71caf78
&field6=00000038683323284%7C_mobilenum_%7CSBIN0011418
&field7=APPROVED+OR+COMPLETED+SUCCESSFULLY%7C00
&field8=Payment+from+PhonePe
&field9=Transaction+is+Successful.+Bank+Sent%3ATransaction+success
&payment_source=payu
&cardToken=
&authenticaticationMethod=
&PG_TYPE=SBQR-PG
&error=E000
&error_Message=No+Error
&net_amount_debit=40
&discount=0.00
&offer_key=
&offer_availed=
&unmappedstatus=captured
&hash=aefe0213c4299c7ee2039d5430f7bee63711ee627e1b47d2605d0384abbbf828f3641dae3cb126c8b2f761084cbb0bebad27bb325696cc44ce3061157d7cd9ff
&bank_ref_no=793887773815
&bank_ref_num=793887773815
&bankcode=UPISBQR
&surl=
&curl=
&furl=
&psp_name=CARDHOLDERXXXXXXXXNAMEPayment Failed
mihpayid=27553387529
&mode=CC
&status=failure
&key=1LtbLt
&txnid=adanilounge-fef018ea-dd58-4af9-bce2-9d1920a93421-1
&amount=2.00
&addedon=2026-03-04+14%3A47%3A38
&productinfo=Description+not+provided
&firstname=CARDHOLDERXXXXXXXXNAME
&lastname=CARDHOLDERXXXXXXXXNAME
&address1=
&address2=
&city=
&state=
&country=
&zipcode=
&email=name%40mail.com
&phone=##########
&udf1=fef018eadd584af9bce29d1920a93421
&udf2=loungeone
&udf3=loungeone
&udf4=fef018eadd584af9bce29d1920a93421
&udf5=0
&udf6=
&udf7=
&udf8=
&udf9=
&udf10=
&card_token=
&card_no=XXXXXXXXXXXX6509
&field0=
&field1=7726158727156987305915
&field2=
&field3=
&field4=
&field5=93
&field6=05
&field7=AUTHNEGATIVE
&field8=93+%7C+Transaction+cannot+be+completed%3B+violation+of+law+%7C+Transaction+cannot+be+completed%3B+violation+of+law
&field9=Transaction+declined+due+to+card+not+enabled+for+online+transactions+or+user+%2F+Bank+Defined+Restrictions
&payment_source=payuS2S
&cardToken=
&authenticaticationMethod=
&PG_TYPE=CC-PG
&error=E325
&error_Message=Bank+denied+transaction+on+the+card.
&net_amount_debit=0
&discount=0.00
&offer_key=
&offer_availed=
&unmappedstatus=failed
&hash=eded314a21cc033d3c9d620006492b76a430bef7f0d661313a6ed9f5717fa7dca8c6ec885cba8ecfdf95396fce3a5ef1a55e42c4b9f0fc8fcab0767e80130eeb
&bank_ref_no=7726158727156987305915
&bank_ref_num=7726158727156987305915
&bankcode=CC
&surl=https%3A%2F%2Fapi.juspay.in%2Fv2%2Fpay%2Fresponse%2Fadanilounge%2FmozmFhdZrfsT69TfhWB
&curl=https%3A%2F%2Fapi.juspay.in%2Fv2%2Fpay%2Fresponse%2Fadanilounge%2FmozmFhdZrfsT69TfhWB
&furl=https%3A%2F%2Fapi.juspay.in%2Fv2%2Fpay%2Fresponse%2Fadanilounge%2FmozmFhdZrfsT69TfhWB
&threeDSVersion=2.2.0Payments Event Payload Parameter Description
Parameters and Description
| Parameters | Description |
|---|---|
| mihpayid | Unique transaction ID assigned by PayU for each transaction. Use for inquiry or refund. |
| key | Merchant key identifying the merchant's PayU account; same as in the transaction request. |
| txnid | Transaction ID (Order ID) that was sent by the merchant in the transaction request. |
| amount | Original payment amount sent in the transaction request by the merchant. |
| productinfo | Product description sent in the transaction request. |
| firstname | Customer first name as sent in the transaction request. |
| lastname | Customer last name as sent in the transaction request. |
| Customer email as sent in the transaction request. | |
| phone | Customer phone number as sent in the transaction request. |
| address1 | Customer address line 1 (from request). |
| address2 | Customer address line 2 (from request). |
| city | Customer city (from request). |
| state | Customer state (from request). |
| country | Customer country (from request). |
| zipcode | Customer zip/postal code (from request). |
| udf1 – udf10 | User-defined fields (udf1–udf5 documented; udf6–udf10 in response). Same values as sent in the transaction request. Character limit 255 for udf1–udf5. |
| hash | Hash calculated by PayU. Merchant must verify it before marking the transaction success/failure to ensure integrity. See Response Handling. |
| status | Outcome of the transaction: success, failure, or pending. Treat only success as successful. |
| error | Error code indicating the reason for failure (e.g. E500). Failure reasons vary by bank. |
| error_Message | Human-readable error message. Refer to Error Codes for the list. |
| PG_TYPE | Payment gateway type used for the transaction (e.g. CC-PG for credit card, DC-PG for debit card, UPI-PG, CASH-PG, EMI-PG, BNPL-PG, QR-PG). |
| bank_ref_num | For successful transactions, the bank reference number generated by the bank. |
| bank_ref_no | Same as bank_ref_num; alternate parameter name for bank reference number. |
| unmappedstatus | Transaction status in PayU’s internal system; can include intermediate states. Values include: dropped, bounced, captured, auth, failed, usercancelled, pending. See Payment State Explanations. |
| surl | Success URL – URL on which PayU redirects when the transaction is successful. |
| furl | Failure URL – URL on which PayU redirects when the transaction fails. |
| curl | Cancel URL – URL used when the user cancels (character limit 50 in request). |
| addedon | Date and time when the transaction was recorded (e.g. 2026-02-27 14:24:42). |
| discount | Discount amount applied (e.g. 0.00). |
| net_amount_debit | Net amount debited from the customer. |
| additionalCharges | Additional charges applied (e.g. convenience fee). |
| payment_source | Source of the payment (e.g. payu). |
| pa_name | Name of the payment aggregator through which the transaction was routed (e.g. PayU, RazorPay). Shown when using Maximiser / other aggregators. |
| offer_key | Key of the offer applied, if any. |
| offer_availed | Indicates whether an offer was availed. |
| authenticaticationMethod | Authentication method used (e.g. 3DS). Note: name may appear with typo in payload. |
| field0 – field9 | Gateway- or flow-specific fields. Content varies by payment mode and outcome (e.g. bank reference, RRN, auth result, status message). For cards, field7/field8/field9 often carry auth result or message (e.g. AUCNEGATIVE, UNKNOWN, Message Received Invalid). |
Payment State Explanations
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.
Status and Description
| Unmapped Status | Status | Description |
|---|---|---|
| auth | Success | 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). |
| captured | Success | The transaction is successful. |
| userCancelled | Failure | This status is used when a transaction is canceled by the customer. |
| bounced | Failure | 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. |
| dropped | Failure | 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. |
| failed | Failure | 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. |
| autoRefund | Failure | When PayU initiates refund for the transaction where PayU got success during reconciliation. |
| initiated | Pending | When the merchant lands on PayU's page, the transaction status will be initiated. |
| in progress | Pending | 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". |
| pending | Pending | The pending state of a transaction occurs when a payment has been initiated but not yet completed. Further, it will be moved as per the payment gateway response, such as captured, failed, bounced, or dropped. |
Refund Successful
{
"additionalValue1": null,
"bank_arn": null,
"refund_mode": "Instant Credit through UPI",
"bank_ref_num": "100142082006",
"key": "IahMJL",
"amt": "72.00",
"remark": null,
"status": "success",
"token": "PZT2506150013OR4AN33",
"mihpayid": " 23907365951 ",
"request_id": "17265314530",
"merchantTxnId": "PZT2506150013OR4AN02",
"additionalValue2": null,
"action": "refund"
}Refund ARN Update
{
"additionalValue1":null,
"bank_arn":308239782136,
"refund_mode":"Instant Credit through UPI",
"bank_ref_num":"308239782136",
"key":"lF76TH",
"amt":"149.00",
"remark":null,
"status":"success",
"token":"DG0036362",
"mihpayid":"17025521702",
"request_id":"11865427756",
"merchantTxnId":"ORDER_33172661_1679394745",
"additionalValue2":null,
"action":"refund"
}Refund Failure
{
"additionalValue1": null,
"bank_arn": null,
"refund_mode": "Instant Credit through UPI",
"bank_ref_num": "100142082006",
"key": "IahMJL",
"amt": "72.00",
"remark": null,
"status": "failure",
"token": "PZT2506150013OR4AN33",
"mihpayid": " 23907365951 ",
"request_id": "17265314530",
"merchantTxnId": "PZT2506150013OR4AN02",
"additionalValue2": null,
"action": "refund"
}Refunds Payload Parameters
Parameters and Description
| Parameter | Description | Source Data |
|---|---|---|
| merchantTxnId | String Merchant Sale transaction id Character Limit: 50 | |
| mihpayid | String payuid Character Limit: max 255 chars | Var1 for refund initiate API |
| bank_arn | String Reference number for refund tracking Character Limit: 45 | |
| bank_ref_num | String Bank reference number Character Limit: 255 | |
| request_id | String Unique refund id generated by payu Character Limit: 255 | |
| token | String Unique refund txn id provided by merchant Character Limit: 23 | Var2 for refund initiate API |
| action | String refund Character Limit: 32 | |
| amt | String Refund amount Character Limit: 65 | Var3 for refund initiate API |
| status | String Status of the refund Character Limit: 32 | Possible values: success/failure |
| additionalValue1 | For future scope | |
| additionalValue2 | ||
| key | String Merchant key Character Limit: 20 |
Dispute
{
"type": "payments",
"event": "dispute",
"reason_code": "Fraud - Card Present Environment",
"created_at": "2025-01-15T21:28:25.000+05:30",
"updated_at": "2025-05-27T22:08:16.000+05:30",
"mid": "2",
"cb_id": 1761758,
"txn_id": "999000000000468",
"cb_type": "RBI/BO",
"due_date": "2025-03-31",
"cb_amount": "1.0",
"cb_status": "Bank Comm Sent"
}Dispute Payload Parameters
Parameters and Description
| Field | Description |
|---|---|
| type | Type of transaction and merchant must include the value as payments only. |
| event | Event type and the merchant must the include the value as dispute only. |
| reason_code | Reason for the chargeback. For the list of reason codes, refer to Reason codes for chargebacks. |
| created_at | Timestamp when the chargeback was created |
| updated_at | Timestamp when the chargeback was last updated |
| mid | PayU Merchant ID |
| cb_id | Chargeback ID |
| txn_id | This is the PayU transaction ID that is associated with the chargeback. |
| cb_type | Type of chargeback (for example, "RBI/BO", that is, Reserve Bank of India/Banking Operations) |
| due_date | Due date for the chargeback resolution |
| cb_amount | Amount involved in the chargeback |
| cb_status | Current status of the chargeback. For the possible chargeback status values, refer to cb_status field values description |
cb_status Parameter Values
Parameters and Description
The cb_status or chargeback status field can have the following values:
| Chargeback Status | Description |
|---|---|
| New | It indicates that a new chargeback has been initiated by the customer basis the chargeback reason. |
| Pending Response | It indicates that the chargeback is awaiting merchant response, that is, to accept, partially accept or decline with evidence. |
| Pending Doc Review | It indicates that merchant has submitted their response, and the response are being reviewed by the PayU Chargeback team. |
| Submitted to Bank | It indicates that the PayU Chargeback team has completed their review and forwarded the evidence to the bank for representment. |
| Insufficient Document | It indicates that the PayU Chargeback team has reviewed the evidence documents and is requesting the merchant for additional documents for representment or the correct document based on the Chargeback team's comment. |
| Closed Customer Favour | It indicates that that the chargeback has been closed in the customer's favour. The merchant will lose the chargeback amount to the customer. |
| Closed in Merchant Favour | It indicates that the chargeback has been closed in the merchant's favour. The chargeback amount will be reversed back to the merchant account. |
| Closed under Fraud Liability | It indicates that the chargeback has been closed since the transaction has been identified as fraudulent. Moreover, PayU will cover the chargeback amount under the fraud liability program so the chargeback amount will be reversed back to the merchant account or will not be debited from the merchant's account. |
Webhook Logs
You can now view the webhook logs on your dashboard by navigating to:
Dashboard -> Developers -> Webhook logs
Ensure that your webhook URL is captures and handles the posted response payload. Additionally, you may use the Transaction Callback API to manually test the response payload:
Updated 9 minutes ago