Common HTTP Response Codes

HTTP Response Code	Type	Description
200	OK	Response returned by our system. See status, tx_status, and message parameters in the response to understand the correct status.
403	Forbidden	It is usually due to sending an incorrect secret-key or timestamp. Please check the generation code in the Authentication section. Also make sure to use your auth_key in the generation code (not the developer key).
404	Not Found	This error occurs when you are passing the wrong request URL, please make sure to check the request URL before hitting the request. Production Base URL: https://api.eko.in:25002/ekoicici/ Staging Base URL: https://staging.eko.in/ekoapi/
405	Method Not Allowed	Check the correct HTTP request method of the APIs from API Reference, for example, GET, POST, PUT or DELETE.
415	Unsupported Media Type	Check the Content-Type of the API from its respective API Reference page and check if you are using the same content-type or not. Example: Content-Type = `application/x-www-form-urlencoded`
500	Internal Server Error	It usually implies that the API is not able to connect to our servers. For staging, remove the port 25004 from the URL. And, in production re-check your URL and HTTP method.

Common Error Messages

message	Resolution
No mapping rule matched	In the URL swap v1 with v2 or vice-versa. If it still does not work then send the request and URL at [email protected].
- Agent not allowed - Agent not allowed to do this transaction - Customer not allowed	Check if the service is ACTIVATED for the user_code. If not then, activate the service for the merchant.
No Key for Response	Please re-check the value of the request parameters. It is either missing or the format is incorrect.
Kindly use your production key	Check if you're using the correct developer key (credentials for staging cannot be used in production).

Response Status Codes

For all financial transactions, status = 0 should be treated as successful else fail and the current state of the transaction can be retrieved from tx_status and txstatus_desc parameter.

For all non-financial requests, you may need to consider both status and response_type_id parameters.

status	Description
0	Success
463	User not found
327	Enrollment done. Verification pending
17	User wallet already exists
31	Agent can not be registered
132	Sender name should only contain letters
302	Wrong OTP
303	OTP expired
342	Recipient already registered
145	Recipient mobile number should be numeric
140	Recipient mobile number should be 10 digit
131	Recipient name should only contain letters
122	Recipient name length should be in between 1 and 50
39	Max recipient limit reached
41	Wrong IFSC
536	Invalid recipient type format
537	Invalid recipient type length
44/45	Incomplete IFSC Code
48	Recipient bank not found
102	Invalid Account number length
136	Please provide valid ifsc format
508	Invalid IFSC for the selected bank
521	IFSC not found out in the system
313	Recipient registration not done
317	NEFT not allowed
53	IMPS transaction not allowed
55	Error from NPCI
460	Invalid channel
319	Invalid Sender/Initiator
314	Failed! Monthly limit exceeds
350	Verification failed. Recipient name not found.
344	IMPS is not available in this bank
46	Invalid account details
168	TID does not exist
1237	ID proof number already exists in the system
585	Customer already KYC Approved
347	Insufficient balance
945	Sender /Beneficiary limit has been exhausted for this month
544	Transaction not processed.Bank is not available now.

Possible values of parameter tx_status:

tx_status	txstatus_desc
0	Success
1	Fail
2	Response Awaited/Initiated (in case of NEFT)
3	Refund Pending
4	Refunded
5	On Hold ( Transaction Inquiry Required)