Check Payment API

The Check Payment (check_payment) API functions similar to the Verify Payment API. However, the input parameter in this API is the PayUID or mihpayuID generated at PayU’s Server unlike verify_payment API where the input parameter is the TxnID (Transaction ID generated at merchant’s server). It returns all the parameters for a given transaction.

Environment


Test Environment	https://test.payu.in/merchant/postservice?form=2
Production Environment	https://info.payu.in/merchant/postservice?form=2

Sample request

curl --location 'https://test.payu.in/merchant/postservice.php?form=2' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'key=vzKCT7' \
--data-urlencode 'command=check_payment' \
--data-urlencode 'var1=403993715530075847' \
--data-urlencode 'hash=d03c7c49929fd9a07fe7f70c3609a8e245c64b2d7959c01193b4a4f85b6e138b468af8debb44fdb6fbb57d0bd5d96bf881cd88e494f8ce273172297faf5da9db'

Sample response

Success scenario

{
    "status": 1,
    "msg": "Transaction Fetched Successfully",
    "transaction_details": {
        "request_id": 135958975,
        "bank_ref_num": "7103714673656711773162",
        "net_amount": null,
        "mihpayid": 403993715530075847,
        "amt": "10.00",
        "disc": "0.00",
        "mode": "CC",
        "txnid": "d721fcf124b54e56989f",
        "amount": "10.00",
        "amount_paid": "10.00",
        "discount": "0.00",
        "additional_charges": "0.00",
        "udf1": "",
        "udf2": "",
        "udf3": "",
        "udf4": "",
        "udf5": "",
        "field1": "7103714673656711773162",
        "field2": "966739",
        "field3": "10.00",
        "field4": null,
        "field5": "100",
        "field6": "02",
        "field7": "AUTHPOSITIVE",
        "field8": null,
        "field9": "Transaction is Successful",
        "addedon": "2023-09-12 14:50:48",
        "status": "success",
        "net_amount_debit": 10,
        "unmappedstatus": "captured",
        "firstname": "Payu-Admin",
        "bankcode": "CC",
        "productinfo": "Product Info",
        "payment_source": "payu",
        "name_on_card": null,
        "card_no": "XXXXXXXXXXXX2346",
        "PG_TYPE": "AxisCYBER",
        "Merchant_UTR": null,
        "Settled_At": null
    }
}

Failure scenario

If the PayU ID (mihpayuid) is missing:

{
"status":0,"msg":"Some error occurred while processing the request."
}

Response parameters

Parameter	Description	Example
status	This parameter returns the status of web service call. The status can be any of the following: 0 - If web service call failed. 1 - If web service call succeeded	0
msg	This parameter returns the reason string.	For example, any of the following messages are displayed: - Parameter missing - Token is empty  - Amount is empty - Transaction not exists
transaction_details	This parameter contains the response in a JSON format. For more information refer to JSON fields description for transaction_details parameter .

Request parameters

Reference information for request parameters

Parameter	Reference
key	For more information on how to generate the Key and Salt, refer to any of the following: - Production: Generate Merchant Key and Salt - Test: Generate Test Merchant Key and Salt
hash	Hash logic for this API is: `sha512(key\|command\|var1\|salt) sha512`

Sample values

Use the following sample values while trying out the API:

var1 (your transaction ID/order ID): 403993715521889530