Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

Why Digital Revenue is Absolutely Critical for Banks

Brett KingbyBrett King
October 28, 2013
in Archive
Reading Time: 6 mins read
0
Share on Facebook

Mobile use is exploding in the banking scene. If you are a retail bank today in the developed world and you don’t have an app for your customers, you are increasingly becoming an exception. Certainly almost every bank in the world today has some form of Internet website and Internet banking capability. However, for most banks, the web and mobile are considered costs – platforms that certainly improve service levels, and lower costs of servicing customers, but that are a net cost to the business.

That’s ironic, because today we have entire businesses that have been built off of the back of revenue from web and, more recently, mobile. If you take the market cap of Alibaba (expected to be north of $150Bn at IPO next year), Amazon ($165Bn), Facebook ($125Bn) alone you already have more than half a trillion dollars in value that is generated by pure-play online commerce.

The disruptive nature of pure-play web retailers has been well documented, and now researchers are starting to quantify specific effects such as so-called Amazon “showrooming” where customers go to traditional retailers[1] to try a product, but buy it on Amazon for price. Modality shift of purchase, for example, the shift in music or book buying behavior, has been as equally disruptive from traditional business models and revenue. This year iTunes turned 10 years old, and in that time music sales in physical storefronts has plummeted by more than half[2]. In 2012 1.4 Billion digital singles were sold in the US alone, which is 7 times the number of CD’s sold in-store during the same period. If you are a record label and you don’t have a digital distribution plan, you’re screwed.

Most retail banking leads I talk to express that their primary concern is that total revenue will suffer, if either support for branch wanes from a consumer perspective or if the bank pulls back on branch budgets or investment. The reality is, however, that in most developed economies there is already clear data showing reduction across the board for branch activity whether it is transactions per month, average number of visits per customer per year, or indeed the most critical measure, revenue per product line. We now understand that for products like Mortgages or Account Opening[3], that web is a key driver for even branch revenue, accounting for 2/3rds of branch traffic for those products.

Most retail banks still overwhelmingly seek to drive to branch as a the default conversion measure for advertising and marketing activities. Married with compliance requirements that often still require in-branch IDV or KYC, and you have a ton of false positives for the remaining branch activities that still produce revenue.

What we know is that just like bookstores and music stores, once the instinct of opening a bank account switches from going to a branch, to downloading to your phone, the physical storefront experience is at threat. Which makes the need for web and mobile revenue absolutely critical for a retail bank.

Ok, so then why are banks historically really bad at delivering revenue online and via mobile?

The historical use of web

For the companies and organizations that published the first, early websites back in the early 90s[4] – the web was a publishing platform. However, by 1995 companies like PizzaHut.com and others were experimenting with what we started to call “Brochureware” – information on products and services that would drive sales. In 1995, many companies were starting to drive revenue via web, including the likes of Amazon.com, WH Smith, Tesco, Virgin Megastores, Interflora, Dixons, PC World and others. The web was now a fully fledged sales channel.

However, Retail Banks never quite saw the web that way in the early days. Primarily because you couldn’t sell bank products and services unless you were a bank, and there just weren’t that many pure-play Internet banks that were built independently of branch networks. So the primary use-case for the Internet became “Internet Banking” – basically a cheaper way to allow customers to transact and do day-to-day banking stuff, instead of requiring them to come into a branch or pick-up a phone. For most banks this was about “channel migration” or reducing the cost to serve customers.

This is why most bank websites in the 1995-2000 timeframe were essentially gateways to a login facility for access to ‘secure’ Internet banking. It is also why the IT team owned web at this stage of the platform’s evolution – because the primary requirement of web was functionality, transactional stability and security. Not revenue.

As bank marketers saw all these e-Commerce businesses growing they demanded access to the bank’s public website platforms to market the brand and sell specific products, but even in 2000, fully five years after Amazon had launched their online bookstore, banks were still only able to rustle up primitive product brochureware. Primarily this was a compliance and process problem. There was simply no way to accept a product application digitally via a web form. Many banks I worked with at this stage either printed out web forms and submitted them to the product teams who handled applications via the branch network, re-entered them in to the same systems the branch teams used, or simply asked customers to ‘fax’ the form to their branch. E-Commerce didn’t really exist for banks at the turn of the century.

When it comes to digital then, we’ve had the web grow up fractured. The public website was owned by marketers who could push messages and campaigns out via the website, but were heavily restricted in terms of what could actually be sold. The assumption was still you would read about a product online and then visit a branch to apply.

Whereas, the secure online banking website was owned by the IT guys who were there to ensure a stable and secure transactional banking experience, but were not measured on a revenue basis. So for the first 6 or 7 years of most Internet banking portals, revenue remained absent. In fact, for many banks today revenue is still absent from behind the login. Which is ironic, because up to 95% of day-to-day web traffic ends up clicking on the login button.

Banks are almost the only businesses that deal with digital this way today. Every other retail business, with the exception perhaps of some utility companies, see the main function of the web as delivering revenue. Banks have always fought this instinct based on the risk of cannibalizing their branch network or on the basis of compliance resistance.

Imagine if Amazon built their websites with the same approach as banks today, you’d have a website that would allow you to look at the entire book catalog, but when you wanted to buy a book would generally force you to visit a physical book store. For existing Amazon customers under this modality, the only real thing you could do online behind-the-login perhaps, would be look at the books you’ve previously bought. When you think about it this way, banks have really screwed up digital when it comes to revenue.

Airlines like Delta or British Airways now generate upwards of 80% of their revenue via digital today. In my opinion, that is what banks could be doing today if they simply enabled revenue digitally.

Solving the revenue problem

When it comes to revenue in the coming pro-digital channel era, no revenue is really bad revenue. It makes no sense to favor branch-derived revenue over revenue from mobile, web, tablet or other channels like an ATM, unless you are desperately trying to justify the ongoing existence of the branch itself. You might argue potential for fraud is a reason for physical IDV and in-branch bias towards revenue, but that still assumes that the identity thieves can’t compromise a physical identity and that the best channel for a customer will always be a branch.

By the end of this decade, just 7 years away, based on the decline in branch activity today, retail banks in the US, UK, Australia, Germany, France and Spain (to mention a few) are going to have to deliver at least half of their revenue via web, mobile and tablet to remain viable. For many banks their lateness to the party on this front means that they will have to outsource acquisition to partners that are already well connected with digital communities of target customers, and competent in positioning offers and products. This will actually serve to further increase the cost of acquisition for basic products from where it stands today, and further erode margin. Not good from an industry perspective.

For revenue to be delivered efficiently the silos will have to disappear. The compliance team will have to start working as consultants to the business to legally unlock revenue opportunities in real-time, or based on the needs of customers that emerge. The campaign marketers who have long battled to raise product awareness and kick that customer into the branch funnel, will find themselves with decreasing CPM effectiveness and decreasing budgets, those budgets having moved to more responsive product experiences or customer journeys.

The key skill sets in this new world will be the data scientists that understand when, why and how customers use bank products, and the storytellers that can place the product or service in the customer’s life when and where they need it. Not pull me into a branch, so I can jump through the risk process.

 

[1] See – Placed: Aisle to Amazon Study, February 2013.

[2] Music sales in-store declined from $11.8 Billion in 2003 to $7.1 Billion in 2012. However, inflation adjusted, that accounts for more than a 50% decline in physical music sales in the last 10 years – source: CNNMoney – http://money.cnn.com/2013/04/25/technology/itunes-music-decline/

[3] See – Web Shopping for Branch Sales, Novantis, August 2013

[4] See Wikipedia Article “List of Websites Founded before 1995”

Previous Post

How Banks Can Compete in The Future

Next Post

Tourism Update: Demand for Southern Exposure Remains Strong

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

Tourism Update: Demand for Southern Exposure Remains Strong

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo