We dove into why developer experiences are gaining criticality in my last post. Part of the post focused on APIs (Application Programming Interfaces) & use cases they enable. Often referred to as the plumbing beneath the modern application development infrastructure, APIs seem to be everywhere. The $5.3B Plaid acquisition by Visa and the PSD2 mandate enforced in Europe were just the latest high profile examples that shone the spotlights on this. In this post, we dive deeper into an exciting revolution in the Fintech industry and understand the value driven by APIs.
Traditionally the financial industry has been extremely conservative. An unwillingness to share proprietary data, solitary risk averse initiatives, and a general lack of innovation has been typical of the industry. In most cases, the factors driving these have been for all the right reasons – managing finances is a big responsibility and the tiniest misstep can have huge implications on individuals or entire economies. The benefits to fostering innovation have always been outweighed by the risks involved, until recently! The rise of APIs has changed this very cost-benefit tradeoff – APIs are increasingly used to drive secure relationships between entities, fundamentally changing traditional assumptions. These relationships could be between different organizations or within the same organization and eventually foster a much faster pace of innovation. Let’s dive deeper by looking at two examples of how this works:
The PSD2 Mandate
The revised Payment Services Directive (PSD2) regulation went into effect in Europe last year. The mandate has two key components – Strong Customer Authentication (SCA) and Open Banking. Diving deeper, there are many layers but at a high level, both components are focused on requiring financial institutions to expose proprietary data and payment services within their platform via APIs in a safe, standardized manner to enable innovation.
Consider mint.com – an aggregator of finances for individuals. Mint.com uses APIs to build secure relationships with different financial institutions and retrieve user data as long as the individual provides consent. A user with finances spread across many financial entities can now have a single aggregated view of their financial health on the company app. This significantly reduces complexity that comes with managing one’s finances and empowers users to make smarter decisions. Another example is Trustly – an app that empowers consumers to directly use their bank accounts to pay for expenses. By providing an alternative to credit card networks, Trustly avoids unnecessary approval loops, chargeback fees, and enables a single payment system for businesses dealing with different currencies. Trustly too has built relationships with banks across the world facilitating a more seamless experience for the end consumer.
In a nutshell, by mandating PSD2 regulations European regulators hope to open the financial sector to more collaboration and innovation driven by the mint.com and Trustly’s of the world. They hope to offer consumers more choice, and ultimately a richer smarter experience.
The Plaid Story
Plaid, founded in 2013, goes one step further to the companies we mentioned in the above section. Conceptually, it aims to be the connective tissue under in a world where collaboration among financial institutions is table stakes. Unlike mint.com or Trustly, Plaid does not focus on specific use cases – it simply acts as a technology layer that enables applications to connect with user bank data by building relationships on both ends.
Plaid focuses on two critical value propositions that enable this layer:
- An ecosystem of hundreds of partner financial institutions and applications that it has built relationships with. Their financial ecosystem partnerships here include 9,600 partners today including all the prominent household names.
- Providing a single extremely reliable API that abstracts away the complexities that come with dealing with APIs for different institutions. APIs have a learning curve and it can often be difficult to get familiar with individual APIs for different organizations. Furthermore different applications and organizations might have different security standards, and the ability to trust a partner is key in developing an API based partnership. Plaid abstracts this out by building a simple, standard, secure interface on top with individual organization and application APIs. For example, notice their API endpoints here – a simple set of extremely secure public facing APIs are connecting to individual APIs belonging to different institutions under the covers. Individuals or businesses wanting to build their own integrations don’t need to know about these – they simply leverage and trust the Plaid layer.
It should be apparent by now why Visa paid a premium to acquire Plaid. Trust based credit card transactions powered by Visa form the foundation of payment networks around the world. That world is changing – and Plaid’s business model and technology stack directly play into the Visa’s very value proposition. By acquiring the company, Visa hedges its bets today and is prepared for the new world tomorrow.
The examples above are only two among many recent and expected upcoming moves within the financial sector, fueled by an API-first economy. The key term we have reiterated in the example above is trust based partnerships. Secure APIs today are the engine below this, and drive innovation in a more collaborative, innovative world.