Monthly Archives

June 2016

Eko goes open source!

By | Money Transfer, Others, Remittance | No Comments

Team Eko is glad to announce that we are getting started with open source! You now have access to the best optimised algorithms and UI to process money remittance transactions at your merchant network.

Till date, this money transfer web application has processed more than Rs 4,000 crores and is being used by more than 2000 agents across the country.

Available now at: https://github.com/EkoHub/Money-Transfer-Web-Applicaton

blog p1

Now, partners/organizations can use this standalone website and deploy it on their systems. Developers can now modify the code and are free to develop or test our remittance APIs.

Frameworks used:

    1. Python
    2. Django framework 1.5
    3. Knockout.js
    4. Gumby framework

It is recommended to run the project in Virtual Environment  instead of changing the global installations as it stores all the dependencies required for this project in the Project folder itself .

Instructions

  1. Download or Clone the Repository
  2. Please go through readme.txt for installation instructions
  3. After installation (including population of database), please review the workflow
  4.  Workflow
    1. Capture Sender Details
      • The merchant/agent enters “Sender Mobile Number” and presses “Go” button. This invokes “Get Customers API” which returns the following scenarios:
      • If customer does not exist – Invoke “Create Customer API”, which fires an OTP to the customer’s mobile number. On entering the OTP, the application invokes “Verify Customer API”.
      • If customer exists – Redirect to Recipient box
    2. Capture Recipient Details – In case customer exists, “Get All Recipients” API is invoked. If the list is empty or the customer wishes to send money to a new bank account, then the merchant/agent  can add a Recipient by clicking on “Add Recipient
      • Adding a recipient requires the merchant/agent to enter bank name, bank account details and recipient details. On entering the required details, the“Add Recipient APIgets  called. Different banks require different flows for adding a recipient efficiently, which has been explained here: http://blog.eko.co.in/add-recipient-workflow-simplified/
      • Selecting any recipient from the list invokes “Get Recipient API” and agent is taken to the Transaction box as shown in the image above.
    3. Capture Transaction Details
      1. Enter the amount of money to be sent and select the Transaction mode. Clicking on “Send moneybutton invokes Send Money API. The status of transaction is displayed as toast at the bottom of the webpage

This is yet another by-product of Eko’s Summer Internship  program under which we hire students from the best universities across the country and provide them a platform to explore our technology. The open source was developed by Siddharth Jandial (NIT J), Kunal Sachdeva (NIT J), Teja Surya (IIT D) and Alankar Verma (NIT R) under the guidance of Mr. Saurabh Mullick.


Recommended reading:

      1. Tutorial on Django – https://docs.djangoproject.com/en/1.9/intro/tutorial01/
      2. To know more about Virtual Environment – http://docs.python-guide.org/en/latest/dev/virtualenvs/

Add Recipient Workflow – Simplified!

By | Blog, Money Transfer, Others, Remittance, Workflow | No Comments

 

We, at Eko, continue to work on providing a seamless and hassle free payment and transaction experience to our merchants, customers and partners.

For sending money to a bank account, a bank account needs to be mapped to a customer’s wallet. For that purpose, “Add Recipient” API is required. However, since different banks require different field parameters for registering a bank account, we have designed a process that simplifies adding of a bank account to a customer wallet.

We have implemented the changes in workflow in our merchant portal “Connect” for money remittance business and now we want to share the same process with our API partners.

4 Simple Steps for adding a bank account

    1. Capture Bank Name – Enable your merchant/customer to first select the bank (figure 1) to which money needs to be transferred. On selecting the bank name, invoke Get Bank API and Eko shall return the following details about the bank like:
      1. Full Bank Name (parameter name “name”)
      2. Account Verification is available or not (parameter isVerificationAvailable) – This signifies if bank has enabled verification of bank account feature or not. If value returned is “1” then verification is available else it is not allowed.
      3. IFSC code required or not (parameter “ifsc_status”) – Signifies if the IFSC code is required for money transaction or not
      4. Channel available for money transfer (parameter name “available_channels”) – This signifies IMPS is available or not and if not then, NEFT channel needs to be pused. The following values signifies which channel is available:
        -> ALL : 0
        -> NEFT : 1
        -> IMPS : 2

        gif 1

    2. Enter Recipient’s Bank Account Details – As a second step, enable your merchant/customer to enter the following:
      1. Recipient’s Bank Account Number – Only bank account number is required for bank, for whom IMPS is available. The next step is point 3.
      2. IFSC Code – If IMPS is not available for the bank selected. The next step is point 4.
    3. Account Name Verification – If Account verification feature is available, then Account Name Info API needs to be invoked, which instantly pulls out the Name of the recipient by either pushing Rs 1 transaction via IMPS or from Eko’s database. In the example shown in figure 2, it shows that for banks like SBI, etc where IMPS is available and account verification is available, only bank account details are required and recipients details are returned in response to Account Name Info

      gif 2

    4. Capture Recipient Details – If Account verification feature is not available, then following recipient details are required:
      1. Recipient’s Name
      2. Recipient’s Mobile Number
      3. IFSC code of the recipient’s BankIn the example shown below, when “Abu Dhabi Commercial Bank” is chosen as bank, for which IMPS and account verification is not available, bank details and recipient details are required

        gif 3
        In the below example, the customer/merchant has selected “HDFC Bank”, for which IMPS is available but account verification feature is not available, and in such cases bank account number and recipient details are required.

        gif 4

After capturing the details of the recipients, “Add Recipient” API needs to be invoked.