41–50 of 162 posts
Earlier quoted context omitted.
The Apple Pay button will only show up to customers who have Apple Pay onboarded and enabled. Customers who don't care about Apple Pay won't ever see the button. (I work on Checkout)
In the future will the "Apple Pay" in this instance also be replaced by PayPal, Google Pay, etc, depending on what the person uses?
Wasn't the advantage of the original checkout the customer didn't have to leave your site?
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…
Does this mean that it will be possible to implement Stripe payments that work without JavaScript?
Earlier quoted context omitted.
The Apple Pay button will only show up to customers who have Apple Pay onboarded and enabled. Customers who don't care about Apple Pay won't ever see the button. (I work on Checkout)
In the future will the "Apple Pay" in this instance also be replaced by PayPal, Google Pay, etc, depending on what the person uses?
Interested to see what the PSD2/SCA implementation looks like. Stripe will go out of their way to avoid adding friction, but the requirements are not trivial.
Wasn't the advantage of the original checkout the customer didn't have to leave your site?
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…
This is a beautiful user interface, but in my business, ~40% of our payments are through PayPal. To integrate Stripe Checkout, we would have to ask the customer whether they're paying with a card or using PayPal prior to displaying the Stripe UI. While that is not the worst option, our current UX is similar to Shopify, where there is an accordion component with multiple options: PayPal, Credit Card, Apple Pay, etc..…
I think it's just a matter of time before people switch from using 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)
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…
> supporting a unified API that can work with redirect-based payment methods Does this mean that it will be possible to implement Stripe payments that work without JavaScript?
Essentially:
window.Stripe('').redirectToCheckout({sessionId});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.
The only two features I care about are (i) a simple popup to accept cc details (ii) an aesthetically pleasing interface
Disclaimer: Slightly off-topic rant about why I as a consumer will always avoid Stripe: Will they now not lie about wire transfer being US-Only and accept the debit card they say they accept? My one interaction with Stripe was absolutely horrible, lost my vendor which is otherwise great a (subscription) sale and will take a lot of effort to right. Edit: Right, it wasn't just errors, but it just didn't work with any m…