This didn't start as a product
It started as the billing system for our own hosting company, and it had been collecting real payments for years before we thought of selling it.
Where this comes from
The team behind Payezz runs GamzyHost, a game server hosting company. Like any provider, we needed to collect recurring payments, issue invoices, suspend what went unpaid, renew what was paid and provision what was sold. We built it ourselves because what was on the market either cost as much as a part-time employee or meant maintaining a self-hosted install, with all its updates and scares.
That engine has been in production for years: charging real renewals, issuing real invoices and handling real failed payments. It's the only fact on this page we can prove, so it's the only one we give.
Payezz is that engine, extracted, generalized and fixed. Generalized because what used to be hard-coded constants there (the games, the RAM plans, the locations) are rows in a database here, which any provider configures from their admin panel. And fixed because, while documenting what we had in order to rewrite it, we found defects we have no intention of repeating: invoice numbering in six different formats, a webhook that marked an event as processed before processing it, and a failed payment that suspended the service the same day and deleted it five days later.
The decisions that define it
A product is the sum of the things it says no to. These three took some arguing, and they're written down, with their reasoning, in the architecture document:
One isolated instance per customer
Its own container, its own database, its own domain. There's no shared database where a badly written filter shows one provider's customers to another. It costs more to run, and we accept that.
Everything editable from the panel
What other systems make you do by editing files or buying an add-on is a database row here. You don't get access to the container, and that's exactly the guarantee that you won't need it.
One Stripe account: yours
The money from your sales goes into your connected account, not ours. Payezz takes its fee on each transaction and never holds your buyers' funds at any point.
What you won't find here
This site has no testimonials, no customer logos, no counter of invoices issued and no five-star ratings. It's not a style choice: we simply don't have them. Payezz is in early access and there are no third parties yet who can give an opinion. When there are, they'll appear with their full names, and you'll be able to check who they are.
For the same reason, the comparison with other solutions marks as “coming soon” whatever is designed but not built, even if it makes the table look worse, and the documentation says, for every piece, whether it works today or is only specified.
As for pricing, the only thing set in stone is the free plan's fee: 1.9% + €0.20 per transaction. The paid plan prices shown on the site are a proposal and are marked as such, both on the pricing section and in the calculator.
Where it stands
The fee engine, the authentication contract between the instance and the control plane, and both database schemas are written and tested. The payment gateway is in place and still needs its database queries. The storefront editor, the SEO panel and the MCP server are specified but not built.
If it's useful to you as it is, write to us and we'll talk about early access without making anything sound better than it is. If you need something that doesn't exist yet, we'll tell you, and we won't charge you for waiting.
Talk to us
We're a small team and we answer ourselves, with no first-line support layer in between. Write to hola@payezz.app or visit the contact page.
Does this sound like a fit?
Create your free account and see it from the inside, no sales call.