Skip to main content

Walkthrough · Beginner · an hour

How to Take Payments Online

How to collect money safely without dragging card data onto your own server, without the guessing — the steps in order, the snag ahead of time, and the tip our support team repeats daily.

The short answer

The job: collect money safely without dragging card data onto your own server. Time to set aside: an hour. Skill needed: beginner.

Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.

By the Hosting & Domains team · Reviewed 18 August 2026

Beginner

Skill rating

an hour

Time budget

5

Steps in total

24/7

Support on call

No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.

First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.

The outline first, then the detail

Over the whole job, you will let the gateway hold the card, open and verify the merchant account, install the gateway extension, test the failures as well as the success and go live, then watch the first real orders arrive.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

The error nearly everyone hits

Assuming SSL alone makes you compliant. The certificate encrypts the connection; PCI scope is set by where card data travels. A hosted or tokenised field keeps that data off your server entirely, whereas building your own card form drags the whole burden onto you.

It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.

A habit worth borrowing

Offer the payment methods your buyers actually use. Cards are the baseline; beyond that, a wallet or a local method your market already knows converts far better than a second card processor nobody wanted.

Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.

The parts that look after themselves here

Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.

Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.

An order going through on a shop that never made the buyer wait for it

A quick platform makes for a short guide

Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.

Mailboxes at your own name are part of the plan — mail is included, not sold back to you at the checkout.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Every undo written out

Any step that could bite is marked, together with the exact way to wind it back.

Jargon never charges you

Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.

Honest about how big it is

Collect money safely without dragging card data onto your own server is a beginner-level job — set aside an hour, with the platform-absorbed steps marked.

The dull parts automated

SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.

Works exactly as printed

Every step is proven on the platform we run — none of the 'your host may vary' hedging.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how an hour stays an hour.

Quick Start

Order placed to site online

  1. 1

    Let the gateway hold the card

    Card details are tokenised on the provider's own infrastructure by Stripe, PayPal and the rest. Raw numbers never reach your hosting, which keeps you inside the lighter PCI bands rather than the heavy ones.

  2. 2

    Open and verify the merchant account

    Business details, bank account, identity documents. Verification takes days rather than minutes, so start it long before the launch date rather than during launch week.

  3. 3

    Install the gateway extension

    Each provider ships an official plugin. Paste the API keys from their dashboard, choose which card brands to show, and leave the sandbox keys in place until testing is finished.

  4. 4

    Test the failures as well as the success

    Every provider publishes test card numbers for declines, for 3-D Secure prompts, and for timeouts. Until the unhappy paths say something useful to the shopper, the checkout is unfinished.

  5. 5

    Go live, then watch the first real orders arrive

    Replace the sandbox keys with live ones, buy something small and real, then refund it. Confirm the money moved, the order was recorded and the refund landed before you announce anything.

Built In

Fitted to every plan

  • Upgrades applied in place, with no migration when you change plan
  • Mailboxes that answer at the name you hold
  • 99.9% uptime as the target, watched around the clock
  • cPanel, which is what most of the industry already runs
  • People on the support desk every hour of every day
  • A renewal figure identical to the one you registered at
  • Staging copies for trying a change before it goes live
  • Your existing site brought across by our engineers, at no charge
  • WordPress Toolkit, with the updates seen to for you
  • LiteSpeed caching in the server itself rather than bolted on by plugin

Frequently Asked

The questions that come up most

Which gateway should a small shop start with?

Whichever one pays into your bank and carries a name your customers know. Card-led markets and developer work suit Stripe; buyers who are wary of typing card details somewhere unfamiliar tend to trust PayPal. Plenty of shops run both, and it costs nothing beyond the per-transaction fee on each.

Can I take payments without a full shop?

You can. The same providers offer payment links and hosted checkout pages that take money with no catalogue behind them, which fits deposits, invoices and one-off services. You get the gateway's security posture without maintaining a shop you never needed.

Will the renewal cost more than the first term?

No. The rate you order at is the rate you renew at, year after year. There is no introductory teaser here, so no second-year jump is waiting — the hosting line stays a fixed figure your accounts can plan around.

Is the free SSL certificate genuinely free?

Entirely, on every plan. The certificate is issued as soon as the name points here and reissues itself well before it lapses. On encryption it matches any paid DV certificate — the paid options exist for wildcard coverage or organisation validation, which most sites never need.

Keep reading

  • How to Create a Subdomain

    Put blog.yourdomain or app.yourdomain live in less time than it takes to make coffee — beginner level, about 5 minutes.

  • How to Enable LiteSpeed Caching

    Turn the server's cache engine on and verify it is genuinely delivering hits — beginner level, about 20 minutes.

  • Best LiteSpeed Hosting

    Weighed properly, ending in a verdict rather than a table of ticks.

  • Web Hosting

    cPanel hosting on NVMe drives — SSL, the migration and year one of the name all included.

  • Magento Hosting

    Plans carrying the memory and PHP headroom Magento genuinely asks for.

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

Put the site on ground you own.

Free SSL, a free migration, renewals billed at the original rate, and people on support around the clock. That is the whole of it.

View Web Hosting plans