Enkash APIs
HomePayment GatewayPayoutsCreate Account
HomePayment GatewayPayoutsCreate Account
Login
  1. Payouts
  • Payouts Overview
  • Payouts Sign Up
  • Payout Methods
  • Payout API Response Codes
  • Payouts Integration Steps
  • Encrypting and Decrypting Payload
  • Payouts Status Codes
  • Get Authentication Token
    • Get Authentication Token
      POST
  • Beneficiary Apis
    • Create Beneficiary
      POST
    • Search Beneficiary
      POST
    • Delete Beneficiary
      DELETE
  • Transfer Apis
    • Create Payout
      POST
    • Search Payouts
      POST
    • Create Batch Payout
      POST
  • Payout Account Apis
    • Get Balance
      GET
    • Get Source Bank Account Details
      GET
    • Add Source Bank Account
      POST
    • Fetch Bank Statement
      POST
  • Webhook Data Apis
    • Get Webhook Data
      GET
    • Create Webhook Data
      POST
  1. Payouts

Payout API Response Codes

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#

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

Common Scenarios#

1.
Duplicate Entries:
409: If a Beneficiary ID, Transaction ID, or Batch Transaction ID already exists, avoid creating duplicates by checking beforehand.
2.
Validation Errors:
422: Ensure all required fields are validated before sending the request, including Beneficiary ID, name, email, phone number, and VPA.
3.
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.
Modified at 2025-01-09 20:12:14
Previous
Payout Methods
Next
Payouts Integration Steps
Built with