Status code & Description

Novalnet provides various status codes along with detail status descriptions to each status as per the error types, which shall be displayed to the end-customer in real time, as per your requirements. Refer Error codes to know the list of status codes and it's descriptions.

API Status

For every API connection establishment, Novalnet returns the status codes that directly imply the result of the action performed. The details about the status codes can be found in the result block of the JSON response.

As simple as it gets, the decision making about the API/Notification result will solely depend on the parameter status under the object result. The parameter can take up either of the values SUCCESS or FAILURE.

Response
{  
		......
		......
		
   "result":{
      "status":"SUCCESS",
      "status_text":"Successful"
      "status_code":100
   },
        ......
}

Refer the sample response below for a failure API action,

Response
{  
        ......
        ......
                
   "result":{
      "status":"FAILURE",
      "status_text":"The payment method is temporarily unavailable, please try again later"
      "status_code":300085
   },
        ......
}

The entire list of error codes along with the description can be found in this >>link<<

status Denotes the resultant status of the API

Example: SUCCESS|FAILURE
status_text The short description of the status. These texts can be shown directly to the end-customer based on the passed language in the request.

Example: Successful
status_code A unique code that can be useful at times to perform operations on specific codes.

Example: 100

Transaction Status

Transaction status directly implies a state about the transaction itself. The details about the status codes can be found in the transaction block of the JSON response.

Response
{  		
   "transaction":{
      "status":"CONFIRMED",
	  .......
	  .......	
   },
      .......
}
PROGRESS A temporary state when the user is redirected to a third party website or banking APP to complete the purchase, or when the user is prompted for 3D Secure authentication. A transaction that remains in the temporary state for longer than 60 minutes will automatically be updated to a FAILED state.
CONFIRMED When the amount is booked in realtime or when the end-customer pays the entire amount directly (mostly relevant for the post-pay payment methods).
PENDING This occurs when the transaction still needs to be verified.
ON_HOLD When the transaction is only authorized, the money will be booked here only after the capture action.
DEACTIVATED Cancelling an authorized transaction will result in this transaction status. In some cases, whenever the payment method goes to a pending flow, the outcome can result in a DEACTIVATED transaction status. Situations like performing a full refund over the Invoice payment (before payment) will lead to the DEACTIVATED state.
FAILURE This occurs when the redirect payment has been cancelled or failed.

Related Topics