How to accept payments online: a guide for European small businesses
By the Pazl teamPublished
How to accept payments online as a small business: payment links, checkout, Stripe vs Mollie vs PayPal, chat payments, EU rules and a one-week launch plan.
Most small businesses in Europe ask the same question at the same moment: an invoice is overdue, a customer wants to pay by card, or a shop needs a checkout. The short answer to how to accept payments online is that you have five realistic options: payment links and invoices, a hosted checkout from a provider such as Stripe, PayPal, Mollie or Adyen, an embedded checkout on your own site, payments inside a chatbot or Telegram Mini App, and subscriptions or deposits. Which one is right depends on how you sell, how often, and what has to happen after the money arrives.
This guide compares the options by effort, fees and fit, covers what EU law expects from you, shows how a payment should flow into your bookkeeping and CRM, and ends with a one-week launch plan. We build checkouts, ordering apps and chatbots with payments at Pazl.
How to accept payments online: the five options
Before choosing a payment gateway for small business use, decide which shape of payment you need.
Payment links and invoices
The simplest way to accept payments online small business owners can set up in an afternoon: create a link in the provider's dashboard, send it by email, WhatsApp or SMS, and the customer pays by card, SEPA transfer or a local method. It suits consultants, tradespeople, one-off orders and deposits. The drawback is that every link is manual work, and nothing updates your records unless you connect it.
Hosted checkout
The provider hosts the payment page. Your site or app sends the customer to it with the amount and a return address; the provider handles card entry, 3-D Secure, wallets such as Apple Pay and Google Pay, and local methods like iDEAL, Bancontact or SEPA Direct Debit. It is the default for most small shops and service sites because PCI compliance stays with the provider.
Embedded checkout on your own site
Here the card form lives inside your page, styled to match, and the provider's script tokenises the card so raw numbers never touch your server. This is how you accept card payments on website flows that need to feel seamless: a booking that confirms without a redirect, a multi-step order, or a portal that reuses saved cards. It costs more and needs a developer, but conversion is usually higher on mobile.
Payments inside a chatbot or Telegram Mini App
If your customers already write to you on WhatsApp or Telegram, the payment can happen there. A chatbot collects the order and sends a payment link or an in-chat card form; a Telegram Mini App can show a full catalogue, basket and checkout without leaving the messenger (we wrote a separate piece on Telegram Mini Apps for business). This removes the biggest drop-off point, the jump from chat to website, and suits restaurants, delivery and repeat orders. Our chatbots with payments start from €2,000.
Subscriptions and deposits
Memberships, retainers, rental deposits and instalments are a different problem: a card has to be stored and charged later. Every major provider supports it, but you need the customer's consent text, a reminder before renewal, a way to update card details and a rule for failed charges; use the provider's subscription objects rather than building your own.
Comparing online payment methods: effort, fees and fit
Provider fees change and depend on your country, the card type (EEA or international) and the payment method, so we do not quote percentages here. Look at the pattern instead, then check the provider's current pricing page for your country before you decide.
| Option | Setup effort | How you pay for it | Best for |
|---|---|---|---|
| Payment link or invoice | Hours, no developer | Provider fee per transaction only | Consultants, trades, one-off orders, deposits |
| Hosted checkout | Days; a developer connects it | Provider fee per transaction; bank methods such as SEPA are usually cheaper than cards | Shops, service sites, bookings |
| Embedded checkout | 1–3 weeks of development | Same provider fees, plus the build | Booking flows, portals, saved cards, higher-volume shops |
| Chatbot or Mini App payment | 2–4 weeks including the bot | Provider fees, plus the bot build | Restaurants, delivery, repeat orders, chat-first customers |
| Subscriptions and deposits | Days on top of any option above | Provider fees; some providers charge extra for billing tools | Memberships, retainers, rentals, instalments |
Where the fee is written: Stripe, Mollie, PayPal and Adyen all publish their rates on their own pricing pages. When you compare, look at three lines — domestic cards, international cards and the bank method your customers use most — not at the headline rate.
The build cost is the part providers do not print. A hosted checkout wired into a website is a few days of work. A full web app with accounts, payments and admin starts from €2,500 with us; a restaurant ordering app with menu, payment and kitchen screen from €4,750. If you are planning a full online shop rather than a checkout on an existing site, see our ecommerce website development page.
Choosing a payment gateway for small business
Stripe for small business is the usual first choice in most of the EU: good documentation, one contract, cards, wallets and SEPA, subscriptions built in. Mollie is popular in the Benelux and Germany for its local methods and simple pricing. PayPal is worth adding as a second button because some customers only trust it, but not as your only gateway. Adyen targets larger volumes and unified in-store and online payments.
| Provider | Strong for | Worth checking |
|---|---|---|
| Stripe | One account for cards, wallets and many local methods; subscriptions and invoicing built in; detailed developer documentation | Whether every local method your customers use is available in your country |
| Mollie | Local European methods, simple set-up, popular in the Benelux and Germany | Subscription and marketplace features against your needs |
| PayPal | Customers who trust PayPal more than a card form; a good second button | Not as your only gateway; check dispute handling |
| Adyen | Larger volumes, one platform for in-store terminals and online payments | Minimum volumes and onboarding requirements for a small business |
Two checks matter more than the headline fee:
- Local methods for your customers. A Dutch shop without iDEAL or a German one without SEPA and PayPal loses orders it never sees.
- Webhooks and an API you can read. The provider must be able to tell your system "this payment succeeded" automatically; otherwise you are back to checking a dashboard by hand.
The provider is only half the answer to how to accept payments online; the connection to your own systems decides whether it saves time.
What you need legally in the EU
Accepting money online in Europe brings obligations that are easy to meet if you plan for them.
- Strong Customer Authentication (SCA) and 3-D Secure. The EU's second Payment Services Directive (PSD2, Directive (EU) 2015/2366) requires two-factor authentication for most online card payments. The big providers' checkouts handle 3-D Secure 2 automatically; a home-made card form does not.
- Receipts and invoices. The customer must receive a confirmation with the items, the amount, VAT and your company details; business customers usually still need a proper invoice with your VAT number. Invoice rules differ by country — check yours with your accountant.
- VAT. Since 1 July 2021, distance sales of goods and certain services to EU consumers above €10,000 a year across the EU are taxed at the customer's country rate and can be declared through the One-Stop Shop (OSS, introduced by Council Directive (EU) 2017/2455). Your checkout must know the customer's country.
- Refund and cancellation policy. Under the Consumer Rights Directive (2011/83/EU), consumers have a 14-day withdrawal right on most distance purchases, with exceptions such as perishable goods or services already fully provided. Publish the policy, link it from the checkout, and make refunds a button in your admin, not a manual bank transfer.
- Data protection. Card data stays with the provider; the customer's name, address and order history are yours to protect under the GDPR (Regulation (EU) 2016/679).
This is a practical summary, not legal advice. For your specific case, check with your accountant or lawyer.
Connecting payments to bookkeeping and CRM
A payment that only exists in the provider's dashboard is a payment someone has to copy by hand at month end. The moment you accept payments online at any volume, the integration is what saves time.
The pattern we build is simple. The provider sends a webhook when a payment succeeds, fails or is refunded. A small service on your side records it against the order, marks the invoice paid in your accounting tool and updates the customer record in your CRM. Payouts are reconciled separately, because one payout bundles many payments minus fees, and your accountant needs the fee line.
If you run an online booking system, the same webhook confirms the slot; if you run a loyalty programme, it adds points. Our project Caffeine, a coffee-shop ordering app, shows this end to end: order, pay in the app, points credited, the till sees the order.
A client area that shows invoices and a "Pay" button is the natural next step once payments are wired in; we explain when that is worth it in what a customer portal is and when you need one.
Common mistakes when you accept payments online
Most of what goes wrong when a business works out how to accept payments online is avoidable:
- Building your own card form. It breaks SCA, puts you in PCI scope and saves nothing.
- Only offering cards. Local bank methods and wallets often convert better and cost less.
- No test of the failure paths. Declined card, closed tab, double click on Pay: each needs a defined outcome.
- Relying on the "success" redirect instead of webhooks. The customer's browser can drop before the redirect; the webhook is the truth.
- Not planning for disputes. Keep delivery proof and correspondence per order so a chargeback can be answered quickly.
How to accept payments online in a week: step by step
Here is how to accept payments online in seven working days if you start on a Monday.
- Day 1 — decide the shape. Links, hosted checkout, embedded, chat or subscription. Pick one provider and one backup method (usually PayPal or SEPA).
- Day 1–2 — open the account. Company registration, IBAN, the director's ID, and a site with terms, privacy and refund pages. Verification can take a day or two, so start it first.
- Day 2–3 — connect the checkout. Test mode, products and prices, VAT rules, local methods switched on, branded receipt emails.
- Day 3–4 — wire the webhooks. Succeeded, failed, refunded and disputed events writing to your order table, accounting tool and CRM.
- Day 5 — test the ugly cases. Test cards for decline, 3-D Secure challenge and insufficient funds; refund a test order; check the payout report.
- Day 6 — go live with a small group. Switch to live keys, take a few real payments from friendly customers and reconcile the first payout.
- Day 7 — announce. Add the pay button or link to invoices, the website, the chatbot and your email signature.
If you want us to do the technical days, tell us what you sell and which tools you already use, and we will scope it with you.
Frequently asked questions
What is the cheapest way to accept payments online as a small business?
For a low number of transactions, payment links with SEPA transfer or local bank methods are the cheapest, because fixed fees are low and there is no build cost. As volume grows, a hosted checkout with local methods usually costs less per order.
Do I need a website to accept card payments?
No. Payment links, invoices with a pay button and chatbot payments work without a website. You do need published terms, a refund policy and company details, often on a one-page site.
Is Stripe good for a small business in Europe?
Yes for most cases: one account covers cards, wallets, SEPA and many local methods, with subscriptions and invoicing included. Compare Mollie if you sell mainly in the Benelux or Germany.
Can customers pay inside WhatsApp or Telegram?
Yes. A chatbot can send a payment link or open an in-chat form, and a Telegram Mini App can run a full checkout inside the messenger. It works well for restaurants, delivery and repeat orders where the customer already writes to you.
Do I need a merchant account to accept payments online?
Not a separate one. Providers such as Stripe, Mollie and PayPal act as the payment facilitator: you open one account with them, pass their verification, and they handle the card acquiring. A traditional merchant account from a bank makes sense mainly at high volumes.
How quickly do I get the money?
It depends on the provider, your country and your account history. Payouts usually arrive on a rolling schedule after a short delay, and new accounts sometimes start with a longer one. Check the payout schedule in the provider's dashboard before you promise suppliers a date.
More about the service: Ecommerce website development