You can drop an email to the integration team on [email protected] with your regsitered mobile number/ Eko code, programming language that you are working on, your developer details, product(s) which you implementing and your query
- developer_key - becbbce45f79c6f5109f848acd540567
- Key -d2fe1d99-6298-4af2-8cc5-d97dcf46df30 (will be used to generate secret-key and secret-key-timestamp). The secret-key and secret-key-timestamp have to be generated dynamically. Refer to the link “https://developers.eko.in/docs/authentication” for the dynamic secret-key and secret-key-timestamp generation
- initiator_id - 9962981729
There are 2 ways to integrate the AePS :
- AePS Gateway : Refer to the link : https://developers.eko.in/docs/aeps
- AePS API / Aadhar pay: https://developers.eko.in/docs/aeps-apis-cash-out
First, you need to onboard your retailer/ merchant using the Onboard user API
Then, activate the service for the users for AePS using the Activate service API in which you need to send the documents via API
Now, check for the status of the user using the user service inquiry API. Make sure that the user must be in an ACTIVATED state in order to start the transaction
Now, implement the AePS Gateway / AePS API as per your choice
Implement the AePS Fund settlement
|Do the transaction inquiry
|Any other value
|Suspicious, contact Eko
For transaction inquiry refer to : https://developers.eko.in/reference#transaction-inquiry
In case of failed transaction, raise a issue on [email protected] if unaware of the reason with the screenshot/ request and response
₹ 10,000 per transaction
5 transactions per Aadhaar per day
₹ 10,000 per transaction
Once you are done with the implementation, you have to share the request and response of the onboard user API, Activate service API and user service Inquiry API and the login credentials with URL with us where the AePS Gateway implementation has been done. In case you have implemented the AePS APIs then share the request and response of all the 3 transactions (cash withdarwal, mini statement and balance inquiry). Also, the requests shared should be from your server and not postman.
Technical team will do the sanity testing to check the flow and then gives you go ahead for the live credentials if everything goes right and will share the production credentials on the regsitered email id.
Sanity Testing is a required step in order to get the live credentials so as to avoid any issues on the prodiction environment and to and fro.
This error message comes because the merchant is already registred with Eko earlier from a diiferent mobile number, ask him to pass the same mobile number if unable to recall drop an email on [email protected] with the compelete request and response of the onboard user API
This is not an error message , we have given the user_code value in the response, map the same and store it with the details in your database
I am getting "Failed!Please try again again after sometime" error message, how can I resolve the same?
Drop an email on [email protected] with the complete request and response along with the timestamp and request URL so that we can check the logs and let you know the issue
This error message comes when we are not getting the request correctly from your end in the form-data. Refer to the link "https://developers.eko.in/reference#activate-service" to check the correct request and also try hitting the API first from the postman.
If getting message on production server then drop an email on [email protected] , for the staging environment drop an email on [email protected] with the complete request and response along with the timestamp and request URL so that the team can check the logs and let you know the issue
I am getting "Failed! do OTP verification first" error message while onboarding a user, how can I resolve the same?
Drop an email on [email protected] or to your RM with your Eko code / Registered mobile number to suppress the OTP verification in the user onboarding flow
Hit the activate service API again with the correct documents and the status will be changed to PENDING and then you need to check hit the user service inquiry API in order to check the updated status of the user on any service.
Updated 5 months ago