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

New version of Stripe Checkout

stripe.com

Post reply on HN
Print view View original

151–160 of 162 posts

Re: New version of Stripe Checkout

#151

Post by CodeWriter23 »

kalleboo wrote: post #148
CodeWriter23 wrote: post #142

Earlier quoted context omitted.

Are you speaking about real threats that cannot be mitigated by best practices, or theoretical threats of the future? I guess in other words, I’m under the impression using Stripe and following OWASP and script signing that my customers are safe. If I’m incorrect please pass me a clue.

As a customer, how do I verify that the merchant is following best practices and hasn't by mistake forgotten some ad script enabled on the payment page? With PayPal as long as I only enter my password on paypal dot com I know I'm safe.

If you’re very careful and copy/paste the PayPal URL into an editor and verify you didn’t get sent to PayPal.com.evil.domain, then you’re very likely to be safe.

Re: New version of Stripe Checkout

#152

Post by TazeTSchnitzel »

CodeWriter23 wrote: post #151
kalleboo wrote: post #148

Earlier quoted context omitted.

As a customer, how do I verify that the merchant is following best practices and hasn't by mistake forgotten some ad script enabled on the payment page? With PayPal as long as I only enter my password on paypal dot com I know I'm safe.

If you’re very careful and copy/paste the PayPal URL into an editor and verify you didn’t get sent to PayPal.com.evil.domain, then you’re very likely to be safe.

I don't need to do that, browsers carefully show the actual domain in ways to avoid that problem since a few years now.

Re: New version of Stripe Checkout

#153

Post by forgot-my-pw »

foobarbazetc wrote: post #46
quotha wrote: post #27

Earlier quoted context omitted.

I think it's just a matter of time before people switch from using PayPal.

We thought this and killed our PayPal integration (went Stripe only) and lost double digits in sales (and received constant emails asking for PayPal). Unfortunately people want PayPal for whatever reason. Everything about PayPal from the merchant side sucks (bad API, bad recurring billing features, slow, no refund of fees for refunds from May, 6 months for someone to do a chargeback!, etc etc)

Maybe integrate with Braintree instead?

Re: New version of Stripe Checkout

#154

Post by somada141 »

I've been looking a fair bit into these embedded checkout things recently and I gotta say that braintree is far-far inferior to Stripe in terms of offerings, usability, API, etc.

There's things one would consider no-brainers for this type of service like discount codes with an expiry date and maximum number of uses that Braintree doesn't offer but their saving grace is PayPal support that, for better or for worse, is a must for most businesses.

The end result is that a dev needs to create a custom checkout UI integrating both services and having their customers split among the two ecosystems which is just gross :).

Re: New version of Stripe Checkout

#155

Post by meowface »

Gaelan wrote: post #132
meowface wrote: post #92

Earlier quoted context omitted.

From an end user perspective, Paypal is a service which magically sends money over the Internet, and you're near-permanently logged into it, so you can pay for anything with almost no friction after you use it for the first time. A Stripe dialog is just a form/modal you see on a website asking you for your credit card details. They're similar services when you break them down, but Paypal is almost more like a social…

IIRC stripe checkout remembers login info.

In that case I might be wrong. I've only ever used Stripe as an end user, and each time I used it it just appeared to be a credit card form, with no accounts and no memory of previous credit cards I've entered (which is what I would want anyway).

Re: New version of Stripe Checkout

#156

Post by gideonatstripe »

GordonS wrote: post #38
jenanwise wrote: post #30

Earlier quoted context omitted.

We found that legacy version of Checkout did not allow us to build a number of features that users have been asking about for years—including instantly turning on Apple Pay without needing you to register with Apple directly, supporting a unified API that can work with redirect-based payment methods such as iDEAL (coming soon), and a bunch more features that we're working on. If you're looking for something embedded…

Plenty Stripe users don't care a jot about Apple Pay, especially those in the B2B space - I consider it a real loss to have customers be redirected vs just showing a modal. As another commenter mentioned, it also means another step for the end user. I understand the desire for a converged Checkout API and UI, but I still kind of wish there were 2 options - modal or redirect.

Hey GordonS,

Gideon from Stripe Product Ops here. I definitely hear you RE: wanting to keep an modal version. If it's not too much trouble, could you email me at gideon+hn@stripe.com so I can get some more feedback from you?

Re: New version of Stripe Checkout

#157

Post by [deleted] »

ycombinateur wrote: post #49
GordonS wrote: post #38

Earlier quoted context omitted.

Plenty Stripe users don't care a jot about Apple Pay, especially those in the B2B space - I consider it a real loss to have customers be redirected vs just showing a modal. As another commenter mentioned, it also means another step for the end user. I understand the desire for a converged Checkout API and UI, but I still kind of wish there were 2 options - modal or redirect.

I so unbelievably strongly agree. There should also be a pop-up version of checkout instead of a redirect. The only two features I care about are (i) a simple popup to accept cc details (ii) an aesthetically pleasing interface

[deleted]

Re: New version of Stripe Checkout

#158

Post by gideonatstripe »

electroly wrote: post #60
jenanwise wrote: post #52

Earlier quoted context omitted.

Future development will be focused on Elements and the new version of Checkout, but we’ll continue to maintain the legacy version as long as we can. Note that if you’re accepting payments from PSD2/SCA-impacted countries, we do recommend using Elements or Checkout, as the legacy version of Checkout doesn’t support 3DS. Would love to hear more about why Elements or the new version of Checkout don’t work for your use c…

For us it's all about implementation simplicity. For a small peanuts site that's a little too complicated for Shopify but not nearly profitable enough to support paying for a lot of custom development, "legacy" Checkout slotted in perfectly. Not having a redirect-based workflow means we don't have to break apart our own checkout process; I can just have one simple HTML form with some magic JavaScript and then by the…

Hey electroly,

Gideon from Stripe Product Ops here. Can you tell me more about your integration if it's not too much trouble? You can email me at gideon+hn@stripe.com any time

Re: New version of Stripe Checkout

#159

Post by [deleted] »

dfabulich wrote: post #63
electroly wrote: post #60

Earlier quoted context omitted.

For us it's all about implementation simplicity. For a small peanuts site that's a little too complicated for Shopify but not nearly profitable enough to support paying for a lot of custom development, "legacy" Checkout slotted in perfectly. Not having a redirect-based workflow means we don't have to break apart our own checkout process; I can just have one simple HTML form with some magic JavaScript and then by the…

I agree 100%. For now, I'll just keep using legacy Checkout, but some day legacy Checkout will stop working. When that day comes, the effort to port to the new Checkout will be approximately the same as the effort to port to PayPal. If there's no pop-up mode by then, I'll probably just switch to PayPal.

[deleted]

Re: New version of Stripe Checkout

#160

Post by gideonatstripe »

rurp wrote: post #131
electroly wrote: post #111

Earlier quoted context omitted.

Just a followup now that I've seen some more details elsewhere that has strengthened my resolve: if you expect me to implement a webhook or to poll for completed transactions, you've lost me, and I think you've lost the knowledge of why people chose Stripe Checkout for their websites in the first place. As soon as legacy Checkout stops working, I'm gone. If I'm implementing webhooks, then I'm implementing it for PayP…

I can't second this enough. Stripe making their software categorically worse for a number of longtime users is infuriating. It's one thing when a toy app does this, but for something as critical as handling payments, "Well we want to add some features you don't care about" doesn't cut it.

Hi @rurp,

Gideon on the Stripe Product Ops team. I'd love to hear which features aren't important to your business and which features would be. If it's not too much trouble, could you email me at gideon+hn@stripe.com so I can get some more feedback from you?

Post reply on HN