Live data from Hacker News

Stripe – Apple Pay

stripe.com

41–50 of 61 posts

Re: Stripe – Apple Pay

#41
post #33

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…

The apple watch will allow for contactless payments via apple pay for people with the iphone 5/5s

And it owuld appear that in addition to contactless payments owning an Apple Watch will allow for in-app Apple Pay(ments) too

Re: Stripe – Apple Pay

#42
post #35

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

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.

Re: Stripe – Apple Pay

#43

Earlier quoted context omitted.

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…

'"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.' Is this 'tokenized device only credit card' the same concept as the Point-of-Sale seeing a unique CC # (generated) for the transaction? (What I believe is one of the selling points for Apple Pay). A…

According to the email I got from American Express, the POS will see the DPAN. So every POS transaction would see the same unique card number.

Re: Stripe – Apple Pay

#44
post #35

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

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.

Re: Stripe – Apple Pay

#46

"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…

Everyone here talks about Apple's "30% cut" (which of course is nowhere near what Apple actually gets, as people don't take into account costs for the high transaction costs on these small purchases), but as someone who runs an App Store (and who has had to on numerous occasions here on Hacker News dispel the weirdly-pervasive myth that Apple makes meaningful money from their App Store, something trivially disprovable using Apple's earning statements), I will assert the difference is more to do with license transfer and fraud mitigation, two things users and developers alike often fail to realize are either hard or even necessary until after it is too late.

In-App purchases are tied to your Apple ID and can be recovered and reactivated by a receipt API on other devices you are logged in to: Apple wants you to use their API for this purpose to guarantee that buying new devices will not lead to the user having lost a ton of money in their software investments. Some developers in the Cydia ecosystem sell things themselves, and they have either draconian or broken device license transfer restrictions. Users still complain to me, even though I had nothing to do with their payment. For Apple, the issue is even worse, as it could keep a user from buying a new device (where Apple actually makes money: anything that stands in the way of this Apple will not tolerate).

Physical goods are also very easy to build fraud contros for, due to the requirement of a physical shipping address; the same is not true of digital goods: Apple has spent a long time building out fraud management for their digital goods sales, and I doubt they want the Apple Pay platform to suddenly be inundated with tons of "app developers" (a class of developer Apple clearly doesn't trust very much) to make people start to think Apple's app ecosystem is a massive source of credit fraud. Apple also likes separating user data from developers: you don't know your customers, only Apple does; for a physical good, that is obviously an impossible separation to maintain, but for digital goods I think they would rather continue to have all purchases gated through them so that all developers see are anonymized identifiers.

Re: Stripe – Apple Pay

#47
post #40
post #33

Earlier quoted context omitted.

The apple watch will allow for contactless payments via apple pay for people with the iphone 5/5s

I've only heard about 5s supporting Apple Pay with Apple Watch.

I suspect that is because touchID is required so no plain iPhone 5 support.

Re: Stripe – Apple Pay

#48
post #15
post #13

"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 Do people actually work in these languages and not go postal? Maybe I'm spoilt as a ruby developer tbh.

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.…

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.

Re: Stripe – Apple Pay

#49

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…

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…

Just to add to this, there is a body that covers "secure chip" technology: GlobalPlatform[1].

[1] http://www.globalplatform.org

Re: Stripe – Apple Pay

#50
post #3

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

Generate a visual code on checkout screen >> Scan with app + camera >> Apple pay. Or use "continuity" on Yosemite if it is Mac > iOS

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.
Post reply on HN