The API should be polled using the Exponential Back Off Retry strategy with an initial interval of 2 minutes and the multiplier factor of 2, for subsequent attempts and the cap the maximum gap of retries at 1 day.
Header Name | Header Value |
|---|---|
| application/json |
| SHA256("/v3/transaction/{merchantId}/{merchantTransactionId}/status" + |
Parameter Name | Type | Description | Mandatory |
|---|---|---|---|
|
| Unique Merchant ID assigned to the merchant by PhonePe |
|
|
|
|
|
Response Data Description: JSON Level Fields
Field Name | Data Type | Description |
|---|---|---|
|
| Redundant field. To be ignored by merchants. |
|
| See "TRANSACTION STATUS : Response Code" table for a list of possible values and their meanings. Make use of the value of this field for taking decisions related to the status of the transaction. |
|
| Short message describing the code |
|
| Object containing details of actual response data |
Response Data Description: Data Level Fields
Field Name | Data Type | Description |
|---|---|---|
|
| Unique Id generated by merchant sent in pay request |
|
| Unique Id assigned to the merchant in the PhonePe system. Assigned during merchant onboarding. |
|
| Amount to be credited to the user. (in paise) |
|
| Phonepe transactionId generated for the credit request |
|
| Phonepe internal payment state. This is an informative field. Don’t use this field for making decisions, since new values can be added to it. |
|
| Phonepe payment status code. Please note, this is a string and new values can be added as and when needed. Don’t use this field for making decisions. |
|
| Object containing payment details. |