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

ApplePay and the iPhone 6: Resistance Is Futile

Brett KingbyBrett King
September 10, 2014
in Payments
Reading Time: 6 mins read
0
Share on Facebook

AplWatch-Hero-Tumble-PRINT-p191ibutc41guvrek1pqh10lg1n4fIf you’ve followed my bullish ramblings on mobile payments here at Finextra, you’ll know that talk of the coming ubiquitousness of mobile payments is nothing new for me:

  • Why Square Wallet failed, and why Coin card is next… (May 2014)
  • Why payments are disappearing, and mobile will win (Oct 2013)
  • Why the iPhone means the end of Swipe and Cards (Sep 2012)
  • Mobile Payments already exceed Checks/Cheques (May 2012)
  • Forget the NFC argument – Look at Payments Behavior (Feb 2012)

In my first book Bank 2.0 I predicted that Mobile Payments at the POS would overtake card payments by 2016-2017. I’m still bullish on that estimate, but would be the first to admit my biggest surprise in respect to Apple’s announcement was that it has taken them until the iPhone 6 to do payments.

What it means for the industry

We can safely say now that the debate over NFC is over – NFC combined with the use of Tokens is the industry standard moving forward. For those suggesting BLE/iBeacon or other cloud based tech might leap frog, I think it’s been fairly obvious all along that NFC was the chosen standard by the card networks, the only issue has been around implementation and timing. Apple’s adoption of NFC signals that interoperability is a key component of the ecosystem moving forward, but it also probably means we’re going to see signficant morphing of the existing networks around the shift to mobile. Those shifts will be:

  1. Move away from Card numbers to Tokenized Identity as the customer identifier (no more “cardholder” folks)
  2. Card networks become data networks – the data passing before, during and after a transaction becomes just as important as the authorization itself
  3. When we move to cardless ubiquity do card networks just become payment networks with payment and identity protocols?

Technologies like BLE and iBeacon have a role to play here. What we didn’t see in the Apple announcement this time around is how they plan to stimulate in-store activity – how they will encourage use of Apple Pay over other payment modalities or other mobile wallets. This is where iBeacon is part of the long-term play.

As Ian Kar pointed out on Bank Innovation, Apple definitely is making subtle moves into the merchant space, with one key intent.  They want to ensure you interact with your iPhone in-store, ensuring you use their wallet when you pay. Most likely that will be through combining loyalty and merchant rewards/offers contextually.

That is the other exciting thing. Mobile payments are not like card or cash payments, and that is what most pundits who are skeptical constantly miss or discount. The use of mobile allows you to contextualize payments with information, content, location data, behavioral data, deals, etc before and after a payment that you could never do with plastic or cash.

Apple has resolved the modality of payments with this move, but we’re still just getting started on the value ecosystem.

Why did it take Apple this long?

Apple was waiting for the right ingredients to ensure success of their Apple Pay initiative. Apple didn’t want another Maps fiasco, and they wanted to ensure people used the feature. However, the United States being Apple’s primary territory and being the card payments backwater it was, has hindered that adoption because the propogation of contactless POS was poor. Enter Target…

The Target, and Home Depot breaches, just to name a couple are part of a broader systemic issue in the US around an aging mag-stripe infrastructure. There are still some, like Clint Boulton at the Wall Street Journal/CIO Journal who argue that cost of replacement of the POS infrastructure can not be justified on the basis of fraud costs alone (Card Security Costs Outweigh Benefits for Many). The varying estimates of POS replacement US-wide range between $9Bn and $35Bn, and estiamted fraud costs this year range between $6.9Bn and $15Bn. On this basis, the business case actually seems pretty strong, but let’s just look at US card fraud as a whole. While some might debate this, the facts are the US is in serious trouble because of their slow EMV adoption.

As reported in Business Intelligence, the US does 25% of the world’s credit card and debit card transactions, but carries 51% of the world’s card fraud. Regardless of what you think of POS replacement costs, this is an incredible statistic that shows how far behind signature and mag-stripe put the US card business.

Apple now knows that the major merchant acquirers and the card networks are all fully committed to rolling out new EMV capable terminals, that will also support mobile contactless payments. This is key – without this guaranteed momentum, Apple was faced with uncertainity over the horse before the cart problem of a mobile payments capability. For merchants, issuers and acquirers, this makes the decision to invest in retooling the POS networks much easier.

The additional sweetners here are three fold. Firstly, tokenization will avoid much of the type of breaches we’ve seen at Target and Home Depot because the token is only a one-time use thing. Secondly, the move to tokens and the combination of biometrics, etc allow for the emergence of a ‘cardholder present’ approach to interchange rates that will potentially give mobile payments a competitive merchant rate. Lastly, the US might effectively jump straight from magstripe to mobile, especially if issuers can figure out how to reduce the cost of card replacement by moving straight to mobile SE and tokens.

Ubiquity is inevitable

For those skeptical of mobile payments adoption, POS retooling and Apple’s entry into payments signals the final hurdle to mainstream adoption. For the last 200 years we’ve seen a gradual speeding up of technology adoption in society, meaning that today the difference between early adopters and late adopters is often measured in just months. Payments behavior is more embedded than most, but that doesn’t mean it is immune to change. A likely model for adoption rate for mobile payments in developed markets is 2-3 years, based on what we’ve seen around Kindle, iTunes, App and Smartphone adoption over the last 7-8 years.

If you are skeptical about this I think it is important to point out that while debit card use has been increasingly signficantly over the last decade, physical payment methods around cash and particularly cheques (checks) have been in constant decline. If we are to examine customer behavior around payments it is very clear. Physical payments are on the decline, real-time electronic payments are the future of demand and interaction.

Now this doesn’t mean that Apple’s move will bring an end to cash or plastic anytime soon. It does mean that mobile payments will dominate within just a few short years as the instinct for a payment changes.

This is not an instinct just being driven by Apple either. On average, 4,361 out of 100,000 people globally were using mobile-payments services as of June 2013, according to Groupe Speciale Mobile Association, an international mobile-telecommunications group, and the World Bank. In sub-Saharan African, the figure was six times that—with nearly a quarter of the population banking on mobile phones. In more than 9 countries across Africa, mobile money accounts already outnumber physical bank accounts, and in markets like Kenya, mobile payments have long outstripped use of physical cash.

Conclusion

Mobile payments and mobile P2P are the coming ubiquitous form of payment. Apple’s entry into this space simply speeds up this shift, and guarantees a common standard across Visa, Mastercard and Amex networks around NFC and the use of Tokenization. By 2020, it won’t just be the USA that considereds mobile payments the primary modality, but indeed, Africa might get there before the US.

For markets like the MINT (Mexico, Indonesia, Nigeria, Turkey) countries the likelihood that the majority of the newly banked will move straight to mobile is extremely high – they won’t be given a plastic card. Distribution costs won’t support that model.

It won’t matter whether you are a farmer in Kenya, or an Apple Fanboy in New York City – mobile payments ubiquity is inevitable. Apple has just cemented that future into place sooner, rather than later.

 

Apple chooses NFC and Tokens for Mobile

Tags: AppleApple PayBlockchainiPhoneiPhone 6iPhone 6 PlusSales & MarketingTouch ID
Previous Post

Visa, MasterCard in Talks with Mobile Wallets for ‘Cardholder Present’ Rate

Next Post

Venmo Cofounders Said to Have Stepped Down

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

Venmo Cofounders Said to Have Stepped Down

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