The "API Economy" has unleashed a real tsunami in business sectors where technology and software development are a major part of its core generation of revenue and earnings. For banking institutions, technology and software development is a key element, whether or not they are platforms as a service (PaaS). Data storage, infrastructure, applications, identity, payments… there are numerous fields of interest for banks whose essential aspects have undergone a transformation through APIs.
The “API Economy” has unleashed a real tsunami in business sectors where technology and software development are a major part of its core generation of revenue and earnings. For banking institutions, technology and software development is a key element, whether or not they are platforms as a service (PaaS). Data storage, infrastructure, applications, identity, payments… there are numerous fields of interest for banks whose essential aspects have undergone a transformation through APIs.
In the Programmable Web directory, with more than 18,000 application programming interfaces in an infinity of fields, over 1,300 APIs are focused on the banking sector, financial sector or linked to crypto-currencies such as bitcoins. In general, the market is estimated to include 2,200 financial APIs. There are numerous companies, startups or organizations that develop interfaces to boost innovation, find new markets for business development or reach agreements with partners who can allow them to improve or grow; or include a business model in the APIs themselves, basically of three types: pay-per-use, subscription, or a revenue distribution model.
A Mulesoft report entitled the 2016 Connectivity Benchmark Report, reflects how 91% of the companies in the world have an API strategy. Banks are one example in fields such as applications, business and development.
In the special case of financial institutions, the use of application development interfaces can be analyzed in a number of different areas, although there are bound to be some more and in no case is this classification an industry standard. First are payments, basically influenced by the consumption of products and changes in habits in the mobile era; then there is the use of data related to bank accounts, transfers or debit and credit cards; and the management of identity in the processes of authentication and security.
Mobile payments and APIs
Mobile payments are possibly one of the areas where the fintechs have found the best breeding ground for their interests. There are many startups that have launched projects as payment initiation service providers (PISPs). According to the Ditrendia Report: Mobile in Spain and in the World, the number of mobile banking users has grown above 800 million and continues to grow. This, combined with the type of user, makes mobile payments into a business opportunity: 45% of young people recognize that they only access their bank accounts through their mobiles to pay bills and make transfers. There are no revenues despite the trend in habits and users.
In recent years, various fintech companies have entered strongly into the world of mobile payments. Three examples are Square, the mobile payment company created by the founder of Twitter, Jack Dorsey; SumUp, the German startup founded in 2011, in which BBVA Ventures invested at the end of 2013, the bank’s first operation of this type in Europe; and iZettle, one of the major players in mobile payments in Europe, which entered into an agreement with Santander to grow in the Spanish market.
Their main business fundamentally depends on the quality of their software development kits (SDKs) and APIs, for both iOS (Apple) and Android (Google) devices. The current domain of most of the Square market is based on the good level of acceptance for its API among the developer community. Currently the company Dorsey has five APIs: Register API, E-Commerce API, Items API, Reporting API and Employees API.
The accumulation of customer data by banks is the object of desire of fintechs. It is the accumulated knowledge resulting from the traditional system of commercial banking. Financial institutions are developing APIs that facilitate access to this information, provided that they comply with conditions that guarantee privacy and security, so that third-party developers can create mobile products. The banks obtain revenues from this initiative, but also talent, innovation and new ideas.
One of the most ambitious banking initiatives in the platform as a service (PaaS) model is the Capital One project. Among the enterprise’s APIs is one that manages data related to the gift points accumulated by Capital One customers, called Rewards API. This API enables can monitor the balance of the account, make savings plans, generate content for exchanging these rewards, create synergies with establishments where you can change these gift points for other products, etc.
BBVA is another of the entities that has made a firm commitment to become a platform as a service. Its Open Platform project is a clear example, with various APIs focused on the management of bank data related to accounts, transfers or cards (Accounts API, Money Transfer API and Cards API). These three APIs always function together with a fourth: BBVA Connect API. All of them are API RESTful, based on an OAuth2 security protocol and programmed using various programming languages: Java, Curl and Python.
Banking identity management
The management of identity data (authentication processes) is undoubtedly the last area that will remain reserved for the exclusive operation of banks, above all in the post-PSD2 scenario (Revised Directive on Payment Services), the regulations by which the financial institutions must transfer access to data and payment services to third parties. The banks will have to ensure the security of the management of our banking identity and financial information with the entry of new leading players specialized in payment services.
Within this sector there is always talk of biometrics as an element for identifying customers and increasing security against bank fraud. This security is based on the science and technology of biological data analysis, including DNA, fingerprints, retinas, voice and face patterns, etc. Any project of this kind needs the design of APIs that make access to identification data easier. This has one advantage: third-party suppliers will be able to offer financial services to people who are not bank users.
Although as of today, it is governments rather than banks who are acquiring this technology, some actors in the financial market such as VISA, the manufacturer of credit and debit cards, have undertaken pilot experiments for customer authentication using biometric data in card transactions. The process identifies customers through the palm of the hand, the iris, the voice or facial biometrics. For this type of technology to expand, scalable solutions will be needed based on open standards: in other words, more APIs
Banco Bilbao Vizcaya Argentaria, S.A. owner of this portal uses cookies and/or similar technologies of its own and third parties for the purposes of personalization, analytics, behavioral advertising or advertising related to your preferences based on a profile prepared from your browsing habits (e.g. pages visited). If you wish to obtain more detailed information, consult our Cookies Policy.
Cookie settings panel
These are the advanced settings for first-party and third-party cookies. Here you can change the parameters that will affect your browsing experience on this website.
Technical Cookies (required)
These cookies are used to give you secure access to areas with personal information and to identify you when you log in.
Name
Owner
Duration
Description
gobp.lang
BBVA
1 month
Language preference
aceptarCookies
BBVA
1 year
Configuration Accepted Cookies
_abck
BBVA
1 year
Helps protect against malicious website attacks
bm_sz
BBVA
4 hours
Helps protect against malicious website attacks
ADRUM_BTs
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT1
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BTa
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
xt_0d95e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
__s9744cdb192d044faa1bf201d29fafd1e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
wpml_browser_redirect_test
WPML
Session
Text translation in the portal
wp-wpml_current_language
WPML
24 hours
Text translation in the portal
Analytics Cookies
They are used to track the activity or number of visits anonymously. Thanks to them we can constantly improve your browsing experience
Your browsing experience is constantly improving.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
AMCV_***
Adobe Analytics
Session
Unique Visitor IDs used in Cloud Marketing solutions
AMCVS_***
Adobe Analytics
2 years
Unique Visitor IDs used in Cloud Marketing solutions
demdex (safari)
Adobe Analytics
180 days
Create and store unique and persistent identifiers
sessionID
Adobe Analytics
Session
Launch's internal cookie used to identify the user
gpv_URL
Adobe Analytics
Session
Adobe Analytics plugin: getPreviousValue Capture the value of a certain variable in the following page view, in this case the prop1
gpv_level1
Adobe Analytics
Session
Cookie used to store the DataLayer levl1 of the previous page.
gpv_pageIntent
Adobe Analytics
Session
Cookie used to store the pageIntent of the previous page.
gpv_pageName
Adobe Analytics
Session
Cookie used to store the pagename of the previous page.
aocs
Adobe Analytics
Session
Cookie that stores the first values collected at the beginning of a process.
TTC
Adobe Analytics
Session
Cookie used to store the time between the App Page Visit event and the App Completed event.
TTCL
Adobe Analytics
Session
Cookie used to store the time between the LogIn event and App Completed.
s_cc
Adobe Analytics
Session
Determine if cookies are active
s_hc
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_ht
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_nr
Adobe Analytics
2 years
Determine the number of user visits
s_ppv
Adobe Analytics
Permanent
Adobe Analytics plugin: getPercentPageViewed Determine what percentage of the page a user views
s_sq
Adobe Analytics
Session
ClickMap/ActivityMap features
s_tp
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_visit
Adobe Analytics
2 years
Cookie used by Adobe to know when a session has been started.
Advertising Cookies
They allow the advertising shown to you to be customized and relevant to you. Thanks to these cookies, you will not see ads that you are not interested in.
The advertising is customized to you and your preferences.
Your choice means you will not see customized ads, only generic ones.
Name
Owner
Duration
Description
OT2
VersaTag
90 days
VersaTag Cookie used to store a user id and the number of user visits.
u2
VersaTag
90 days
VersaTag Cookie where the user ID is stored
TargetingInfo 2
MediaMind
1 year
Cookie that serves to assign a unique random number that generates MediaMind.
Customization Cookies
These cookies are related to general features such as the browser you use.
Your experience and content have been customized.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
mbox
Adobe Target
9 days
Cookie used by Adobe Target to test user experience customization.
Looks like you’re browsing from MexicoSpainArgentinaPeruColombiaBelgiumChileUSAFranceHong KongItalyPortugalUnited KingdomTurkeyUruguayVenezuelaAlemania, so let’s show you the custom content for your
location. Change
Select a country
In order to access the private area and corresponding sandbox, select the country of the APIs you want to use.