BLOGS BY TOPIC▼
BLOGS BY AUTHOR▼
BLOGS BY YEAR▼
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.
Posted by Andy Brown on 01 June 2021
You need a minimum screen resolution of about 700 pixels width to see our blogs. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.
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:
|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!