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

Stripe and Apple Pay

stripe.com

Post reply on HN
Print view View original

21–30 of 100 posts

Re: Stripe and Apple Pay

#21

Post by zwily »

yahelc wrote: post #17
MBCook wrote: post #16

Earlier quoted context omitted.

I doubt it. For one thing they'd lose the ability to ensure you're who you say you are with TouchID, etc.

Presumably, if they wanted to do a web version, they could introduce Safari-only JavaScript APIs for verifying TouchID.

They could use Continuity-type stuff to have you verify the payment from your phone, that's happening in your desktop browser.

Re: Stripe and Apple Pay

#22

Post by jessriedel »

nextstep wrote: post #4

I'm not sure I understand Stripe's value proposition here. What is the benefit of using Stripe's library over using ApplePay (PassKit) directly? (Honest question)

Here's how I think about it: Apple is the user's broker and Stripe is the merchant's broker. Every time there's a transaction between the user and the merchant, they are setting up a deal between their respective brokers.

As fgblanch points out, a merchant using Stripe only needs a single account with them to handle credit cards, Apple Pay, and whatever else comes along tomorrow.

As Igglybook and zaidf point out, Apple wants to provide the hardware and software for the user, but they don't actually want to be a financial services company like Stripe.

Re: Stripe and Apple Pay

#23

Post by jasonbarone »

MBCook wrote: post #16
nlh wrote: post #9

I presume from what I've read/seen, ApplePay will be app-only (i.e. iOS) for launch. But I've got to imagine they (as in, Apple and Stripe) will integrate with web-based payment forms as step 2. Or, should I say, "I hope"...

I doubt it. For one thing they'd lose the ability to ensure you're who you say you are with TouchID, etc.

That's what I thought, but Apple Watch supports Apple Pay and that doesn't support Touch ID.

Re: Stripe and Apple Pay

#24

Post by thesimon »

jefftchan wrote: post #15

Can we now use Stripe + Apple Pay to circumvent 30% revenue cut?

Apple only takes 30% for digital goods, I doubt they'll remove that limitation.

For non-digital goods, Stripe is offering a library for iOS for a few years now which isn't affected by the 30% cut.

Re: Stripe and Apple Pay

#25

Post by pc »

jefftchan wrote: post #15

Can we now use Stripe + Apple Pay to circumvent 30% revenue cut?

Your Stripe pricing is the same if you use Apple Pay -- there are no additional fees. (And no 30%.)

(We should update the page to say this...)

Re: Stripe and Apple Pay

#27

Post by ajju »

pc wrote: post #25
jefftchan wrote: post #15

Can we now use Stripe + Apple Pay to circumvent 30% revenue cut?

Your Stripe pricing is the same if you use Apple Pay -- there are no additional fees. (And no 30%.) (We should update the page to say this...)

It looks like Applepay generates one-time cards by default resulting in a single-use Stripe token. Does that mean the use case this supports is only one-time payments versus "sign up with Apple pay+Stripe"? Any advice on how best to integrate Apple pay for recurring pay scenarios like Sumon?

Edit: Some more context on how this all works from the other ApplePay thread on HN: http://clover-developers.blogspot.com/2014/09/apple-pay.html

Re: Stripe and Apple Pay

#29

Post by Letio »

Patrick,

Curious, was the majority of the work required to support ApplePay related to the format of the PKPayment? I assume in other cases, you just pass the raw PAN + pin, etc, where as now you need to pass the encrypted single use token + cryptographic data + more. Was more work required to support ApplePay?

And if so, did Visa/MC/Amex and the processing networks recently start supporting this payload, or has it been in place for some time?

Finally, what does Apple use the Merchant ID for?

Post reply on HN