Email hosting, paid the way privacy buyers prefer
Invoice each period's mailbox count and the customer pays it at a crypto checkout from their wallet — no card-update prompt, no failed renewal, and the privacy-minded buyer gets the payment method they came for.
Why per-seat email hosting fits cards badly
Why does a $3 mailbox cost so much more than 3% to bill?
Four mismatches between low-priced, per-seat, privacy-first hosting and card processing.
A fixed per-charge fee swamps a $3 mailbox
A $3 mailbox costs about $0.39 to accept on a 2.9% + $0.30 processor — roughly 13%, since the flat $0.30 alone is 10% of the seat before the percentage lands. Per-seat pricing only works if the fee shrinks with the seat; a fixed charge does the reverse.
The card on file expires and pauses the inbox
Nobody plans to lose their mailbox, yet its billing rides on a card the bank reissues and retires on a schedule of its own. When that renewal fails, the warning notices land in the inbox you are about to suspend — the same address every other password reset goes to. The customer never decided to leave; a billing detail took out the channel they recover everything else through.
Privacy-first customers don't want to hand over a card
The people who pay for private email specifically came to avoid surveillance-driven, ad-funded inboxes. Asking them to put a card on file — tied to their identity and tracked by the network — works against the exact reason they chose you. A wallet option is the payment method this audience actively prefers.
Cross-border declines lose international subscribers
Private-email buyers sit in every market, and a card issued in one country clears badly in another: cross-border approval rates fall, a hard 3DS step-up gets abandoned, some issuers geo-block the charge outright. Each refusal is a subscriber you never meet — and on a per-seat price already thinned by a flat fee, the ones who do get through are covering the ones who couldn't.
How a flat percentage fits per-seat billing
What changes when the seat invoice settles in stablecoins?
Four things that go right the moment per-seat billing stops running through fixed-fee card rails.
No fixed-fee floor — a $3 mailbox keeps its margin
Accepting a $3 mailbox costs a proportion of it and nothing else. No flat component sits underneath, deciding that the smallest seat is the one charged 13%, so the standing argument against your entry plan disappears. The economics read identically at one mailbox and at four hundred, which lets the price list follow the product rather than the rail.
Seats paid from a wallet — nothing to expire or re-auth
The renewal is an invoice the customer settles themselves, out of a wallet they already open every week. Nothing is stored on your side to go stale, so the failure that suspends an inbox and then sends the warning to that same inbox never begins. No card-update prompt and no authentication step to re-clear either — the seat count changes, the next invoice reflects it, and the customer approves an amount they can see.
The payment method privacy buyers want
Your customers came for privacy, and a wallet payment fits that — no card tied to their identity, no surveillance-card economics behind the inbox they pay to keep clean. Offering wallet alongside cards converts the segment that was hesitating at the card form, and it's a selling point, not a workaround.
Roughly $0.03 to accept on a $3 mailbox, not $0.39 — and global
Put the two numbers beside each other on a single seat: $0.39 to the card stack, about $0.03 here. That is most of a $3 mailbox's processing cost gone, and it does not come back as a conversion cut when the customer is abroad — they pay from a wallet, the geo-block never applies, and the dollar you invoiced is the dollar you keep. Across a seat-billed book it stops being a rounding line and starts being margin.
How email hosts wire Paymos into per-seat billing
Which integration fits how you bill seats?
Three ways to wire stablecoin payments into your mailbox billing.
Server-side API — wired into your seat-billing cycle
Your system knows the seat count per account at period close. It calls the Paymos API to create the invoice for the rolled-up total; the customer pays from their wallet; an HMAC-SHA256 webhook confirms settlement and your billing marks it paid. It's the integration shape you already run for your card gateway; aim it at Paymos instead and the per-seat fee math turns in your favour.
See details
Hosted Checkout — signup and plan upgrades
For a new signup or a seat upgrade, send the customer to a Paymos-hosted page. They pay from their wallet and return with the plan active. No card form on your domain — fitting for a privacy audience — and no 3DS to fight on international customers who'd otherwise decline.
See details
Payment Links — annual prepay and team plans
For an annual prepay or a team buying a block of seats, generate a payment link from your dashboard or CRM and send it over. The customer settles it from their wallet and it closes on confirmation — a clean fit for buyers who want a real invoice and prefer to pay once a year.
See detailsEmail hosting billing flows on stablecoins today
What seat-billing patterns run cleanly on a wallet?
Four flows from real email-hosting setups — single mailbox, team seats, annual prepay, and an international subscriber.
Single mailbox — period invoice from your system
A solo customer on a single private mailbox: your system issues the period invoice and they pay it from their wallet. No fixed-fee floor eating a cheap plan, no dead card pausing the inbox — the mailbox stays active the moment the payment confirms, on the privacy-friendly method they chose.
Team seats — one invoice for the seat count
A small team on a per-seat plan: each period your system rolls up the seat count into one invoice and the team pays it from a wallet in a single transfer. Add or remove seats and the next invoice reflects it — no card re-authorisation when the count changes, only a fresh invoice each period.
Annual prepay — Payment Link
A privacy-minded customer prepays a year to avoid monthly renewals and keep their footprint minimal. They pay once from their wallet via a payment link and the plan extends for the full term. No card on file across the year, no failed renewal to chase — one payment, twelve months secured.
International subscriber — direct wallet payment
A subscriber abroad whose card won't clear with your merchant account pays from a wallet instead. The payment confirms in seconds and the mailbox activates — a subscriber you'd otherwise have lost to a decline, paying on the method a privacy audience already prefers.
Email hosting on stablecoins
Frequently asked questions
How does Paymos fit our per-seat billing and suspension logic?
Seats are recurring — does the customer pay manually each period?
Doesn't paying from a wallet conflict with our privacy promise?
How do refunds work for a cancelled or downgraded plan?
Which networks and stablecoins should I offer for cheap mailboxes?
Can I keep cards for customers who want them and use Paymos for the rest?
Honest disqualifier
When NOT to use Paymos for email hosting billing
Four cases where card billing still fits your mailboxes better.
Your users can't be asked to think about renewal, ever
Email is the account everything else resets through, and some customers want it renewed with zero involvement — a stored card, flaws included. A wallet renewal always asks the owner to approve. Soften that with annual prepay and reminders, or keep card auto-renew as the default and give the wallet to the privacy segment.
Your audience isn't the privacy crowd
The wallet option resonates when customers chose you to escape ad-funded, identity-linked inboxes. If you sell mainstream business mailboxes to local companies that pay comfortably by card, that resonance is absent — the fixed-fee saving on a $3 seat is the whole story. Weigh it against the cost of running a second rail.
Sales tax and VAT are handled by your card processor today
Paymos won't register you in new jurisdictions, calculate rates, or remit anything — it has no tax layer at all. If the card stack currently does that work across your customer map, dropping it means picking the work up yourself or with your accountant. Keep cards on the taxed segments and run wallet revenue as its own ledger line.
There's no exchange between your wallet and your bank yet
Mail servers, storage, and staff get paid in fiat; Paymos pays you in USDT or USDC and stops there. Until an exchange account turns that balance into money your bank recognises, every settled invoice adds to a pile you can't spend. Open the route first — it's a one-time setup that unlocks everything else.
Related flows
Other Services & Hosting sub-niches on Paymos
Pricing
1.0% per settled invoice. No fixed fee, no rate markup
The charge is a share of whatever the seat is worth, on a $3 mailbox and on the annual team prepay alike. Moving the balance to your own wallet adds no percentage of ours — a subsidised network fee for the route, quoted before the transfer goes. We go down to 0.3% on seat count and what a plan is worth; ask from your first invoice. Per-seat pricing only survives if the fee shrinks with the seat, and a flat card component does the opposite: on that $3 mailbox the stack lands near 13%.
See pricing