Get paid the way privacy buyers prefer
Invoice each period's mailbox count and the customer pays it 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
Email is a service people can't afford to lose, but the stored card reissues, changes number, and expires on its own schedule. When the renewal fires on a dead card, the charge fails, the failed-payment emails start, and a mailbox the customer depends on drifts toward suspension over a payment detail rather than a decision to leave.
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
Privacy-conscious customers are global, but a card abroad often won't clear with a foreign merchant — geo-blocks, low cross-border approval, hard 3DS. On a thin per-seat margin, every decline is a subscriber lost, on top of the fixed-fee drag on the ones who do pay. (Side-by-side in Pricing.)
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
A stablecoin payment has no fixed per-charge leg, so the cost scales with the bill instead of swamping it. A $3 mailbox keeps its margin instead of giving up 13% to a flat fee. The smaller the plan, the bigger the difference — the opposite of how cards treat low-priced per-seat tiers.
Seats paid from a wallet — nothing to expire or re-auth
Each period your system issues one invoice for the seat count and the customer pays it from their wallet in a single transfer. No card-update prompt, no strong-customer-authentication step, no stored card to expire and pause the inbox. The customer approves each renewal themselves instead of relying on a card that quietly dies.
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
That same $3 mailbox costs about $0.03 to accept on Paymos instead of about $0.39 — no fixed-fee floor and no cross-currency cut, and a customer abroad pays from a wallet with no geo-block in the way. The recovered margin compounds across a seat-billed book. Full rate card in Pricing below.
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
Same rate for the $3 mailbox and the annual team prepay. High-volume tier at 0.3% on request. Compare to roughly 13% all-in on a $3 card charge once the fixed fee is counted, plus failed-renewal churn.
See pricing