Bill Payment API

curl --location --request POST 'https://<hostName>/payu-nbc/v1/nbc/billpaymentrequest?agentId={agentId}&customerParams={customerParams}&deviceDetails={deviceDetails}&paidAmount={paidAmount}&paymentName={paymentName}&refId={refId}&billerId={billerId}&paymentDetails={paymentDetails}&userDetails={userDetails}&isQuickPay={isQuickPay}&timeStamp={timeStamp}&planId={planId}&additionalParams&COUcustConvFee&planDetails&directBillChannel&payByLink&paymentRefID' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>'

📘

Notes:

• In case of a failure response, if the message is payment_request_pending, this transaction should be considered as in progress by the agent. For terminal status, a payment status call is required. 
  The agent should consider transaction status as pending in case of any exception received from PayU in payment or status API response. 
• The agent should not override transaction status against the same reference ID in repeated requests. Ideally, each Payment Request should be raised with a unique Ref Id. 
• As the Bill Payment API is transactional, so to avoid any issue like duplicate RefId, make sure to post a request with a unique reference ID for a payment call. Each call is mandatorily required to be posted with a unique RefId only. Our fetch flow & payment flow go hand in hand with one reference ID. In case of any issue with the Bill Payment API, Bill Payment Transaction Status API must be used.  For more information, refer to Bill Payment Transaction Status API.

For the following exceptional cases, PayU recommends using the Bill Payment Transaction Status API, which will provide the correct status for payment. 

• Connection Failure/ Socket Issue  
• CU is Down
• Payment Status as Pending
• Payment Status as Failure with ErrorCode: “BBPSERR001”

Success scenario

{
   "code":200,
   "payload":{
      "timeStamp":"<server timestamp when response was sent>",
      "paidAmount":"<paid amount in double>",
      "refId":"<reference id>",
      "message":"bill paid to biller",
      "billerId":"<biller-Id>",
      "additionalParams":{
         "txnReferenceId":"TYY567UII",
         "<key1>":<value1>,
         "<key2>":<value2>
      }
   },
   "status":"SUCCESS"
}

Failure scenario

• Payment request failed

{
  "code": 600,
  "status": "FAILURE",
  "payload": {
    "errors": [
      {
        "reason": "<error Message>",
        "errorCode": "<Error Code>"
      }
    ],
    "refId": "<RefId>",
    "type": "payment_response",
    "message": "payment_request_failed",
    "additionalParams": {
      "Key1": "value1",
      "Key2": "value2",
      "Key3": "value3"
    }
  }
}

• Payment request pending

{
  "code": 600,
  "status": "FAILURE",
  "payload": {
    "errors": [
      {
        "reason": "<error Message>",
        "errorCode": "<Error Code>"
      }
    ],
    "refId": "<RefId>",
    "type": "payment_response",
    "message": "payment_request_pending",
    "additionalParams": {
      "Key1": "value1",
      "Key2": "value2",
      "Key3": "value3"
    }
  }
}