Discourse with a full implementation of AI + crypto (BTCPay as a bridge to everything else) sounds great to me.
That cuts the men in the middle and offers a direct payment method for our customers.
Then if someone wants to pay 10% to PayPal, they could develop their own plugin like with Stripe, Patreon, or whatever.
Open-source needs to be close to open-source from a philosophical (and practical) perspective.
In 8 years working full-time with Discourse I have had maybe 2 customers that wanted to pay with cryptocurrency. I guess you have a very different customer base. I suspect for the bulk of Discourse Enterprise customers, it’s less than that. For the most part, Enterprise customers drive development of new features.
And if you want to support BTCPay or whatever, you can develop or fund your own plugin. BTCPay doesn’t support a Ruby library, and the Bitpay ruby client they link to seems to have been abandoned (it’s been marked read-only). That’s going to make developing and maintaining a BTCPay plugin for Discourse complicated.
Already tried to do it a long time ago. I will try to fund it on a different community that could be more interested to come.
One simple integration could fit for everyone who wants to receive direct money from their customers.
That’s better to offer plenty of solutions to fit with many centralized providers.
Stripe and PayPal leave half of the world outside because there is Latam, Asia, Oceania.
BTCPay is open-source, which makes the integrations more sustainable and easy to maintain.
Integrations
Everyone has their opinion; only one actual type of money is open to everyone and it’s almost free by design.
That’s a very good example of a Faulty generalization - Wikipedia. The world seems to be a better picture to analize.
Edited and republished to respect the community guidelines
Cool! That’ll make things easier. The link that I found linked from one of the links you provided linked to some unmaintained repo that said not to use it (by my quick read, anyway).
You didn’t offer a budget and no one else seemed interested. My wild guess on a budget was $2000-10000. Lots of ways to make the budget on the low end by hard-coding things and, maybe referring to products already created on the BTCPay side of things.
A quick solution would be to use WooCommerce and WordPress. It’s a bit fussy, but if the problem you’re trying to solve is “how can I accept BTCPay with Discourse” then WooCommerce would probably be easier (you don’t have to tell me the reasons to avoid WordPress! and WooCommerce isn’t free)
True enough! Whether a decade makes my point any more or less hasty is not an argument I’ll enter unless we’re both armed with beers in our hands 
. And maybe it’s true that Discourse.org would have thousands more customers if only they had a BTCPay plugin, but until paying customers ask them for it they aren’t going to do it.
You might be able to find someone young and hungry for a programming project (perhaps for a course or One Hour: Ignite. Inspire. Code.) willing to take it on as a proof of concept.
Fair enough, thanks for your follow-up and being open to constructive discussions about it.
That’s nice to hear. Now I have something to offer when looking for funding in the Monero community.
I’m currently analyzing the best approach to use Ghost SSO on Discourse (I really want to use Discourse’s database, but payments should sustain our community, so I’m in a tough spot here).
BTCPay recently added Ghost payment support, and we have Ghost on our blog, so I think it should work for us this way.
I appreciate the suggestion. Ghost looks better to me than WordPress, which goes against my digital philosophy, if it exists.
Yeah, I understand it but I like to think of exceptions so here are my prayers, hehe.
Sounds good to me. Cheers
also consider that the subscriptions are managed by stripe. So you would have to implement all the logic about canceling subscriptions, expiring subscriptions and so on.
I did that with the monero subscriptions plugin. It is a lot of work. You are basically building a mini stripe.
