This page has 0 threads | Add post

Blogs

Finding our blogs useful? Please consider helping us to share more!

Our experience of switching to Stripe payments Part five of a five-part series of blogs
This is the blog which I wish I could have read before starting to integrate Stripe payments on our website! It explains why I'm ultimately glad we went for Stripe, but also some of the things which are harder than they need to be. Our experience of switching to Stripe payments Background and reason for change Enabling payments using Stripe Customising payments forms Conclusion - would I choose Stripe again? (this blog)

Our experience of switching to Stripe payments

Part five of a five-part series of blogs

This is the blog which I wish I could have read before starting to integrate Stripe payments on our website! It explains why I'm ultimately glad we went for Stripe, but also some of the things which are harder than they need to be.

Our experience of switching to Stripe payments
Background and reason for change
Enabling payments using Stripe
Customising payments forms
Conclusion - would I choose Stripe again? (this blog)

Posted by Andy Brown on 01 June 2021

Conclusion - would I choose Stripe again?

The short answer is yes, but they could make things so much easier! Here are my top requests of the Stripe web developers:

Request	Details
Document elements better	There is online documentation for how elements work, but it's nowhere near as good as for payment integration, and there's no full list that I could see online of all of the element and style properties that you can set (and what they mean). More importantly, there's no summary of how mounted elements work (including nuggets of information such as that you can't use borders in Stripe styles, and can't embed generated IFrames in table cells).
Make mixing elements easier	It's possible to mix standard form elements (address, postcode, etc) with Stripe elements (card number, CVC number, etc), but getting them to look the same is not as easy as it should be.

Request

Details

Document elements better

There is online documentation for how elements work, but it's nowhere near as good as for payment integration, and there's no full list that I could see online of all of the element and style properties that you can set (and what they mean). More importantly, there's no summary of how mounted elements work (including nuggets of information such as that you can't use borders in Stripe styles, and can't embed generated IFrames in table cells).

Make mixing elements easier

It's possible to mix standard form elements (address, postcode, etc) with Stripe elements (card number, CVC number, etc), but getting them to look the same is not as easy as it should be.

Having said all of this, having a single page order-and-payment form is wonderful, and I know that future development will be so much quicker and more powerful than it would have been had we stayed with WorldPay. So it's four out of five stars to Stripe!

Parts of this blog
Our experience of switching to Stripe payments Background and reason for change Enabling payments using Stripe Customising payments forms Conclusion - would I choose Stripe again? (this blog)