- developer_key - becbbce45f79c6f5109f848acd540567
- Key - f74c50a1-f705-4634-9cda-30a477df91b7 (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
How can i integrate the BBPS?
For the BBPS APIs inetgration refer to the link : https://developers.eko.in/docs/bbps
3 APis have to be integrated for BBPS. Please refer the link "https://developers.eko.in/reference#get-operator-list-api" , "https://developers.eko.in/reference#fetch-bills-api" and "https://developers.eko.in/reference#pay-bills-api"
- Onboard your retailers/merchants on Eko platform using Onboard User API
- Activate service for your retailers/merchants on service_code = 53 (for BBPS API)
- Check the status of the service for the retailer/merchants using the User Service EnquiryAPI
- Integrate BBPS API for enabling BBPS transactions for onboarded retailers/merchants.
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
You need to pass dynamic secret-key and secret-key-timestamp in every request in headers along with developer_key. For the dynamic generation of secret-key and secret-key-timestamp, refer to Authentication . We have sample code available in PHP, Java and C#.
You can check all the API’s for onboarding and AePS APIs with their flow on Postman. You can download the User onboarding and service Activation postman collection here , BBPS APIs postman Collection here
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 BBPS APIs implementation has been done along with the testing utility account number. 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.
You need to pass the dynamic secret-key and secret-key-timestamp for every request
We only accept the requests on the production environment from the whitelisted IP only. You can provide an Indian Server IP for the whitelisting
We are asking for the request_hash parameter also which must be generated in the correct sequence only
On one account we can whitelist maximum if 3 IPS and in order to make the IP whitelisted you need to send an email on [email protected] with your regsitered mobile number / Eko Code and make sure that the IPs must have a geoloaction of India otherwise as per compliance we cannot whitelist the IP outside of India.
If you are working on the staging environment then you must check that if you are generating and passing the secret-key and secret-key-timestamp in the headers along with the correct initiator_id and developer-key and secret-key and secret-key-timestamp must be generated properly. Also, make sure that the aadhar encryption must be done correctly, request must be passed in the correct form of JSON and request_hash generated properly
On the production environment, make sure that you are only requesting from the whitelisted IP and also passing the correct credentials including the correct generation of the secret-key, secret-key-timestamp and request_hash. Also, make sure that the aadhar encryption must be done correctly, request must be passed in the correct form of JSON
You can hit the API first from the postman collection
402 Error code comes when we are not receiving the developer-key from your end. Please check the same
404 error code comes when you are passing the wrong request URL, please make sure to check the request URL before hitting the request.
Please connect with the integration team on [email protected] and menion the environment (UAT / production) you are facing the issue on
Do not test the APIs on the production environment with the dummy values as the details are shared with the bank
Raise the same on [email protected] with the complete request and response along with the request URL
If you are getting this message in the Fetch Bill API then make sure to pass the correct and valid and existing utility account number value
I am getting "Failed to connect to staging.eko.in port 25004: Connection refused / Failed to connect to api.eko.in port 25002: Connection refused" error message, what should i do?
This message is coming because the connection is not being made from your server with our server. Please telnet from your server and check if the connection is being made from your server or not.
The command for staging environment which you have to use: telnet staging.eko.in 25004.
The command for production environment which you have to use: telnet api.eko.in 25002.
Also, in your server settings please check if port 25004 is open for you or not for the staging server and 25002 port must be opened for production environment
I am getting "Name not matched" error message even after passing the correct and exact name mentioned on the PAN card, what should i do?
Drop an email on [email protected] the complete request and response and request URL
Any address must be passed in JSON format
Pass the correct and valid name of the state. Please find the state list which is stored in our database and pass the state value accordingly:
| id | name |
| 1 | Andaman and Nicobar |
| 2 | Andhra Pradesh |
| 3 | Arunachal Pradesh |
| 4 | Assam |
| 5 | Bihar |
| 6 | Chandigarh |
| 7 | Chhattisgarh |
| 8 | Dadra and Nagar Haveli |
| 9 | Daman and Diu |
| 10 | Goa |
| 11 | Gujarat |
| 12 | Haryana |
| 13 | Himachal Pradesh |
| 14 | Jammu and Kashmir |
| 15 | Jharkhand |
| 16 | Karnataka |
| 17 | Kerala |
| 18 | Lakshadweep |
| 19 | Madhya Pradesh |
| 20 | Maharashtra |
| 21 | Manipur |
| 22 | Meghalaya |
| 23 | Mizoram |
| 24 | Nagaland |
| 25 | Delhi |
| 26 | Odisha |
| 27 | Puducherry |
| 28 | Punjab |
| 29 | Rajasthan |
| 30 | Sikkim |
| 31 | Tamil Nadu |
| 32 | Telangana |
| 33 | Tripura |
| 34 | Uttar Pradesh |
| 35 | Uttarakhand |
| 36 | West Bengal |
| 37 | Andhra Pradesh (New) |
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
If getting message on prodution 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 firstl" error message whiel 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 supress the OTP verification in the user onboarding flow
Pass the value of this parameter from your end and it must be a valid utility accout number which is exisiting in real life
Below is the cURL request for the activation of the BBPS service:
curl --location --request PUT 'https://staging.eko.in:25004/ekoapi/v1/user/service/activate'
--header 'developer_key: becbbce45f79c6f5109f848acd540567'
--header 'secret-key: MC6dKW278tBef+AuqL/5rW2K3WgOegF0ZHLW/FriZQw='
--header 'secret-key-timestamp: 1516705204593'
--header 'Content-Type: application/x-www-form-urlencoded'
Replace with your production credentials and in the user_code pass the user code.
Updated 3 months ago