Skip to content

Collect cross-border invoices by the next block

Let a customer in São Paulo or Singapore pay a bare-metal invoice to your Paymos balance, even when their card gets declined — the money is yours the moment it confirms, no wire to wait on.

Collect cross-border invoices by the next block

Why dedicated-server receivables sit in limbo

Why does a paid server invoice take days to become cash?

Four ways cards and wires slow down — and shrink — what an overseas customer pays you.

International cards decline for a US or EU merchant

A dedicated-server customer in Latin America, MENA, or Southeast Asia often can't get a card accepted by a foreign hosting merchant — issuer geo-blocks, low cross-border approval rates, hard 3DS walls. The customer wants to pay and can't, and you either lose the order or run a manual workaround that takes days.

Wires are slow and skim the invoice

A bank wire on a monthly bare-metal bill can take a few days to land and cost $15–50 inbound on the correspondent chain, often with a 1–2% bank currency margin layered on top — at a rate the bank sets. The receivable sits in float while you've already provisioned the hardware.

Manual reconciliation eats hours every cycle

Wires arrive with truncated references, mismatched amounts after fees, and no clean invoice ID, so finance reconciles by hand every billing cycle. On a book of international customers, that's hours of matching payments to invoices that should have closed themselves the moment money moved.

Processing skims about 3% off the cards that clear

On the cards that do go through, a typical 2.9% + $0.30 processor takes about $14.80 on a $500 monthly server bill — roughly 3% before any cross-currency markup. Across a book of recurring servers it's a line you don't control, on top of every declined order and every slow wire. (Side-by-side in Pricing.)

How stablecoin settlement closes the receivable

What changes when the server invoice settles in stablecoins?

Four things that go right the moment cross-border server payments stop running through cards and wires.

Overseas customers pay direct — even when their card declines

A customer in São Paulo or Singapore pays the bare-metal invoice from a wallet, no issuer geo-block and no 3DS wall in the way. One payment flow regardless of country, no per-region processor integration. You collect from the heavy-demand markets that cards were quietly turning away.

The money is yours on confirmation — no wire wait, no reserve

The customer pays and the funds credit your Paymos balance within seconds of confirmation — no multi-day wire, nothing held back in a reserve. The receivable closes the moment money moves, exactly when you've already provisioned the hardware and want the cash to be yours.

Invoice ID travels with the payment — reconciliation closes itself

Each invoice carries its own ID and amount, and a webhook tells your system the exact invoice that settled. No truncated wire references, no fee-shrunk amounts to match by hand. Finance stops reconciling cross-border payments line by line because the rail closes the receivable for them.

Roughly $5 to accept on a $500 bill, not $14.80 — and the rate stays yours

That same $500 server bill costs about $5 to accept on Paymos instead of about $14.80 — with no cross-currency cut, no inbound wire fee, and no rate set by a bank. Price in a dollar stablecoin, receive the same stablecoin, convert on your own schedule. Full rate card in Pricing below.

Server billing flows on stablecoins today

What server billing patterns run cleanly on a wallet?

Four flows from real hosting setups — monthly bare-metal, cross-border customer, enterprise prepay, and one-off setup.

Monthly bare-metal — recurring invoice via WHMCS

A monthly dedicated server billed through WHMCS: the renewal invoice goes out on your existing schedule and the customer settles it from their own wallet. No card on file to expire and trigger a suspension, no failed renewal on a paying customer — the plugin marks it paid and provisioning carries on uninterrupted.

Cross-border customer — direct wallet payment

A customer abroad whose card won't clear with your merchant account pays the server invoice from a wallet instead. The payment confirms in seconds, the receivable closes itself, and you keep a high-value customer you'd otherwise have lost to a decline — with no manual top-up workaround on either side.

Enterprise quarterly prepay — Payment Link

An enterprise customer prepays a quarter of capacity against a contract. You send a payment link, they pay from a corporate wallet, and the net amount after processing credits your Paymos balance the same day. No recurring authorisation to maintain; the contract handles renewal pricing and the cash is yours up front.

One-off setup or migration — Payment Link

A setup fee or a migration project billed once: a payment link goes out, the customer pays from their wallet, and it lands before the work starts. No fixed-fee floor eating a small invoice, no dispute window opening behind a service you've already delivered.

Dedicated servers on stablecoins

Frequently asked questions

Does the Paymos WHMCS plugin handle provisioning and suspension?
The plugin handles the payment leg — it marks the WHMCS invoice paid when settlement confirms and fires the event your provisioning and suspension rules already listen for. Your existing WHMCS automation (server creation, suspension on non-payment, termination) runs unchanged; Paymos replaces the gateway that confirms the money arrived.
How fast does a payment confirm, and can I suspend on non-payment safely?
A wallet payment typically confirms within seconds to tens of seconds depending on the network the customer picks. Paymos waits for the required confirmations on each network — small invoices clear quickly, large ones wait until finality is safe — before firing the paid webhook, so your suspension logic acts on a confirmed settlement, not an unconfirmed transfer. Your failed-payment and grace-period rules stay in your hands.
How do refunds and credits work for an over-provisioned or cancelled server?
A refund or credit is a transfer you make yourself, from your Paymos balance back to the customer's wallet, for whatever amount your terms call for. Paymos charges its percentage only on a settled invoice — there's no extra fee on a refund, and no card network adjudicating a dispute over a server you've already run.
Which networks and stablecoins should I offer for cross-border server customers?
For most server bills, fast low-fee networks like Arbitrum, Base, and BSC keep the economics clean for both sides. USDT is the workhorse for international customers — especially in LATAM, MENA, and Southeast Asia where it's the local default — and USDC is the common treasury asset for customers who plan to convert to fiat. Which network and stablecoin to use is best left to the customer at checkout.
Can I keep cards for domestic customers and use Paymos only for international?
Yes, and it's a common setup. Keep your card gateway for domestic customers who pay fine on cards, and route the international segment — the declines, the slow wires — to Paymos. A gateway setting in WHMCS or your panel picks which option a customer sees; over time many cross-border customers self-select to wallet for the faster confirmation.
Do I need to hold stablecoins, or can I convert to fiat?
You receive the stablecoin to your Paymos balance and decide what to do with it. Many hosts hold a working balance in USDC or USDT and convert to local fiat on their own treasury schedule through an exchange relationship they already have. Paymos settles the payment to your Paymos balance; it doesn't move the money to your bank for you, so the conversion step stays under your control.

Honest disqualifier

When NOT to use Paymos for server billing

Four cases where cards or bank transfer are still the right call.

Every server customer is local and their cards clear

This rail earns its keep on international declines, inbound wire fees, and exchange-rate margin. If your whole book pays domestically by card at high approval rates, those levers never move, and a second settlement flow still costs finance and support attention. Leave cards in place until cross-border demand gives the wallet something real to do.

Your enterprise contracts run on POs and net-60

When the contract specifies a purchase order, net-60 terms, and payment through the customer's AP system, instant settlement is a mismatch with their process, not a feature. Keep bank transfer for that tier. Point Paymos at the buyers who can actually pay from a wallet today — cross-border customers and prepaid capacity deals.

Hesitant buyers need card dispute rights to commit

A stablecoin invoice settles final — there's no network arbiter a nervous first-time customer can appeal to. That protects you on hardware you've already racked, but it removes a reassurance some buyers want before sending $500 to an overseas host. Offer cards beside the wallet and let each customer pick their comfort level.

Your treasury has no route from stablecoins to fiat

Settlement is USDT or USDC to your Paymos balance — Paymos never touches your bank account. Data-center rent, power, and bandwidth are fiat costs, so without an exchange relationship the balance is stranded. Set up that exchange route first; after that, holding a working stablecoin balance becomes a treasury choice rather than a blocker.

Pricing

1.0% per settled invoice. No inbound wire fee, no exchange-rate margin

Same rate for the $20 VPS add-on and the $5,000 enterprise prepay. High-volume tier at 0.3% on request. Compare to roughly 3% all-in on cards, plus declines and $15–50 wire fees on cross-border.

See pricing

Collect every server invoice, wherever the customer is