Knowledge base

Taking payment from your clients

Connecting your own gateway, what we still bill you for, and who handles a dispute.

You bill your clients; we bill you. Those are two separate money flows and they use two separate gateways.

Connecting yours

Reseller → Gateways → connect. Your clients' cards are then charged by your account, the money lands in your bank, and your company name appears on their statement. We never see their card details.

Supported: card via the major gateways, PayPal, and crypto. Connect more than one and your clients choose.

What we bill you regardless

Your own invoice from us is for what your clients consumed — sites, storage, bandwidth, domains, AI, licences — at your reseller rate, on your own billing cycle. That is unaffected by whether your clients have paid you, which is the working-capital risk of reselling and is why client wallets and dunning exist.

Who handles what

  • A client's card is declined — yours to chase. Dunning does the chasing for you.
  • A client disputes a charge — yours. It is your merchant account, and your evidence.
  • A refund to a client — yours to issue, from your gateway. It does not credit your invoice
  • from us; the resource was consumed.

If you do not connect a gateway

Clients can still be billed against wallet credit that you top up on their behalf, which suits resellers who invoice offline. Reseller → Client wallets is where that lives.

⛔ Test with a real card before you onboard a client. A gateway that is connected but not verified takes payment and holds it, and the first you hear is a client saying they paid.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →