Category

Technology

Eko API Widget

(Updated) Introducing API Widget!

By | Blog, Money Transfer, Remittance, Technology, Uncategorized | 6 Comments

Eko was founded on the basic principle of enabling financial transactions for anybody from anywhere. In the evolution process, Eko pioneered domestic money transfer service where customers earning in cash could simply remit money to their family by visiting a nearby shop. This model brought about Retail 2.0 where every retail shop wanted money transfer service. This Rs. 1 lakh cr per month opportunity also attracted big and small companies in the fray.

 

Open Platform

Eko did a great job of establishing a tech-driven efficient retail network of +25k outlets achieving unit economics. This only means driving maximum business with fewer people and paper involved. We have a mantra at Eko to be “Paper-less and People-less”.

 

The retail model still had a limitation – the business generated was directly proportional to the number of retail outlets acquired. For example, if you have 10 front-line managers each managing 500 outlets, then if the number of front-line managers is doubled then only the business would be doubled. Being a tech company, we wanted to disrupt this equation.

 

In 2015, Eko finally decided to open its platform so that any other third party organization could run a money transfer services on top of Eko’s platform. This was truly revolutionary and democratic since it allowed Eko to service customers in those nooks and corners of the country where Eko did not have any front-line managers.

 

In 2 years, Eko has +200 enterprise partners processing double the amount of transactions than its own retail network.

 

Another Roadblock

Driving inspiration from the Android story, Eko decided to further build the enterprise platform where “Made in India” desi payment applications could be made. While the number of applications using Eko’s platform was increasing but there was another challenge – The small enterprise partners with small or no technology teams were taking significant time (~2 months) to integrate with APIs.

 

With a minimum design and UI/UX background, the small enterprises were struggling to get their services live thereby losing business numbers.

 

Eko’s Interface – “Connect”

On the retail side of Eko’s business, Eko developed a state-of-the-art progressive web app “Connect” combined with an in-house Interaction Framework and an API first back-end.

 

Interaction Framework is, in short, like a content management system for financial transactions. It defines a transaction in terms of one or more financial entities and how they interact with each other. This eases and automates the process of building dynamic yet simple and intuitive process flows for making financial transactions.

 

Open “Connect”

Eko opened Eko’s Connect UI as an API widget for our enterprise partners. Integrating Eko API widget in their application would take care of most API calls and give the enterprise a ready-made UI thereby requiring minimum coding.

 

Eko_Connect Widget

Connect has been built in a modular way using latest web technologies like Web Components, Shadow DOM, etc that enables us to expose and embed any part of the Connect into any other web app in a very secure and seamless manner. We will talk about how to integrate the API widget in detail in another post, meanwhile watch the below video to know more about API widget.

 

 

Widget Roadmap

Eko will further open more transactions like AePS (Aadhaar enabled Payment System), BBPS (Bharat Bill Payment System), recharge, etc on the API widget in future where simply you would change one parameter and the enterprise would be able to use it for other purposes as well.

 

Start your money transfer business here. For any queries drop a comment below or write to us at api.sales@eko.co.in  and we will get you started instantly.

Most popular mobile devices in the Eko merchant network

By | Money Transfer, Remittance, Technology, Wallet

Eko works with a select network of almost 10,000 merchants across almost all the states in India who facilitate remittance services for our customers.

A good portion of our merchants transact on smart-devices. The following is a glimpse of the popular device (manufacturers) that our merchants have used in Aug/ Sept 2016:

ekodevicessep16

Samsung, Xiomi and Micromax win,
followed closely by LYF, Lenovo and Vivo,
surprisingly even Apple figures!

Smartphones ki jay!

How we built the Connect Web App – Part 1 – Breaking from our past

By | Technology

This is a series of posts about our adventure with the most exciting project at Ekoconnectalpha.eko.co.in, the progressive web app enabling Eko‘s merchants to make payments and financial transactions.

The original post is at: blog.abhiweb.com/2016/08/how-we-built-the-connect-web-app-part-1-breaking-from-past

The Past

About eight years ago, Eko introduced the simplest of all interfaces to bring banking, payments and other financial transactions to the masses: by dialing numbers on a basic mobile phone. But as the smartphones and laptops grew in popularity with our merchants, we introduced other smart applications. One of them was a simple web portal for money remittance called “Connect”:

 

The old connect portalThe website was immediately successful with our partner merchants, thanks mostly to its simple three-pane interface for quickly transferring money to any bank account in India.

In the last three years, the old Connect portal has already been used to transact for more than 670 billion dollars.

But soon, money remittance service was not enough. We wanted to introduce more services. The only problem was that our engineers had to individually design and build interfaces for these new services. And we realized…

  • we had to manually design and code each page/interface separately. The process was too slow!
  • the three-pane interface was only suitable for the remittance workflow
  • we needed a different interface for different services

And, as a solution, us lazy folks at Eko came up again with our common mantra:

generalize and automate!

Breaking From The Past

So, we came up with the following solution:

  1. The Interaction Framework: to generalize all the financial services (transactions) supported by our platform into interactions that take place between two or more entities.
    For example, a money transfer is an interaction between two bank/wallet accounts.
    Over this generalization, we defined requests, responses, parameters, complex validations, interaction relationships, interaction flows, dynamic behavior, etc. This became our Interaction Framework!
  2. A Progressive Web App: to build a progressive web app and automate the process of providing new services by leveraging the Interaction-Framework. We decided to use Google’s Polymer (which was still in beta, back then) and build custom web components purely on the front-end web technologies.
  3. An API Backend: to design a backend service on Node.js that would be totally decoupled from the front-end app.

In the next articles of this series, I would elaborate on our design decisions and the final architecture and discuss how we finally built the modern progressive web app.


 

The original post is at: blog.abhiweb.com/2016/08/how-we-built-the-connect-web-app-part-1-breaking-from-past

 

Bitnami