Anyone here know anyone from Paddle that you can put me in touch with? (Or share your experience with them?)
I’m reconsidering whether Stripe is the right solution for the initial payments option in Domain (https://codeberg.org/domain/app) or whether it makes more sense (and would be easier for folks who want to run their own Domain instances and become Small Web hosts) if I integrated a Merchant of Record (MoR) solution instead.
Right, so I signed up with Paddle and with FastSpring (also a merchant of record) and I don’t think Paddle is going to work as you can’t create subscription plans via their API. In FastSpring you can so I’m going to continue to looking at that. So, to update my query:
Anyone know anyone at FastSpring they can introduce me to or have any experiences with them they can share with me?
(I may still end up going with #Stripe.)
Thanks!
I’m sure you’re all riveted to hear my next niche micro-update on finding a payment solution to integrate into #Domain¹ but I’m actually reconsidering #Paddle. The more I think about it, the less custom logic there is in Domain to handle payment providers the better. A very lightweight abstraction over embedding a #payment form and handling #webhooks should make it easier to add others in the future at the cost of more setup in the payment provider itself.
Yep, it looks like I’m going with Paddle (https://paddle.com) as the first supported payment system for Domain*.
(Barring any issues with getting our use case approved.)
So, asking again: does anyone know anyone that works at #Paddle? Would love to talk to them about what we’re trying to do with the Small Web and Kitten ** and Domain and hopefully have them support our use case.
* https://codeberg.org/domain/app
** https://codeberg.org/kitten/app
The initial integration of Paddle into Domain is now complete. I’m happy with how it turned out.
Now the only (“only” he says) bit left is reimplementing the provisioning and setup of Small Web servers running Kitten (or Kitten apps).
It‘s getting there…
PS. Just noticed and fixed the typo in the “Stay Small!” section. It now reads:
“(e.g., one where cities can use tokens to provide their citizens with access to the commons from the commons, etc.)”
(That’s just one example based on the work we did with the City of Ghent a little while back to prototype how something like that could work. In addition to not taking payments, you will also be able to use tokens – not cryptocurrency; just pre-generated tokens that you can distribute to folks.)
@aral It's all pretty riveting, to be fair. I'm personally grateful for your posts and feel like I learn something every time I see one.
@konstantin Yep, exactly. But gotta start somewhere :)
Hadn’t heard of Mollie. Will check them out, thanks :)
@aral If Paddle is a service that takes care of the whole integration and as a Domain user you then don't have to fiddle with Stripe or Adyen, i would say that is an improvement.
The 5% + 0,50 is a bit steep compared to (from the top of my head) lower rates that these other companies offer. But having to not deal with most of that payment and taxes stuff would be worth it.
And i think as a platform (Domain) offering a more plug and play solution like this makes it more attractive.
@ff0000 Good to have the validation, thanks.
I’m going to start implementing an integration today and see how it goes :)
@aral Of course! I have experience with integration payments through Adyen and Stripe, both offer plug and play options (which we don't use as a business, because custom checkout and world wide transactions that have to be considered). So once you step outside of their *drop in huge SDK and pray* it becomes a huge hassle.
As i understand, for Domain you want to offer payment integrations that are as easy to do as that PayPal pay now button? (minimal technical know how needed).
@ff0000 Want to make it as easy as possible but running Domain (to enable the hosting of Small Web sites and apps) will always require some technical knowledge and organisational investment of time and resources (as opposed to running Small Web sites and apps, which should require none).
@aral I understand, but if you can keep the threshold as low as possible, that would be nice, so i understand this approach. :)
@aral have you looked at https://www.lemonsqueezy.com it is on my list to look at and looks like a similar but younger paddle
@Sdevore My eventual goal is to support multiple so it’s on my list too. But need to start with one :)
@aral It looks great in all its "simplicity".
Love the minimal style!
@aral At what point would you say that it's stable enough to build a full test case with? (for instance a new version of my band's website). For fun, and testing.
@ff0000 I’d say you can play with Kitten for that right now (and please report any issues if you run into any while you do) but until Domain is ready, deployment won’t be easy.
@aral Well good thing i don't have a lot of free time at the moment, so i won't be able to do full pen tests and e2e tests, but once i have i will of course share any issues. :)
@ff0000 Thanks; that’ll be hugely useful, appreciate it :)
@ff0000 Thanks!
Kitten will always be for developers and *hosting* Domain *instances* will always be for folks with technical knowledge but I am trying to make every component in the system as simple to use as possible. That’ll be something we never stop iterating on :)
If we keep that philosophy throughout, then *using the things we make* with Kitten (and using Domain to obtain them) will hopefully be easy for folks who use technology as an everyday thing to do everyday stuff.