Earlier quoted context omitted.
If you're trying to be like Vercel—it's a red flag for any reasonable person when you clearly spent more effort on your landing page than your actual product. What made Stripe so successful is that, I personally would not even attempt, like you said, "integrations with providers" "bank partnerships" "compliance screens" because that sounds basically impossible.
"It's hard so you shouldn't try doing it" thank you, very productive reply
Show HN: We built an open source, zero webhooks payment processor
31–40 of 230 posts
Re: Show HN: We built an open source, zero webhooks payment processor
#32Earlier quoted context omitted.
Who cares about developer experience? Genuinely asking, because I’m a developer too and I certainly don’t care. What we care about is solving the actual problem of payments with the downstream companies.
“Well your payments platform doesn’t actually do payments, but the developer experience of doing nothing was flawless!” Sorry for the snark, but been in payments a long time, and seen too much of this nonsense.
Re: Show HN: We built an open source, zero webhooks payment processor
#33For those who are wondering, like me, what is this? Is this a new alternative to Stripe? The answer is: no. This is an added layer of abstraction on top of Stripe.
Re: Show HN: We built an open source, zero webhooks payment processor
#34> Not to mention choreographing the lifecycle of our business domain with the Stripe checkout flow and webhook event types, of which there are 250+ You don’t need to listen for all event types if you aren’t using _every_ Stripe feature.
Re: Show HN: We built an open source, zero webhooks payment processor
#35For those who are wondering, like me, what is this? Is this a new alternative to Stripe? The answer is: no. This is an added layer of abstraction on top of Stripe.
For now, yes. The game plan over time is to get deeper into the actual card rails side of things. But first we really want to nail the developer experience.
You are going to run into things like TSYS closing out batches every three days regardless of what happens.
The handling features for them and their customers thing is going to be a herculean task over even a couple different platforms. Not impossible, but it's big and you would do well to see what's out there before committing to a standard interface. Take a look at https://datacapsystems.com/ to see it done well.
Also, adding another layer like this, you better have an early plan to staff a support desk.
Oh, also, you are gateway, not a processor.
Re: Show HN: We built an open source, zero webhooks payment processor
#36Earlier quoted context omitted.
For now, yes. The game plan over time is to get deeper into the actual card rails side of things. But first we really want to nail the developer experience.
Who cares about developer experience? Genuinely asking, because I’m a developer too and I certainly don’t care. What we care about is solving the actual problem of payments with the downstream companies.
fewers bugs = happier customers not getting charged for shit they didn't agree to be charged for
Re: Show HN: We built an open source, zero webhooks payment processor
#37> Not to mention choreographing the lifecycle of our business domain with the Stripe checkout flow and webhook event types, of which there are 250+ You don’t need to listen for all event types if you aren’t using _every_ Stripe feature.
Sure, but everything from the Stripe UI down to their API is feature creeped. I remember using it 10 years ago and I got it working in 10-20 minutes. Last month I see it up for my new project and it took almost a whole day
Re: Show HN: We built an open source, zero webhooks payment processor
#38Re: Show HN: We built an open source, zero webhooks payment processor
#39For those who are wondering, like me, what is this? Is this a new alternative to Stripe? The answer is: no. This is an added layer of abstraction on top of Stripe.
For now, yes. The game plan over time is to get deeper into the actual card rails side of things. But first we really want to nail the developer experience.