Enkash Developer Portal
Home
Home
Login
  1. Home
  • Back to home
  • Bill Payment
  • APIs
    • Generate Authentication Token
      POST
    • Fetch Current Bill
      POST
    • Fetch Biller List
      GET
    • Fetch Biller Categories
      GET
    • Fetch Bulk Bill Details
      POST
    • Get Utility Bill By Reference ID
      GET
    • Get Utility Bill Status
      GET
    • Confirm Debit for Bill Payment
      PUT
    • Initiate Bill Payment via EnKash PG
      POST
    • Create Bill Without Bill Fetch
      POST
    • Create Bill After Successful Bill Fetch
      POST
  • Webhook
    • Setup Webhook Endpoint
      POST
  1. Home

Bill Payment APIs

EnKash’s Bill Payment API uses specific response codes and HTTP status codes to indicate the outcome of API requests. Properly handling these codes ensures clear communication, robust error handling, and seamless integration for your applications.
The guidance below applies to these APIs:
Create Bill Without Bill Fetch
Create Bill API
Get Utility Bill by Reference ID
Get Utility Bill Status
Bill Payment Webhook

API Respons#

Response Codes
These codes are returned in the response_code field of the API response.
CodeDescription
0API call was successful. Check payload for details.
1API call failed. Check response_code and payload for the reason
36Velocity limit breached
37Velocity limit breached
38Duplicate referenceId provided
HTTP Status Codes
The API also uses standard HTTP status codes to indicate the result of the HTTP request.
HTTP CodeMeaning
400Bad request. This could be a field validation error or invalid biller ID
412Missing or invalid input parameters, type mismatch, invalid checksum, or invalid nodal bank/company ID. Also triggered if both bank account and VPA are provided together
422The specified biller is not active
500Internal server error. Could include bill fetch failures
502Server down
503Service unavailable
504Gateway timeout. Suggests trying again after a delay
HTTP Status Codes
2XX (Success)
The request was successfully processed.
Check the billPayStatus and paymentStatus fields in the response payload to determine the actual transaction outcome.
4XX (Client Errors)
Indicates a problem with your request (like invalid data or failed validation).
Treat this as a hard failure. Review and correct your request data before retrying.
Check response_code and payload in the response for details.
5XX (Server Errors)
The server encountered an issue or timed out.
Wait 2–3 minutes, then use the Get Utility Bill Status API to run an enquiry:
If the enquiry returns transaction details, your original request likely completed.
If it returns a 400 with payload: "No utility payment found", the transaction did not go through—so it’s safe to retry.
Checking the Payload for 2XX Responses
If you receive a 2XX HTTP response, inspect these fields in the JSON payload to determine the final payment outcome
billPayStatusIndicates the overall status of the bill payment transaction
Bill Pay StatusDescription
SUCCESSBill payment completed successfully
FAILEDPayment failed. Check paymentStatus and failureReason
IN_PROGRESSWaiting for confirmation from the biller
PENDINGPayment request has been initiated but is not yet complete
Payment Statusis relevant when billPayStatus is FAILED or IN_PROGRESS. It shows the current state of the wallet debit or payment processing
Payment StatusDescription
FAILEDWallet debit failed (for example, due to insufficient funds)
REFUNDEDPayment failed, and the amount was refunded to your wallet
IN_PROGRESSorPENDINGStill processing.
failureReasonIf billPayStatusis FAILED, this field explains exactly why the payment failed
Modified at 2025-07-06 19:56:45
Next
Generate Authentication Token
Built with