Payout API Response Codes

Enkash’s Payout API provides response codes to indicate the outcome of API requests, ensuring clear communication and efficient error handling for businesses. Properly handling these codes is essential for seamless integration and operation.

Response Codes

Code	Description
0	Success.
1	Failure.
403	APIs not enabled.
403	Encryption failed for response.
409	Beneficiary ID already exists.
409	Transaction ID already exists.
409	Batch Transaction ID already exists.
412	Bank account and IFSC both are required.
412	Invalid nodal bank in request.
412	Invalid checksum in the request.
412	Invalid Company ID.
412	Bank account and VPA are both provided in the request. Please provide only one to add the beneficiary.
422	Invalid encrypted request.
422	Invalid request format.
422	Invalid Client ID.
422	Please provide a valid Beneficiary ID.
422	Please provide a valid name.
422	Please provide a valid Virtual Payee Address (VPA).
422	Invalid or missing parameter in the request.
422	No beneficiary details present.
422	Please provide a valid email.
422	Please provide a valid phone number.

Integration Note

Ensure your application handles all response codes effectively.

Common Scenarios

Duplicate Entries:

409: If a Beneficiary ID, Transaction ID, or Batch Transaction ID already exists, avoid creating duplicates by checking beforehand.

Validation Errors:

422: Ensure all required fields are validated before sending the request, including Beneficiary ID, name, email, phone number, and VPA.

Missing or Incorrect Parameters:

412 / 422: Double-check that the request contains all mandatory parameters and follows the correct format.

Example Error Handling

{  
  "code": 412,  
  "message": "Bank account and IFSC both are required."  
}

Action

Ensure both bank account details and the IFSC code is present in the request to proceed.

Payout API Response Codes