7 ms·

Stripe – Apple Pay

183 points by Killswitch 12y ago

jonhmchan 12y ago
I'm very impressed with how quickly Stripe has been able to get Apply Pay integration as part of their platform. I'll be looking into it for my own apps.
- lyinsteve 12y ago
  They were a launch partner when Apple announced Apple Pay. They most likely had advanced knowledge and have been working on integration for a long time.
zrail 12y ago
I know this is a long shot, but will it ever be possible to use Apple Pay with Checkout from a webpage?
- ErikHuisman 12y ago
  Generate a visual code on checkout screen >> Scan with app + camera >> Apple pay. Or use "continuity" on Yosemite if it is Mac > iOS
  - zrail 12y ago
    Sure, that would be one way to hack around it. I'm wondering, specifically, if Stripe Checkout[1] will ever gain Apple Pay support. Presumably it's up to Apple to expose the relevant API to javascript. [1]: https://stripe.com/checkout https://stripe.com/checkout
    - gameguy43 12y ago
      Yeah, this is what I meant by my confusing question above.
      - druidsbane 12y ago
        One day they'll probably let you enter your user id and password to get it started then scan your fingerprint on a device to confirm. Why not?
        skinnybatch 12y ago
        my only issue with this has to do with the occasional lapse in recognition of the touch ID. if it can't read your fingerprint several times, it asks for your password code. touch ID is of course not theft-proof, but initially it's a slightly greater obstacle than a simple numeric code.
  - downandout 12y ago
    It would be beyond easy to make a generic app that registers a custom protocol handler on the phone that could handle this. Don't know if Apple would approve it but sending the user to, for example, myapplepayapp://transactions?Id=123 where the id could be used to grab all the order data from the shopping cart, identify the merchant, and grab their Stripe API credentials would be simple and useful.
gameguy43 12y ago
"Apple Pay doesn’t replace In-App Purchases. You should use Apple Pay when charging for physical goods (such as groceries, clothing, and appliances) or for services (such as club memberships, hotel reservations, and tickets for events). You should continue to use In-App Purchases to charge for virtual goods such as premium content in your app." Anyone understand why this is? Is there a reason I shouldn't let my users use Apple Pay to buy the freemium digital content on my website? I don't quite understand what capitalized In-App Purchases means...oh, maybe Apple Pay is only possible from an app, not from a mobile web browser? Is that true? (But like, why?)
- eddieroger 12y ago
  Apple's guidelines. In-App purchases can't be used for physical goods, but must be used for anything that does stuff through the app.
  - cjantz 12y ago
    I think Apple needs to check on this very careful just because of some services like Uber offer services through the app and don't sell a physical good. The opposite of this is, that you can't use Apples tier-pricing for services like that just because of it's usage-dependant and is reflected through actions in the real world. I wonder how much effort Apple is going to put into checking on this actually. Especially because of services like Uber sell the ride. But what if the direct contract partner would be the driver and any service provider like that would just process transactions for comfort - so acting like a payment gateway for drivers.
    - lemue 12y ago
      A valid point, but I guess Apple will change the terms of service or will define services like Uber as physical good, since the service affects the real world and can not be realised through in-app purchases. I think that is what it is all about. They do not want Devs to opt out of in-app purchases and adopt ApplePay instead.
    - eddieroger 12y ago
SmithHummel 12y ago
Applepay, it's so simple, so swift, so sleek... yawn. Anyone taking wagers for how long until Apple requires all physical goods/services sold via iOS apps to use ApplePay (just like they currently require all digital goods/subscriptions to use In-app purchases)? I'd place a bet on two years til Apple requires a cut. Stripe is quite complimentary to ApplePaynow. I wonder how long they will also be complementary...
kalleth 12y ago
"It just takes a few lines of code to set up and display the Apple Pay UI" https://pbs.twimg.com/media/B0aIWgoIgAE2oNE.png:large https://pbs.twimg.com/media/B0aIWgoIgAE2oNE.png:large Do people actually work in these languages and not go postal? Maybe I'm spoilt as a ruby developer tbh.
- Scorponok 12y ago
  It's a lot of code to write, but extremely understandable when you come back to read it a year later and wonder "what the heck do the parameters to this function do?"
- keesj 12y ago
  I've only just started learning iOS development (Swift, not Objective-C) and although initially the code looks quite complicated, Xcode more than makes up for it. Its auto-complete functionality makes it very fast to write these rather lengthy lines of code. Plus it's a really descriptive way of writing code. Also, like with many languages, once you understand the basic syntax it doesn't look as complicated anymore. (First time you came across Ruby it might have looked quite complicated as well).
  - prawn 12y ago
    Yes, if you watch an experienced developer in Xcode, you will see that the autocomplete makes writing out these sorts of things very, very fast.
- JoshTriplett 12y ago
  In fairness, the code in that screenshot is horrifically formatted, wrapped, and indented. Properly written and formatted, that code would suck much less.
  - pc 12y ago
    I think it's his browser width. Here's what it looks like for me: http://cl.ly/image/0I2T2G3F0B3I http://cl.ly/image/0I2T2G3F0B3I
callmeed 12y ago
So, what is the fallback for users on non-apple-pay devices? Just normal "enter/save your billing information"?
- matthewarkin 12y ago
  If you use Stripe-iOS it should auto fall back to a card number entry box.
adamfeldman 12y ago
I'm so disappointed that the 5s doesn't support Apple Pay for in-app purchases of physical goods (the payments product Stripe partners with Apple to provide). I've yet to discover any reason why except marketing/branding – ostensibly consumers would be confused that they can use their 5s for purchases through apps but not in retail stores, due to the lack of NFC. From a technical perspective, there doesn't seem to be anything holding the 5s back. The A7 has a secure element/"enclave" like the A8 (a cryptographically secure place on the SoC to store payment tokens, fingerprints, and the like), and the 5s has an A7 and the TouchID sensor. EDIT: The secure element is in fact distinct from the secure enclave. agnokapathetic explains below.
- mitman 12y ago
  I was under the impression that Secure Element is separate from Secure Enclave. Secure Element is for CC information and Secure Enclave for fingerprint data. Since the 5s lacks Secure Element, it makes sense why even Apple Pay in apps wouldn't work. I have not been able to find anything to suggest one way or the other, so I could be wrong. Please correct me if I said something wrong.
- agnokapathetic 12y ago
  The technical reason is that while the iPhone 5s has the Secure Enclave co-Processor (SEP), it does not have an Apple Pay Secure Element (SE). The SEP is a ARM TrustZone-like separate processor running a stripped down L4 derived microkernel. This manages encryption keys, the secure boot-loader and OS update signing. The Apple Pay Secure Element is a separate chip which runs a Java-Card-OS. "Cards" in the java-card-OS are cryptographically "personalized" by the payment network (VISA, AMEX, MasterCard) with per-device keys and the device personal account number (DPAN)--the tokenized device only credit card. This is the same java-card + payment network personalization that physical chip-and-pin cards, Google Wallet and most other NFC payments use. So my guess is that the Payment Networks were not comfortable using the Secure Enclave Processor and preferred to reuse the same technology used by chip-and-pin, with a separate Secure Element chip. Source: https://www.apple.com/privacy/docs/iOS_Security_Guide_Oct_2014.pdf https://www.apple.com/privacy/docs/iOS_Security_Guide_Oct_20...
xsb 12y ago
What happened to Stripe Bitcoin payments? https://stripe.com/bitcoin https://stripe.com/bitcoin
- StavrosK 12y ago
  They just enrolled me in the demo two or three days ago. It's pretty slick (well, very slick), it's just that their libraries don't yet support it (I think the API is going to change). It was very easy to add to Checkout, though.
- matthewarkin 12y ago
  Yea they just totally revamped the beta, its pretty awesome. Bitcoin went from being a completely separate API to integrated with the standard charge APIs. It also got integrated into Stripe checkout.

183 points by Killswitch 12y ago

I'm very impressed with how quickly Stripe has been able to get Apply Pay integration as part of their platform. I'll be looking into it for my own apps.

lyinsteve 12y ago
They were a launch partner when Apple announced Apple Pay. They most likely had advanced knowledge and have been working on integration for a long time.

zrail 12y ago

I know this is a long shot, but will it ever be possible to use Apple Pay with Checkout from a webpage?

ErikHuisman 12y ago
Generate a visual code on checkout screen >> Scan with app + camera >> Apple pay. Or use "continuity" on Yosemite if it is Mac > iOS
- zrail 12y ago
  Sure, that would be one way to hack around it. I'm wondering, specifically, if Stripe Checkout[1] will ever gain Apple Pay support. Presumably it's up to Apple to expose the relevant API to javascript. [1]: https://stripe.com/checkout https://stripe.com/checkout
  - gameguy43 12y ago
    Yeah, this is what I meant by my confusing question above.
    - druidsbane 12y ago
      One day they'll probably let you enter your user id and password to get it started then scan your fingerprint on a device to confirm. Why not?
      - skinnybatch 12y ago
        my only issue with this has to do with the occasional lapse in recognition of the touch ID. if it can't read your fingerprint several times, it asks for your password code. touch ID is of course not theft-proof, but initially it's a slightly greater obstacle than a simple numeric code.
- downandout 12y ago
  It would be beyond easy to make a generic app that registers a custom protocol handler on the phone that could handle this. Don't know if Apple would approve it but sending the user to, for example, myapplepayapp://transactions?Id=123 where the id could be used to grab all the order data from the shopping cart, identify the merchant, and grab their Stripe API credentials would be simple and useful.

gameguy43 12y ago

"Apple Pay doesn’t replace In-App Purchases. You should use Apple Pay when charging for physical goods (such as groceries, clothing, and appliances) or for services (such as club memberships, hotel reservations, and tickets for events). You should continue to use In-App Purchases to charge for virtual goods such as premium content in your app." Anyone understand why this is? Is there a reason I shouldn't let my users use Apple Pay to buy the freemium digital content on my website? I don't quite understand what capitalized In-App Purchases means...oh, maybe Apple Pay is only possible from an app, not from a mobile web browser? Is that true? (But like, why?)

eddieroger 12y ago
Apple's guidelines. In-App purchases can't be used for physical goods, but must be used for anything that does stuff through the app.
- cjantz 12y ago
  I think Apple needs to check on this very careful just because of some services like Uber offer services through the app and don't sell a physical good. The opposite of this is, that you can't use Apples tier-pricing for services like that just because of it's usage-dependant and is reflected through actions in the real world. I wonder how much effort Apple is going to put into checking on this actually. Especially because of services like Uber sell the ride. But what if the direct contract partner would be the driver and any service provider like that would just process transactions for comfort - so acting like a payment gateway for drivers.
  - lemue 12y ago
    A valid point, but I guess Apple will change the terms of service or will define services like Uber as physical good, since the service affects the real world and can not be realised through in-app purchases. I think that is what it is all about. They do not want Devs to opt out of in-app purchases and adopt ApplePay instead.
  - eddieroger 12y ago

SmithHummel 12y ago

Applepay, it's so simple, so swift, so sleek... yawn. Anyone taking wagers for how long until Apple requires all physical goods/services sold via iOS apps to use ApplePay (just like they currently require all digital goods/subscriptions to use In-app purchases)? I'd place a bet on two years til Apple requires a cut. Stripe is quite complimentary to ApplePaynow. I wonder how long they will also be complementary...

kalleth 12y ago

"It just takes a few lines of code to set up and display the Apple Pay UI" https://pbs.twimg.com/media/B0aIWgoIgAE2oNE.png:large https://pbs.twimg.com/media/B0aIWgoIgAE2oNE.png:large Do people actually work in these languages and not go postal? Maybe I'm spoilt as a ruby developer tbh.

Scorponok 12y ago
It's a lot of code to write, but extremely understandable when you come back to read it a year later and wonder "what the heck do the parameters to this function do?"
keesj 12y ago
I've only just started learning iOS development (Swift, not Objective-C) and although initially the code looks quite complicated, Xcode more than makes up for it. Its auto-complete functionality makes it very fast to write these rather lengthy lines of code. Plus it's a really descriptive way of writing code. Also, like with many languages, once you understand the basic syntax it doesn't look as complicated anymore. (First time you came across Ruby it might have looked quite complicated as well).
- prawn 12y ago
  Yes, if you watch an experienced developer in Xcode, you will see that the autocomplete makes writing out these sorts of things very, very fast.
JoshTriplett 12y ago
In fairness, the code in that screenshot is horrifically formatted, wrapped, and indented. Properly written and formatted, that code would suck much less.
- pc 12y ago
  I think it's his browser width. Here's what it looks like for me: http://cl.ly/image/0I2T2G3F0B3I http://cl.ly/image/0I2T2G3F0B3I

callmeed 12y ago

So, what is the fallback for users on non-apple-pay devices? Just normal "enter/save your billing information"?

matthewarkin 12y ago
If you use Stripe-iOS it should auto fall back to a card number entry box.

adamfeldman 12y ago

I'm so disappointed that the 5s doesn't support Apple Pay for in-app purchases of physical goods (the payments product Stripe partners with Apple to provide). I've yet to discover any reason why except marketing/branding – ostensibly consumers would be confused that they can use their 5s for purchases through apps but not in retail stores, due to the lack of NFC. From a technical perspective, there doesn't seem to be anything holding the 5s back. The A7 has a secure element/"enclave" like the A8 (a cryptographically secure place on the SoC to store payment tokens, fingerprints, and the like), and the 5s has an A7 and the TouchID sensor. EDIT: The secure element is in fact distinct from the secure enclave. agnokapathetic explains below.

mitman 12y ago
I was under the impression that Secure Element is separate from Secure Enclave. Secure Element is for CC information and Secure Enclave for fingerprint data. Since the 5s lacks Secure Element, it makes sense why even Apple Pay in apps wouldn't work. I have not been able to find anything to suggest one way or the other, so I could be wrong. Please correct me if I said something wrong.
agnokapathetic 12y ago
The technical reason is that while the iPhone 5s has the Secure Enclave co-Processor (SEP), it does not have an Apple Pay Secure Element (SE). The SEP is a ARM TrustZone-like separate processor running a stripped down L4 derived microkernel. This manages encryption keys, the secure boot-loader and OS update signing. The Apple Pay Secure Element is a separate chip which runs a Java-Card-OS. "Cards" in the java-card-OS are cryptographically "personalized" by the payment network (VISA, AMEX, MasterCard) with per-device keys and the device personal account number (DPAN)--the tokenized device only credit card. This is the same java-card + payment network personalization that physical chip-and-pin cards, Google Wallet and most other NFC payments use. So my guess is that the Payment Networks were not comfortable using the Secure Enclave Processor and preferred to reuse the same technology used by chip-and-pin, with a separate Secure Element chip. Source: https://www.apple.com/privacy/docs/iOS_Security_Guide_Oct_2014.pdf https://www.apple.com/privacy/docs/iOS_Security_Guide_Oct_20...

xsb 12y ago

What happened to Stripe Bitcoin payments? https://stripe.com/bitcoin https://stripe.com/bitcoin

StavrosK 12y ago
They just enrolled me in the demo two or three days ago. It's pretty slick (well, very slick), it's just that their libraries don't yet support it (I think the API is going to change). It was very easy to add to Checkout, though.
matthewarkin 12y ago
Yea they just totally revamped the beta, its pretty awesome. Bitcoin went from being a completely separate API to integrated with the standard charge APIs. It also got integrated into Stripe checkout.