So between squeeing over the watches and squealing over the bendy phones and free music and all the other nonsense that just seems to get sillier all the time, anybody remember that other little thing Apple squeezed into their do?
Apple Pay For Developers
Apple Pay Human Interface Guidelines
Apple Pay Programming Guide
Haven’t seen very much discussion of that yet, but we’re kinda suspecting here it might turn out to be more of a Big Deal than most people are expecting right now. Here’s an excellent article to catch you up if you’ve been in the distracted by the shiny things crowd:
How Apple Pay works and why it matters for developers
Background: Clover and First Data (our parent company) have been working with Apple to prepare for the launch of Apple Pay to support developers, merchant acquirers, and issuing banks (see First Data’s press release). Clover is enabling all merchants to accept In-App payments, and will be In-Person/NFC enabling all merchants as well (see https://www.clover.com/features/iphone). Here’s a bit of how it works from a developer’s perspective, and why it matters…
Apple Pay marks the first time a popular operating system is making payments a platform service for real-world, non-digital-good transactions, in a broad, inclusive manner that is compatible with the mainstream payments processing industry. At Clover we’re particularly excited because we believe it opens up lightweight apps that can interact and transact with small-and-medium brick-and-mortar restaurants. By lightweight, I mean that these apps won’t need to maintain a user database, require user logins, worry about getting cards on file, or being an unwilling payment aggregator. i.e., it will be at least 10x easier. I expect a huge amount of innovation in real-world mobile commerce as a result over the coming years because of the revolution that Apple Pay is starting…
Generally we tend to dive headlong into Full On Mockery Mode™ soon as we see “revolution” touted in this industry, as perhaps the Dear Longtime Reader may have noticed here and there; but yeah, in this particular case, ok, this just could turn out enough of a thing that “revolution” would only be mild hyperbole. If the details are a bit eye-glazing to you, we’ll tl;dr here from the comments:
This article does explain the advantage Apple Pay has over other eWallet systems. By utilizing Network-Level Tokenization, Apple has integrated with all gateways, processors, issuers, and acquirers in the current payment scheme by negotiating directly with Visa, MasterCard, AMEX, Bank of America, JP Morgan Chase, Wells Fargo, and the list goes on…
This isn’t something that other eWallets have done. Thus, why Apple Pay will be around… and others won’t.
We’re pretty firmly on board with that prognostication.
There’s some more perspectives worth reading collected over at Michael Tsai’s blog.
And here’s a list of Apple-recommended payment platforms:
Authorize.Net : $49 setup, $25 monthly, 2.9% + 30¢ transaction : support, apply
Braintree : 2.9% + 30¢ transaction : support, apply
Chase Paymentech : $9.95 monthly, 1.99% + 25¢ (and up) transaction : support, apply
CyberSource : $CALL! :
First Data (Payeezy) : 2.9% + 30¢ transaction : apply
Stripe : 2.9% + 30¢ transaction : support, apply
TSYS : $5 monthly, 2.7% transaction : apply
“Starting today, any Stripe user can begin accepting Apple Pay in their iOS apps.”: stripe / stripe-ios
Chez Wenderlich’s Apple Pay Tutorial with Stripe
Why Apple Pay is the Most Secure Form of Payment