Apple's Foray Into Payments

Apple has made two announcements this year that show an expansion into areas outside of the technology industry. The first was Apple Watch, which is most definitely a technology product but looks positioned against the current premium watch industry just as much as against current smartwatches on the market. The second was Apple's foray into the payment industry, Apple Pay. While Apple Watch won't be around until next year, Apple Pay is here right now with one caveat. Apple Pay currently only works in the United States, or more specifically, only with a credit card issued by a United States bank. However, the service will eventually be expanded to support cards issued by banks in other countries.

How Apple pay works is fairly straightforward, that's the entire point of it. If the region on your device is set to the United States, the passbook app will contain a card that allows you to add a credit or debit card. You can then either type your info in, or use your camera to get the information from the card. Once the card is verified by your bank, you will have a card that appears in passbook and you're ready to start using Apple Pay. From the user's perspective, Apple Pay is simple and easy to use. But what goes on behind the scenes to keep everything secure can be quite complicated.

Security

The first thing to know is that your credit card information is never stored on the phone. Upon adding a credit card, the information is encrypted and sent to the appropriate issuing bank which confirms that the card is valid. A token is then sent back to the iPhone and stored in the secure element, which is essentially just an internal smart card chip. This token, not your credit card number, is what is used during payments. Apple's marketing and technical material refers to it as a Device Account Number. The token itself resembles a credit card number, but the only similarity between it and your card is the 4 digits on the end. 

The use of tokens is where much of the security of Apple Pay comes from. By removing the actual credit card number from the equation, the merchant you're paying never gets to see your credit card number, security code, or your name. The token presumably is also only linked to the actual credit card via some database held by the bank, rather than some sort of equation that could be reverse engineered. This means that even in the event where a merchant is hacked and your token number shows up, it is entirely useless because it does not function as a credit card and is tied to the iPhone it was used on.

Beyond the overarching security, there's additional security at the time of payment. It begins with the use of Touch ID for authorizing payments. Although Touch ID launched with the iPhone 5s which does not have the necessary NFC hardware to use Apple Pay, I believe that this sort of service was the original goal when Touch ID was first being created. Paying with Apple Pay requires using Touch ID to verify your fingerprint. This prevents anyone from making purchases using your iPhone if it is lost or stolen.

One thing to note is that Apple Pay is not just a service for making purchases in stores. It also works for making purchases at online retailers than integrate it into their applications. All the security features that I've described apply to both in-store and online purchases, so there's no compromises on either side.

Going Forward

Making Apple Pay successful is going to take a lot of work on both Apple's part and on the part of retailers. Currently the service only works with cards from US banks, leaving out the rest of the world. Apple needs to expand the service much quicker than competitors have done so with theirs. For example, Google Wallet remains a US only service over 3 years after its initial launch. Apple Pay is not going to achieve success if it ends up in the same situation. Apple has given no timeframe for expansion to other countries, but if the iPhone 6 and 6 Plus get replaced by newer models before Apple Pay expands outside the US it will be a worrisome situation.

Apple also needs to convince retailers to support the service. The list of supported merchants on the Apple Pay section of their website has grown since its initial launch, and if Apple Pay is ever going to be a viable way to make everyday purchases that list needs to continue to grow. Work by banks to increase adoption of NFC capable terminals will also speed up this process, as Apple Pay works with existing NFC enabled checkouts. Apple also faces resistance from retailers that are partnered with other payment systems. Recently there have been reports that merchants who support the CurrentC mobile payment standard are disabling NFC on the payment terminals in their stores to block Apple Pay. I don't believe this will be an issue in the long term because consumers will realize when companies are prioritizing their own agenda over the customer's experience and they'll go to other retailers. If Walmart won't support Apple Pay and a customer wants to use it, they'll just go to Target instead.

As someone who doesn't live in the United States, I'm hopeful that the service will expand to Canada before this iPhone becomes obsolete. There are many obstacles in the way, but Apple appears to have put more effort into working with banks and merchants to get the service off the ground than any of the other mobile payment services we have today. How things play out will only be revealed with time.

Continuity Conclusion
Comments Locked

173 Comments

View All Comments

  • blackcrayon - Monday, October 27, 2014 - link

    That's notification center, it was already in Mavericks. And iOS for that matter. It's not exactly like the gadget sidebar but there is some overlap now that you can put custom widgets there.
  • Colin1497 - Monday, October 27, 2014 - link

    Suggestion for 8.1.1: Recalibrate "Motion Calibration" so that it isn't constantly running location services and destroying my battery life, forcing me to simply turn off the functionality. There's no way that it's working as intended when it basically runs location services all the time to the extent that my phone is always warm and my battery only lasts half a day. Obviously everyone isn't having this problem, only people who have apps that tie into "Motion Activity," but it's a legit problem with plenty of discussion on the support forums.
  • Brandon Chester - Monday, October 27, 2014 - link

    Yeah seriously, I turned it off because it runs almost constantly. I don't even know what it's doing but it hasn't impacted my device by not having it.
  • tipoo - Monday, October 27, 2014 - link

    You know what I'd love is some performance tests with it, especially on older hardware, like Core 2 Duo/320M era, and on spinny hard drives. I've held back on upgrading the macbook in the family due to some mixed messages about it, some say it's the same as Mavericks (which I find a dog, tbh, Windows 7 is so much faster on the same system), some say it's a bit slicker in some areas, while others say it tanked performance.

    I've gotten the feeling that OSX has become less optimized for HDDs as they optimized more for SSDs. I wonder if it still even does things like hot file clustering?
  • xrror - Monday, October 27, 2014 - link

    This will sound like a cop out, but I can't recommend strongly enough just getting a cheap SSD for the older core2 iMacs and macbooks. Even without a ram upgrade (stock 2GB), the difference is astounding.
  • tipoo - Monday, October 27, 2014 - link

    I would agree with that, though it's not my own system so explaining and getting someone else to invest in a SSD is a bit of an uphill battle, and besides that I think they'd rather be putting that towards saving for a new system eventually too.

    Maybe I'll give them the Momentus XT hybrid from my dying Dell Studio 1555, that adds a bit of peppiness.
  • DPUser - Tuesday, October 28, 2014 - link

    Only problem is Apple has really put the screws to enabling Trim for third party SSDs in Yosemite.

    http://www.cindori.org/trim-enabler-and-yosemite
  • tipoo - Tuesday, October 28, 2014 - link

    That sucks, but wasn't TRIM killing SSDs in OSX for some reason? It only worked well on Apple certified SSDs.
  • DPUser - Tuesday, October 28, 2014 - link

    Trim works perfectly in OSX with SSDs that support it (meaning all current SSDs). I encourage anyone who cares to lobby Apple to change its policy in this regard: stop locking out Trim for third party SSDs.
  • Penti - Monday, October 27, 2014 - link

    Regarding design, I don't think old users will be shocked. The dock looks essentially the same as in OS X Tiger (10.4 or reminiscence of Ceetah – Tiger 10.0 - 10.4).

    Translucency or semi-transparency has been done for so many years in different Window Managers and shells for *NIX system or Windows Vista–7. While they drop some skeuomorphism they at the same time introduce transparency, new animations and other stuff that Microsoft sacrificed in order to run on low-end devices. They even keep rounded of corners. Though I don't think it's much of a shift, it's more back to the roots of earlier OS X releases and still builds on NeXTSTEP looks in some ways. A simpler cleaner look doesn't go against that. Of course technology and hardware makes some things more natural today than 15 years ago. The roots isn't really on machines capable of translucency or of 16.7+ million colors, or accelerated animations.

Log in

Don't have an account? Sign up now