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 Apple’s NFC snub might hurt the banks and networks more than ever?

Brett KingbyBrett King
September 23, 2012
in Payments
Reading Time: 8 mins read
0
Share on Facebook

I’ve always maintained that Near Field Communication (NFC) was attractive for both the banks acting as acquirers and issuers, and ultimately the networks themselves. Particularly in the US marketplace. Why? The only way to keep the Point-of-Sale (POS) terminal in a transaction as we shift to mobile wallet and mobile payments at merchants is for banks and networks to seamlessly transition cardholders from ‘swipe’ to tap. The longer the banks and networks take to convert to NFC-enabled transactions, the more likely it is that the POS terminal will no longer offer value at the merchant space as we drive to wallet driven payments as opposed to the swipe paradigm.

What did we do before credit and debit card networks? We paid with cash and cheques. This was an asynchronous process that relied purely on you having either cash in your wallet (or your chequebook) and a merchant (we called them store owners back then) who would accept your payment. We might sometimes forget that there was a time when cards were not accepted and the equipment to process a card transaction didn’t exist, or hadn’t been deployed. In the early days the clunky knuckle-busters were the height of technology, but over time the networks started to deploy electronic terminals to reduce fraud rates, and improve clearing times.

It took almost two decades for card payments to become globally ubiquitous, so it might be reasonable to think that a paradigm shift at the POS will take years to become mainstream. Why would you spend money deploying expensive NFC-enabled POS terminals unless consumers were going to use them, right?

In normal circumstances, if there were no competition, this would make good business sense. The problem for the banks and networks is that they think the ‘card’ is defensible – that this product has enough inertia for consumers to not be bothered by the fact that they can’t yet pay with their phone at every POS terminal. In the US, this inertia has not only meant a slow roll out for NFC, but has also seen US merchants slip 7-8 years behind their EU counterparts. In the EU already 75% of cards support the EMV standard, and more than 90% of terminals, whereas in the US only 30% of merchants support EMV. So we hear frequent stories of US travelers in Europe unable to pay for the simplest of purchases or transactions with long outdated card tech. Worse for the US card industry is that the industry is paying 3c of every transaction in preventable fraud right now due to outdated signature and mag-stripe tech.

So you might think that Apple’s NFC snub supports the theory that there’s simply no hurry. Maybe Apple are simply waiting for NFC to become mainstream before they jump in. That’s undoubtedly part of the reason, but I think there’s another explanation, which presents real problems for the incumbents.

Not-for-consumers?
NFC is sometimes referred to by skeptical industry pundits as Not-For-Consumers. But the technology is sound, has been around for more than a decade, and is a logical transition when you are trying to move consumers from a plastic ‘swipe’ to a phone-based ‘tap’.

Let me tell you why I think Apple baulked this time around with NFC. I think there are three main reasons, but has little to do with the consumer adoption angle:

  • Firstly, the most obvious. Apple wants maximum utilization of their device and technology, and it’s likely true that they’re waiting for better US-based infrastructure (their home market and one of their largest) to support phone payments at the POS. Apple is not known generally at leading consumers with new technologies, they weren’t the first with an ‘MP3’ player, neither were they the first tablet manufacturer. Apple is known for their impeccable timing with new technologies, along with creating disruptive ecosystems to support those technologies (like iTunes).
  • Secondly, they don’t control the ecosystem and they’re not keen on providing tech that banks and card networks make money on, but they don’t. While it is true Apple has such phenomenal market and brand power that they could move the market on this, why move the market so that banks and card networks continue to make interchange fee, and Apple makes nothing beyond the handset sale?
  • Lastly, they’ve figured out that they just don’t need to support the existing POS technology to enable payments at all – so the longer banks and networks wait to deploy NFC ready merchant capability, the less likely it is that Apple will go for NFC all together. In fact, the lack of NFC industry adoption means Apple is choosing to pursue support for digital wallet solutions, taking the card and swipe out of payments all together.

Was it a good decision for Apple? That’s highly debatable, although, it isn’t going to hurt iPhone 5 sales. Apple could have re-released the iPhone 3G and called it the iPhone 5 and they probably would have sold 20 million units without blinking.

So does this mean there’s life left in Cards?
Hell no, not a chance. In fact, the lack of NFC roll out is actually creating significant momentum behind a much more serious and disruptive trend. The trend to go cardless and POS-less completely.

While banks and networks have been debating the merits of NFC, and while US merchant acquirers and card issuers have been debating the roll-out of EMV and new POS technologies, there has been a quiet but steadily growing shift towards payment experiences that don’t require a swipe or tap paradigm at all. Pay with Square, PayPal merchant payments, Amazon checkout, closed loop Mobile Apps like Starbucks’ app, or clever applications of back-end payments like Uber, Apple Store (App) and iTunes are rapidly growing in credibility, both at the POS and online through e-Commerce.

The beauty of NFC, for the banking industry, is that the industry could simply have migrated customers from card to phone and all the existing value chain stayed in place. You still needed a bank relationship, they issued you a card number (or Primary Account Number – PAN as it is known in industry speak) and you still went along to a merchant and used you bank generated account (now theoretically on a mobile phone with an NFC chip) to pay a merchant through their POS terminal. It is a simple way to keep the card and swipe paradigm going and it meant that both the issuing banks and the card networks kept getting interchange fee because there was no alternative to their incumbent rails.

The problem for the industry is that right now we’re doing away with the swipe paradigm altogether, primarily because there wasn’t a rapid enough adoption of NFC-enabled payments. We’ve simply circumvented the poor user experience of the swipe card, for a richer user experience on the mobile device.

Why do I say a poor user experience?

We live in a data rich world right now, where we can download books, music, even boarding passes to our phone. We can use our phone to track where our friends and family are, or communicate with them instantly. Our phones can keep track of our fitness levels, and spur us on to new goals of activity. We can use these same devices to find a restaurant, a bargain at a retailer, or just to find directions (that is if you aren’t using Apple Maps…)

Compared with this rich data platform, nuanced user experiences and the amazing capabilities of our smartphones, the humble plastic card is just plain dumb. It can’t tell us anything at all. Even when we use it at the POS, we can only find out if the transaction is approved or declined. When a transaction is declined, we’re none the wiser – we wouldn’t know if it were due to insufficient funds, whether the merchant has screwed up, or whether there is a hold on our card for some other reason. Payments just look dumb, old and out of date.

The driver for reinventing payments is not putting the card into the phone to get rid of the plastic in our wallet – it is about reinventing and leveraging a payment instance married with data. The trouble for the incumbents is that you just don’t need a card, a swipe or even a POS terminal when it gets down to it. A rapid transition to NFC would have saved the swipe-at-a-POS paradigm by allowing for a rich data support envelop around the payment.

With the poor industry adoption of next-gen POS payment tech, consumers and innovators are seeking that user experience without the swipe at all.

Maybe no card is better anyway
If you’ve tried Uber, for example, you would have pre-registered your account online or through an App and then the time comes for your first trip in an Uber car around town. You book a car through the app, and it shows you the driver coming your way via GPS and how far away he is. Then you’re in the car and off to your destination. When you arrive you exit the car and receive a receipt for the trip on your phone via the app. No card, no swipe, a seamless payment and ride experience. It’s the new paradigm of payment – seamless, frictionless, and information rich.

Uber – doesn't need a swipe to offer better payments

 

Alternately you may have recently walked into Starbucks to order a No-Whip, Skim Soy, Mocha Frappuccino and a bagel (toasted), but at the point of sale you simply pull out your phone scan the App-generated bar code and you’re off. Soon you’ll be able to just say your name via Pay with Square at the Starbucks register and the payment will be processed, just like you can at merchants like Gregory’s Coffee today.

Whether it is Square, PayPal, Uber, Dwolla, Venmo, iTunes, Apple Store, Starbucks, or any other App-enabled digital wallet, we’re finding that we don’t need a swipe.

Now I know what you’re thinking – that we still need a card number, we still need an issuing bank, and we still need the merchant rails, right?

For now, yes.

Conclusions
The problem, however, for banks is that value stores such as Dwolla, Venmo, PayPal, iTunes only require you to pay a fee to the bank every time you top-up your value store account. Then, if you’re using a digital wallet to pay, you avoid interchange at the transaction level.

For solutions like Pay with Square, Apple Store, and Uber, there is obviously ongoing interchange fee for the network, but because the swipe paradigm has been removed, the back-end rails could be replaced with another P2P (peer-to-peer) payment network solution that avoids the Visa and Mastercard rails all together, perhaps through use of the cloud.

In fact, the fastest growing payment class today would simply be classified as peer-to-peer electronic payments. Increasingly merchants and consumers are going to be seeking simply to make a payment and the incentives to pay in real-time directly from one bank account to another. This is becoming the holy-grail in payments. The problem is that ultimately a P2P real-time payment could entirely circumvent the card networks.

So whether you are a bank or a card network – the decision of Apple to avoid NFC probably just killed your chances of keeping the status quo of interchange via the card/swipe paradigm.

The likelihood is that the digital wallet, whether via a smartphone initiated payment or simply built contextually into shopping experiences, has got too much momentum now to save the swipe paradigm. The next step is simply to avoid interchange, the networks and traditional value stores all together. That’s where merchants and start-up want to take this, and they’re all leading with a better user experience than the existing incumbents. It’s all up for grabs now…

Tags:apple,google,iPhone,mastercard,Mobile,NFC,Pay with Square,PayPal,Square,Uber,visa,Wallet

Tags: AppleArticlescustomer experienceFuture of BankingGoogleiPhoneMastercardmobileMobile bankingNFCPayPalplatformSquareUberVisaWallet
Previous Post

Why Bank Telephone Customer Service Doesn’t Have to @>!#$*

Next Post

Alternative Financial Services Grow, and So Do the Unbanked and Underbanked

Related Posts

fis
Payments

Fiserv, Global Payments, FIS tap M&A for growth

May 6, 2025
Payments

Fiserv resolves data center outage

May 6, 2025
A car with the hood open
Payments

Auto aftermarket sees rising need for BNPL

May 6, 2025
Next Post

Alternative Financial Services Grow, and So Do the Unbanked and Underbanked

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