Live data from Hacker News

Show HN: We built an open source, zero webhooks payment processor

github.com

181–190 of 230 posts

Re: Show HN: We built an open source, zero webhooks payment processor

#181
post #174

Quick feedback from a Stripe and Braintree customer, who wrote their own subscription system so as not to use Stripe Billing. The things that caused me problems in the past: * inflexible subscription system * unreliable web component for gathering credit card information * unreliable 3DSecure implementation * incompetent support (these four are the main reasons why I switched from Braintree to Stripe) * complex and u…

Could you elaborate on inflexible subscription system and also what you would like to see from a 3DSecure implementation?

Full disclosure: I'm a dev at a fintech startup and we're currently working on these two things so I'm curious how our direction lines up with your thoughts

Re: Show HN: We built an open source, zero webhooks payment processor

#182
You can make it even easier

And serverless

Just have the client redirect to your checkout flow, and it redirects back with a signed payload. Like oauth. Done.

Make an HTTP interface that’s easy to curl, as well as a Javascript library to assemble the request and verify the result.

Client JS can handle own postbacks. Maybe not even to their own domain.

Or maybe client server will read that querystring in the resulting request and verify signature.

Totally up to the customer.

Finally, have the sdk also have an option to load an iframe (eg in a dialog) instead of redirect, and use postMessage for securely sending signed result. Just make sure to use Intersection Observer v2 in that case https://web.dev/articles/intersectionobserver-v2

DONE

PS: Hire me ;-)

While you do the banking side, I can integrate a ton of web3-enabled stuff for you including invoices across blockchains, recurring subscriptions, as well as contests and auctions for price discovery. See https://intercoin.org/applications

Re: Show HN: We built an open source, zero webhooks payment processor

#183
post #178
post #175

Earlier quoted context omitted.

> US-centric thinking about invoicing, which makes invoicing unusable (I issue invoices only after a successful payment, because I owe tax on all invoices including unpaid) This sounds strange. I don't think there's anything US-centric about considering an invoice to be a payment request — which makes issuing them after payment nonsensical.

> invoice to be a payment request — which makes issuing them after payment nonsensical Most EU countries use an accrual-based VAT system, where taxes are owed on any invoice issued, paid or unpaid. This makes issuing them before payment nonsensical, because you will end up paying taxes on invoices that will never be paid, thus ruining your business. A proforma invoice exists specifically for the purposes of quoting a…

[deleted]

Re: Show HN: We built an open source, zero webhooks payment processor

#184
post #181
post #174

Quick feedback from a Stripe and Braintree customer, who wrote their own subscription system so as not to use Stripe Billing. The things that caused me problems in the past: * inflexible subscription system * unreliable web component for gathering credit card information * unreliable 3DSecure implementation * incompetent support (these four are the main reasons why I switched from Braintree to Stripe) * complex and u…

Could you elaborate on inflexible subscription system and also what you would like to see from a 3DSecure implementation? Full disclosure: I'm a dev at a fintech startup and we're currently working on these two things so I'm curious how our direction lines up with your thoughts

> inflexible subscription system

For example, Braintree can't switch from monthly to annual billing (or the other way around). You have to delete the subscription and recreate it with a different billing period.

I want my customers to be able to switch plans, billing periods, currency, and buy additional items (user slots), all with proration.

> what you would like to see from a 3DSecure implementation

I would like not to see anything, really. I want to forget 3DSecure even exists. Stripe largely gets this right. Braintree required me to do many rather bizarre things, pass additional data, and then rewrite the entire flow once every couple of years or so. With the last rewrite, I was told that in my case (SaaS subscriptions) I would need to drag the customer through 3DSecure TWICE and that there is no other way. So I switched to Stripe, because I value my customers' time.

Also, 3DSecure with braintree would fail every once in a while and I would get customers from various countries telling me they are unable to subscribe. Braintree support, after a week or two, would inquire and either tell me it's the customer's bank (not helpful), or tell me that I have to rewrite my integration to a New Way of Doing Things, which was usually so far off the mark for my use case it wasn't even funny. I just checked my E-mail archives quickly for "Braintree support", over the years I'm up to around ~400 E-mails exchanged.

Re: Show HN: We built an open source, zero webhooks payment processor

#185
I don't get why you're calling it A) a "payment processor", even though you don't process any payment yourselves, and B) "open source", even though it's running everything through your SaaS and presumably also storing data in your databases (not speaking about telemetry but real business data). I struggle a lot with building a more flexible system for feature gates, usage credits, payment schemes etc., so I 100% understand the pain point you're addressing, but I don't feel like you're delivering much on your headline.

Re: Show HN: We built an open source, zero webhooks payment processor

#187
post #174

Quick feedback from a Stripe and Braintree customer, who wrote their own subscription system so as not to use Stripe Billing. The things that caused me problems in the past: * inflexible subscription system * unreliable web component for gathering credit card information * unreliable 3DSecure implementation * incompetent support (these four are the main reasons why I switched from Braintree to Stripe) * complex and u…

> I issue invoices only after a successful payment, because I owe tax on all invoices including unpaid

(IANA I am not an accountant) but how is it legal? as a customer you want to pay against an invoice, and AFAIK it is required by law in most places.

Re: Show HN: We built an open source, zero webhooks payment processor

#189
post #187
post #174

Quick feedback from a Stripe and Braintree customer, who wrote their own subscription system so as not to use Stripe Billing. The things that caused me problems in the past: * inflexible subscription system * unreliable web component for gathering credit card information * unreliable 3DSecure implementation * incompetent support (these four are the main reasons why I switched from Braintree to Stripe) * complex and u…

> I issue invoices only after a successful payment, because I owe tax on all invoices including unpaid (IANA I am not an accountant) but how is it legal? as a customer you want to pay against an invoice, and AFAIK it is required by law in most places.

You pay against a proforma invoice, or if your credit card gets charged automatically, there is no proforma and you just get an invoice that confirms the transaction.

But in general, this is why proforma invoices exist.

Post reply on HN