There is a particular kind of lost sale that stings. Someone says yes, asks how to pay, and then waits three days while you work out how to send an invoice. By the time they get it, the moment has passed. Knowing how to accept payments online is not a technical skill any more; it is basic business hygiene, and it takes an afternoon.
The good news is that the hard parts have been solved by other people. You do not build card processing. You do not store card numbers. You connect to a processor that already handles the regulated, terrifying parts and you get on with selling.
This guide covers accepting payments online end to end: the options, how to do it without a website, choosing a processor, what fees really cost, when the money lands, deposits and subscriptions, designing a checkout that converts, refunds and disputes, security, and the paperwork you should have in place before the first payment.
What you actually need to accept payments online
Three things. Somewhere for the customer to pay — a page with an amount and a card field. A payment processor that takes the card details, checks them, and moves the money. And a bank account in your name or your business name for the processor to pay into.
Everything else is convenience layered on top: receipts, records, refund buttons, subscriptions, tax handling. Useful, but not the thing standing between you and the first sale. People delay for months because they think they need a store, an accountant and a limited company. They need a link and a bank account.
The one thing you never need is to handle card numbers yourself. If any setup asks you to receive card details by email, message or over the phone into a spreadsheet, stop. That is the fastest route to a security problem you cannot afford.
Payment links, checkout forms and full stores
There are three levels, and most businesses over-build. A payment link is a hosted page for one amount or one product. You send it, they pay, it is done. Ideal for invoices, deposits, one-off jobs and anything you agree in a conversation.
A checkout form is a payment link with questions attached. The customer chooses options, answers what you need, and the total updates before they pay. This is the sweet spot for services, custom orders, bookings and event tickets, because the answers and the money arrive as one record instead of two you have to match up later.
A full store is a catalogue with browsing, search, categories and stock. It is genuinely better when you have dozens of products and repeat buyers. For fewer than about ten things, it is mostly maintenance you will resent.
- Payment link — fastest, one price, no questions
- Checkout form — options, quantities, custom totals, customer details
- Storefront page — several products behind one link
- Full store — catalogue, stock, browsing, search
- Invoice — a formal document with terms and a due date
How to accept payments online without a website
You do not need a site because the payment page is already a page. Your processor or form builder hosts it, it works on every phone, and it has a URL. That URL is the only asset you need, and it can live anywhere a link lives.
Put it in your social bio so people can buy from the profile they already found. Paste it into a direct message the moment someone asks the price. Add it to your email signature. Print it as a QR code on a counter card, a van, a market stall or a receipt so an in-person conversation ends in a payment rather than an intention.
This is also how you sell before you have decided what your business looks like. A link costs nothing to change. A website you built around the wrong offer costs a weekend to rebuild every time you learn something.
Choosing a payment processor for a small business
Processors look similar on the homepage and differ in the details that bite. Start with availability: not every provider supports every country, and support for your country as a buyer is not the same as support for your country as a seller receiving payouts.
Then compare the things you will feel every week. Which payment methods it offers your customers — cards, digital wallets, local bank methods — because people abandon when their normal method is missing. How fast payouts are, and whether new accounts are held longer. How refunds are issued and whether the original fee comes back. And what happens when something goes wrong: whether there is a human to reach.
Do not choose on headline rate alone. A slightly cheaper percentage means nothing if the checkout drops your customers, the payout takes twice as long, or your account is frozen with no explanation and no phone number.
- Supported in your country for receiving payouts
- Payment methods your customers actually use
- Published fees, including international and currency conversion
- Payout schedule and first-payout delay
- Refund and dispute handling, and what fees are returned
- Whether it connects to the form or storefront you plan to use
- Reachable support before you have a problem
Understanding payment processing fees
Every card payment costs you a percentage plus a small fixed amount. The fixed part is what makes small transactions inefficient: on a very low-value sale, the flat fee can be a meaningful share of the total, which is a good argument for bundles and minimum orders rather than selling single tiny items.
Then come the extras. International cards usually cost more. Currency conversion adds a spread. Subscriptions can carry an additional fee. Disputes carry a fee that you often pay whether or not you win. Read your provider's current published pricing page, because rates change and vary by market — never plan on a figure you half-remember from a blog post.
Handle it in your pricing, not at the checkout. Adding a surcharge at the last screen is one of the most reliable ways to lose a sale, and in some places it is restricted or banned outright. Set a price that already survives the fee and let the total the customer sees be the total they pay.
Payouts: when the money actually lands
New sellers are consistently surprised by the gap between sale and settlement. The card is charged instantly, but the processor holds the funds through a settlement window and then pays out on a schedule — commonly a few working days, sometimes longer for a brand new account or a higher-risk category.
Plan for it. If you buy materials for each job, take a deposit up front rather than assuming today's sale funds tomorrow's supplies. If you have a big launch day, do not commit that money to a bill dated the same week.
Also make reconciliation easy on yourself from day one. Payouts arrive as batches, not as individual sales, so the amount in your bank rarely matches any single order. Keep your processor's payout reports and your order records together, and reconcile monthly rather than trying to reconstruct a year in April.
Receipts, invoices and tax
A receipt is proof the customer paid; an invoice is a request to pay with terms attached. Businesses buying from you will often need a proper invoice with your details, the date, a description, the amount and any tax shown separately. Consumers usually just need a clear receipt.
Send the receipt automatically the moment payment succeeds, and make sure the name on the receipt matches the name that appears on their card statement. Mismatched names are one of the most common causes of an innocent dispute weeks later, when somebody scans a statement and does not recognise you.
Tax rules vary too much by country to summarise safely, but two habits travel everywhere: keep every payout report and every order record, and find out early whether you need to register for sales tax, VAT or the local equivalent at your level of turnover. Ask an accountant once, at the start, rather than guessing repeatedly.
One-off payments, deposits, instalments and subscriptions
A one-off charge is the simplest and covers most product sales. But service businesses usually do better with a deposit: a smaller committing amount taken at booking, with the balance due on completion. It filters out people who were never serious, funds the work, and dramatically reduces no-shows.
Instalments split a large price into scheduled payments and can make a premium package accessible without discounting it. The trade-off is admin — failed payments happen, and you need a plan for chasing them that is not personal and awkward.
Subscriptions are the strongest form for anything ongoing: memberships, retainers, maintenance plans, paid newsletters. They also come with obligations. Make cancellation easy and obvious, warn before renewal, and never bury the cancel route. Hard-to-cancel subscriptions generate disputes, which cost you more than the customer you were trying to keep.
- One-off — products, single jobs, tickets
- Deposit plus balance — services, bookings, custom work
- Instalments — high-ticket packages and courses
- Subscription — memberships, retainers, ongoing access
- Pay what you want — donations and community support
Designing an online checkout that does not lose the sale
People abandon checkouts for boring reasons, and the same handful account for most of it: an unexpected cost appearing at the end, a form that suddenly asks for far more than expected, a page that does not feel safe, or a mobile layout that fights the thumb.
Fix them in order. Show the full total, including any delivery or fees, before the card field. Ask only for what fulfilment requires — a digital product does not need a postal address. Keep the payment on the same visual page rather than bouncing through unfamiliar screens. And make the button say what it does: pay 40 pounds, not submit.
One more thing that reliably helps: a visible refund or contact route on the checkout itself. It seems counterintuitive to mention refunds while asking for money, but it is exactly the moment a hesitant buyer needs reassurance that a mistake is fixable.
Refunds, chargebacks and disputes
Write a refund policy before you need one, publish it where buyers see it, and follow it without argument. A policy you apply consistently is worth more than a generous one you apply moodily, because customers can only trust the version they can predict.
Refund quickly when it is clearly right. The cost of a small refund is almost always lower than the cost of a public complaint or a dispute. Note that the processing fee on the original sale is often not returned to you, so a refunded sale can leave you slightly down — build that into your policy rather than resenting it later.
Chargebacks are different and worse. The customer goes to their bank instead of to you, the money is pulled, and a fee usually applies regardless of outcome. Prevent them with recognisable statement names, clear delivery timelines, prompt replies and an obvious refund route. If one arrives, respond with evidence: the order record, the delivery proof, the message history.
Security and what you are responsible for
The safest architecture is the one where card details never touch you. When you use a hosted checkout or an embedded field from a reputable processor, the sensitive data goes straight to them, and your compliance burden shrinks to something a small business can actually carry.
Your responsibilities are still real, though narrower. Serve pages over HTTPS. Use strong, unique passwords and two-factor authentication on your processor and your form tool — account takeover is a far more common attack on small sellers than card fraud. Limit who on your team can issue refunds. Never accept card details by email or message, no matter how insistent the customer is.
Turn on the fraud tools your processor provides rather than building your own. Address checks, card verification codes, velocity limits and the extra authentication step required in many regions cost you very little friction and remove a large share of fraudulent attempts.
What you need in place before the first payment
None of this is legal advice, and the details differ by country, but the checklist below is what a processor and a reasonable customer will expect from you. Get these ready before launch and the account verification step takes minutes instead of a fortnight.
Most of it is just writing things down clearly. What you sell, what it costs, what happens after payment, how long delivery takes, how someone gets a refund, and how they reach a human. Ambiguity in any of those becomes a dispute eventually.
Do it once, in plain language, and reuse it on every checkout you build.
- Verified identity and a bank account in the correct name
- A trading name that matches the card statement descriptor
- Clear pricing, including delivery and any unavoidable fees
- Written terms, a refund policy and a privacy note
- A working contact route that you actually monitor
- Automatic receipts sent on every successful payment
- Records of orders and payouts kept for your tax year
Test it, launch it, then watch three numbers
Before you send the link anywhere, run a real payment through it with your own card, on your own phone, on mobile data. Then refund it. You will discover the wrong currency, the missing receipt, the confusing statement name and the broken confirmation page in ten minutes rather than in front of a customer.
Once live, three numbers matter. How many people open the checkout. How many start paying. How many succeed. A weak first number is a traffic and offer problem; a weak second is a price and trust problem; a weak third is usually a technical or card-failure problem worth investigating in the processor's logs.
Improve one at a time and give each change a couple of weeks. Payments are the part of the funnel where small percentage gains turn into real money, because you are working on people who already decided to buy.
If you want the link, the checkout form and the record of who paid to live in one place, you can set that up free at onesol.io and start taking payments without building a website at all.