Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stripe – Apple Pay

stripe.com

Post reply on HN
Print view View original

11–20 of 61 posts

Re: Stripe – Apple Pay

#11

Post by arrrg »

gameguy43 wrote: post #5

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

For in-app purchases Apple collects their 30%, for Apple Pay substantially less. That’s what this comes down to.

In think it more or less comes down to this: If you buy something you (potentially) use inside the app (an ebook, access to some server-side service you can use with the app, …) it’s an in-app purchase. If what you buy is something you use outside the app (a taxi, a pizza, all physical goods, …) you can use Apple Pay.

This differentiation has always existed. Until now Apple just didn’t offer any help with payment with the second category and you had to do it all on your own.

Re: Stripe – Apple Pay

#12

Post by gameguy43 »

zrail wrote: post #9
ErikHuisman wrote: post #7

Earlier quoted context omitted.

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

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

Yeah, this is what I meant by my confusing question above.

Re: Stripe – Apple Pay

#14

Post by Scorponok »

kalleth wrote: 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.

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

Re: Stripe – Apple Pay

#15

Post by marc »

kalleth wrote: 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. (First time you came across Ruby it might have looked quite complicated as well).

Re: Stripe – Apple Pay

#16

Post by druidsbane »

gameguy43 wrote: post #12
zrail wrote: post #9

Earlier quoted context omitted.

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

Yeah, this is what I meant by my confusing question above.

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?

Re: Stripe – Apple Pay

#17

Post by JoshTriplett »

kalleth wrote: 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.

In fairness, the code in that screenshot is horrifically formatted, wrapped, and indented. Properly written and formatted, that code would suck much less.

Re: Stripe – Apple Pay

#18

Post by cornflake »

kalleth wrote: 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.

You can get pretty much native performance out of a cross-platform SDK like: http://www.appcelerator.com/titanium/titanium-sdk

and make the dev environment even more rapid with something like: https://github.com/dbankier/JAST

I don't quite get why you would develop in XCode & Android unless you were trying to squeeze out the last x% in performance or were doing something super custom like Instagram.

Re: Stripe – Apple Pay

#19

Post by pc »

JoshTriplett wrote: post #17
kalleth wrote: 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.

In fairness, the code in that screenshot is horrifically formatted, wrapped, and indented. Properly written and formatted, that code would suck much less.

I think it's his browser width. Here's what it looks like for me: http://cl.ly/image/0I2T2G3F0B3I

Re: Stripe – Apple Pay

#20

Post by malchow »

gameguy43 wrote: post #5

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

How long can Apple maintain this somewhat fictional dichotomy? 30% App Store / 2% Apple Pay. It's a HUGE delta.
Post reply on HN