Hi all,
For me, it's the whole process of taking the time to read the documentation, picking a client library for your language, testing the integration, managing keys for different environments, and deploying to production. I just want to get back to my core app, and not spend time doing integrations for operations.
Stripe now supports all sorts of payment workflows besides the simple one-time credit card payment, such as subscriptions, metered billing, and transactions in a 3-sided marketplace (like DoorDash), which can get complicated.
I'm making a low-code payment workflow builder. It helps you integrate with Stripe to gather payment from customers.
The builder let you drag 'n drop processing steps together to build a payment workflow of any complexity supported by Stripe. If you need to customize, you can drop down to the low level code.
Once you're satisfied with the flow, you can deploy it to serverlessly with a click of a button. This separates business operations like payment workflows separate from your app. It shouldn't require a git commit to change payment confirmation emails and pricing structures.
I have a bare prototype working, but before going too much further, I wanted to start talking to people to see that I'm on the right track. What are your frustrations and experiences with integrating payment workflows? Is this something that is a problem that you'd like taken care of for your next project(s)?
I plan on posting updates and notifying people about the beta at the bottom of this page: https://paymentworkflowbeta.substack.com/p/coming-soon
No this is really a good idea actually. Really interested
Thanks! If interested click into the substack link and subscribe to get notified.
What sort of issues do you run into integrating payments?
Hey good idea :) you can take a look at Primer. I think this is the same thing you want to create https://primer.io
Thanks for the link! I didn’t know it existed. I’ll check them out more.