You do not need an ecommerce website to take secure card or online payments.
A business can take payments through:
- hosted payment links;
- QR codes;
- invoice payment links;
- virtual terminals;
- telephone and MOTO payments;
- Tap to Pay on a compatible smartphone;
- physical card terminals;
- Open Banking or Pay by Bank;
- recurring-payment arrangements;
- marketplaces; and
- payment requests generated through business software.
The important question is not simply:
“How do I take a payment without a website?”
It is:
“Where is the customer, who enters the payment information, is the payment one-off or recurring, and what needs to happen after the customer pays?”
A tradesperson collecting a £200 deposit, an accountant taking invoice payments, a telephone sales team and a software platform generating thousands of payment requests all need very different payment setups.
This guide explains the main ways UK businesses can accept payments without building a conventional ecommerce website and how to decide which option fits the payment journey.
Which payment method do you need?
| Customer situation | Payment option to consider |
| Customer is remote and can enter their own details |
Payment link or hosted payment page |
| Customer is on the telephone and gives card details to staff |
Approved virtual terminal / MOTO setup |
| Customer is standing in front of you |
Tap to Pay or physical card terminal |
| Customer is paying an invoice |
Invoice payment link, card payment or Pay by Bank |
| Customer is paying regularly |
Recurring card, Direct Debit or another suitable recurring-payment model |
| You sell through Instagram, WhatsApp, SMS or email |
Send a secure hosted payment link |
| Your CRM, booking system or software should create payment requests automatically |
Integrated or embedded payment setup |
Payment links: often the simplest way to get paid without a website
For many businesses, a hosted payment link is the most straightforward way to accept an online payment without operating an ecommerce checkout.
The business creates a secure payment request through its payment provider and sends the customer a link.
The customer opens the link and enters their own payment information on the provider's hosted payment page.
The link might be sent through:
- email;
- SMS;
- WhatsApp or another messaging service;
- an invoice;
- a CRM;
- a booking confirmation;
- a social-media message;
- a printed QR code; or
- another customer communication.
Major payment providers now explicitly offer hosted payment-link products that do not require the merchant to operate its own website.
For the detailed payment-link journey, read our Pay by Link guide .
How does a payment link work?
A simple journey can look like this:
- The merchant creates a payment request.
- The amount and reference are added.
- The provider generates a secure URL.
- The merchant sends the URL to the customer.
- The customer opens the hosted payment page.
- The customer enters their own payment details.
- The payment provider processes the transaction.
- The merchant receives the payment status.
- The funds are later settled according to the provider arrangement.
Depending on the provider, the payment request may also carry information such as:
- customer name;
- invoice number;
- booking number;
- order reference;
- deposit amount;
- currency;
- product or service description; and
- internal account reference.
This becomes particularly useful when payments need to be matched back to invoices, bookings or customer accounts.
The customer should enter their own details where possible
A payment link and a virtual terminal may both be used for remote payments, but they create different payment journeys.
Payment link: the customer enters their own payment information into a hosted online checkout.
Virtual terminal: the merchant's employee manually enters the customer's card information into the provider's browser-based terminal.
Where a customer can complete a secure online payment themselves, businesses should consider whether that creates a better authentication, card-data and operational journey than staff manually handling card details.
Taking payments by QR code
A QR code can provide another route into a hosted payment page.
The customer scans the code with their phone and is taken to the provider's payment journey.
QR codes can be useful on:
- printed invoices;
- letters;
- quotes;
- brochures;
- posters;
- event materials;
- reception desks;
- market stalls;
- restaurant tables;
- donation materials; and
- other physical customer communications.
A QR code should not be confused with the payment method itself.
It is normally simply a way of directing the customer into the underlying hosted payment experience.
The merchant should still understand:
- which payment provider processes the transaction;
- which payment methods are available;
- how the transaction is authenticated;
- how payments are identified;
- how refunds work; and
- how settlement is reported.
Taking card payments over the telephone
A business may need to take payment while speaking to the customer over the telephone.
There are two very different approaches.
Send the customer a payment link
The customer remains on the telephone but receives a secure payment link and enters their own details.
This can reduce the amount of card information handled directly by employees and may allow an ecommerce-style authentication journey.
Use a virtual terminal
The customer provides their card information to the business and an employee manually enters it into an approved virtual terminal.
This is generally treated as a Mail Order / Telephone Order, or MOTO, payment journey.
Read our Manual Card Payments guide and MOTO Merchant Account guide for the detailed requirements.
What is a virtual terminal?
A virtual terminal is normally a browser-based payment interface supplied by an acquirer, processor or payment service provider.
The merchant's employee logs into the system and manually enters the customer's card information.
It can be useful for:
- telephone orders;
- remote invoice payments;
- professional services;
- telephone bookings;
- call centres;
- B2B account payments;
- occasional remote transactions; and
- other genuine MOTO use cases.
However, the fact that a provider gives a business access to a virtual terminal does not mean every transaction should be manually processed through it.
The provider may assess:
- why MOTO is required;
- what percentage of turnover will be telephone based;
- transaction values;
- business sector;
- customer countries;
- fraud and chargeback history;
- fulfilment;
- staff access;
- card-data controls; and
- whether customer-led alternatives such as payment links are available.
Taking face-to-face payments without a website
If the customer is physically present, a website may have no role in the payment at all.
The business could use:
- a countertop card terminal;
- a portable terminal;
- a mobile card machine;
- Tap to Pay on a compatible smartphone; or
- another approved point-of-sale payment device.
The most suitable option depends on how and where the business trades.
Tap to Pay: using a phone as the payment acceptance device
Tap to Pay technology can allow a compatible smartphone to accept contactless cards and digital wallets without a separate card reader.
This can be particularly useful for:
- mobile trades;
- market sellers;
- events;
- delivery businesses;
- mobile services;
- occasional face-to-face payments;
- queue busting; and
- businesses that do not want a conventional terminal for every employee.
The phone still needs a supported payment application and compatible payment-provider arrangement.
See our Tap to Pay UK guide for more detail.
Taking invoice payments without a website
Businesses issuing invoices do not need to build an ecommerce store simply to let customers pay online.
The payment option can instead sit directly within:
- the invoice;
- invoice email;
- accounting software;
- customer portal;
- CRM;
- ERP system;
- payment reminder; or
- accounts-receivable workflow.
The customer could then pay using cards or another supported method such as Pay by Bank.
We cover this in more detail in our Invoice Payment Processing guide .
Need to take payments without an ecommerce website?
Tell us what your business sells, where your customers are and how you want them to pay.
You do not need an ecommerce website for every payment setup. Merchant Advice Service can help you understand whether you need payment links, MOTO, terminals, Open Banking or a more integrated payment solution before identifying providers that may be suitable.
Find suitable payment providers
Open Banking and Pay by Bank without a website
A customer does not necessarily need to use a debit or credit card to make a remote payment.
Open Banking payment initiation can allow a customer to authorise a payment directly from an eligible bank account.
A business might send the customer a payment request containing:
- the amount due;
- customer reference;
- invoice number;
- order number; or
- other payment information.
The customer then authenticates through their bank rather than manually entering card details.
This can be particularly relevant for:
- invoice payments;
- B2B payments;
- professional services;
- higher-value transactions;
- account balances; and
- other remote payments traditionally collected by bank transfer.
See our Open Banking guide for the wider payment-initiation model.
Can you take recurring payments without a website?
Potentially, yes.
A website is not necessarily required to establish a recurring-payment relationship.
Depending on the provider and business model, recurring collection could use:
- recurring card payments;
- Direct Debit;
- a subscription-payment product;
- a payment link that establishes a stored credential;
- Variable Recurring Payments where appropriate and supported; or
- another provider-supported recurring arrangement.
The customer still needs to understand what they are agreeing to.
The business should establish:
- how consent is obtained;
- amount and frequency;
- how customers cancel;
- how failed payments are managed;
- what happens when payment details change;
- refund arrangements; and
- how recurring transactions are reported and reconciled.
Taking payments through Instagram, WhatsApp, Facebook or social media
Social media and messaging services can be useful sales and communication channels, but they should not automatically be treated as the payment processor.
A cleaner model is often:
customer enquires through social or messaging → business confirms the order → secure hosted payment request is sent → customer completes payment with the payment provider
The payment request could be shared through:
- Instagram direct message;
- WhatsApp;
- Facebook Messenger;
- SMS;
- email; or
- another approved communication channel.
The customer is then taken away from the conversation and into the provider-controlled payment environment.
Businesses should avoid asking customers to send complete card details back through ordinary email, SMS or social-media messages.
What about selling through Amazon, eBay, Etsy or another marketplace?
Online marketplaces provide another way to sell without operating a standalone ecommerce website.
However, this is a different model from obtaining your own merchant account or payment gateway.
With a marketplace, the platform normally controls significant parts of:
- customer checkout;
- payment acceptance;
- seller onboarding;
- payouts;
- refund processes;
- fees;
- disputes; and
- platform rules.
A marketplace can therefore be appropriate for businesses that actually want to trade through that marketplace.
It is not necessarily a substitute for a direct payment setup if the business acquires customers independently and simply needs a secure way to collect payment.
Do you need a merchant account if you do not have a website?
Not necessarily as a separately contracted product.
Different payment-provider models package payment acceptance differently.
Some providers combine:
- payment gateway;
- acquiring;
- hosted checkout;
- settlement;
- payment links; and
- reporting
within one PSP relationship.
Other merchants may have:
- a separate merchant acquirer;
- a separate payment gateway;
- a virtual terminal;
- payment-link functionality; and
- other payment software.
The important question is therefore not whether the product is marketed as a “merchant account”.
It is who is:
- underwriting the business;
- acquiring the card transaction;
- providing the payment technology;
- settling the money;
- handling refunds and disputes; and
- supporting the merchant if something goes wrong.
No website does not mean no underwriting
A payment provider still needs to understand who it is providing payment services to.
The provider may assess:
- business identity;
- directors and owners;
- business activity;
- products and services;
- where the business trades;
- customer locations;
- transaction values;
- monthly processing volume;
- fulfilment;
- refund policy;
- chargeback exposure;
- financial position;
- previous payment-provider history; and
- how customers are acquired and sold to.
A hosted payment page removes the need for the merchant to build its own ecommerce checkout. It does not remove the provider's responsibility to understand the business.
What if the provider asks for a website?
This is where businesses without conventional websites can sometimes encounter friction during underwriting.
A provider may use a website to understand:
- what is being sold;
- prices;
- business identity;
- customer terms;
- refund policy;
- delivery or fulfilment;
- contact information; and
- how customers interact with the business.
If there is no website, the merchant may need to demonstrate this information another way.
Depending on the provider and business, that could include:
- invoices;
- contracts;
- price lists;
- brochures;
- social-media business pages;
- booking-platform listings;
- customer terms;
- refund policies;
- proof of trading;
- existing merchant statements;
- supplier information; and
- a clear explanation of the customer journey.
Different providers have different onboarding requirements, so not having a website should be disclosed clearly rather than attempting to make the application appear to be conventional ecommerce.
No website does not mean no consumer-law obligations
UK businesses selling remotely can still have obligations even where they do not operate a conventional ecommerce website.
Government guidance on distance selling covers sales made through channels including phone and text as well as online transactions.
Depending on the transaction, businesses may need to provide customers with information such as:
- business name;
- contact details;
- business address;
- description of the goods or services;
- price including applicable taxes;
- how payment can be made;
- delivery arrangements;
- delivery costs;
- contract information; and
- cancellation information where relevant.
Businesses should therefore avoid thinking:
“We only sell through WhatsApp, so ecommerce or distance-selling rules do not apply.”
The sales channel and legal nature of the transaction matter more than whether the merchant has built a conventional website.
PCI DSS when taking payments without a website
Not having a website does not remove PCI DSS responsibilities.
The relevant PCI DSS environment depends on how payment-card information is handled.
Customer enters their own card details
A properly hosted payment page can reduce the amount of payment-card data handled directly by the merchant.
However, the merchant still needs to confirm its actual PCI DSS responsibilities with its acquirer or payment provider.
Employee enters the customer's card details
A virtual terminal creates a different card-data environment because the merchant receives the card information and manually enters it.
The PCI Security Standards Council has a specific SAQ C-VT eligibility route for certain merchant environments using an internet-based virtual terminal supplied by a PCI DSS validated service provider.
Eligibility depends on the complete environment, not simply on the fact that the product is called a virtual terminal.
Strong Customer Authentication and payments without a website
A payment link is still an electronic online payment journey.
Strong Customer Authentication requirements can therefore apply depending on the transaction and any relevant exemption.
The payment provider normally manages the technical authentication journey, including 3D Secure where appropriate.
This creates an important distinction between:
- a customer completing an ecommerce-style hosted checkout; and
- a genuine MOTO transaction where staff manually process a telephone or mail-order payment.
A business should not classify an ecommerce transaction as MOTO simply to avoid authentication requirements.
Taking deposits without a website
Payment links can be particularly useful for businesses that need a deposit rather than full ecommerce checkout.
Examples include:
- builders and trades;
- kitchen and bathroom companies;
- private clinics;
- beauty and aesthetics;
- restaurants;
- events;
- holiday businesses;
- wedding suppliers;
- professional services;
- training providers;
- vehicle sales and repairs; and
- other appointment or future-delivery businesses.
The provider will still want to understand when the final product or service will be delivered.
Taking a payment by link does not remove future-delivery or chargeback exposure.
What happens when manual payment links stop being enough?
A small business may begin by creating a few links manually each week.
As payment volume grows, the operational questions change.
The business may need:
- automatic payment-link generation;
- unique customer references;
- invoice references;
- booking references;
- CRM integration;
- accounting integration;
- ERP integration;
- API access;
- webhooks;
- automated reminders;
- multiple users;
- role permissions;
- multiple merchant IDs;
- multiple currencies;
- automated refunds;
- transaction-status updates; and
- payment reconciliation.
At that point, the business no longer simply needs “a way to send a payment link”.
It needs a payment architecture.
Integrating payment requests with business software
A business can accept online payments without a public ecommerce website while still having a sophisticated payment integration behind the scenes.
For example:
customer booked in CRM → deposit request created automatically → payment link sent → customer pays → booking updated → payment reconciled
Or:
invoice generated in ERP → hosted payment request created → customer pays → invoice marked paid → settlement matched automatically
The integration may involve:
- CRM;
- booking software;
- ERP;
- accounting platforms;
- case-management systems;
- practice-management software;
- property software;
- field-service systems;
- invoicing software; or
- bespoke business applications.
For the wider architecture, see our Integrated Payments guide .
Using an API to create payment requests
Higher-volume businesses may want their software to create payment requests automatically.
A payment API can potentially allow the business system to:
- create a payment;
- set the amount;
- attach references;
- generate a hosted checkout;
- retrieve payment status;
- process refunds;
- receive webhook notifications; and
- update internal systems.
Businesses planning custom technical integration can read our Payment API Integration guide .
A business can have embedded payments without having an ecommerce website
This becomes especially important for software businesses.
An invoicing platform, booking system, CRM, vertical SaaS product or business-management platform could allow its users to send payment requests directly from the software.
The end merchant may never need to build a conventional ecommerce checkout.
The payment functionality is instead embedded into the software workflow.
Software companies building this model should read our Embedded Payments guide .
Hosted payments vs embedded payments
These terms solve different problems.
Hosted payment
The payment provider hosts the checkout environment.
The merchant sends the customer to that payment page.
This can work very well for businesses that want to accept online payments without building a checkout themselves.
Embedded payment
Payment functionality is integrated into a software product or business workflow.
The user may create payment requests, view payment status, issue refunds or manage payment data without leaving the software platform.
The actual card-entry page may still be hosted by a payment provider behind the scenes.
“Hosted” and “embedded” therefore describe different parts of the payment architecture and can exist together.
How much does it cost to take payments without a website?
There is no standard fee simply because a merchant does not have a website.
Costs can depend on:
- payment method;
- card type;
- online vs MOTO;
- merchant sector;
- monthly processing volume;
- average transaction value;
- provider pricing model;
- gateway fees;
- fixed transaction charges;
- commercial cards;
- international cards;
- currency conversion;
- refund charges;
- chargeback fees;
- terminal charges where applicable; and
- integration costs.
A provider advertising “free payment links” may still charge the normal processing fee on every transaction.
Businesses should therefore compare the total cost of the payment setup rather than the cost of generating the URL itself.
What should businesses compare between providers?
Business acceptance
Will the underlying provider actually accept your sector and business model?
Payment journey
Do you need the customer to enter their own information, or do staff genuinely need a MOTO facility?
Payment links
Can links contain fixed amounts, references and expiry rules?
QR codes
Can payment requests be converted into QR codes where required?
Virtual terminal
Is MOTO supported and approved for the proportion of payments you expect to process?
Payment methods
Do you need cards, wallets, Open Banking, Direct Debit or other alternatives?
Recurring payments
Can the provider support your required subscription or repeat-payment arrangement?
Integrations
Can payment requests connect with your CRM, booking software, accounting system or ERP?
Reporting
Can every transaction be matched back to the relevant customer, invoice, order or booking?
Settlement
When does the money reach your bank account?
Refunds
Can full and partial refunds be handled easily?
Security and authentication
How are PCI DSS, SCA and 3D Secure handled for the relevant payment channels?
Pricing
What is the complete cost rather than simply the advertised transaction rate?
You may not need a website. You do need the right payment journey.
Start with where the customer is, who should enter the payment information and what needs to happen after the transaction.
Merchant Advice Service can help you understand whether your business needs a payment link, virtual terminal, card terminal, Open Banking or a more integrated payment setup before identifying providers that may be suitable.
Find suitable payment providers Explore merchant account providers
How Merchant Advice Service helps businesses without a website
Merchant Advice Service helps businesses understand their payment requirements before identifying payment providers that may be suitable.
For businesses without a conventional ecommerce website, that can include:
- payment links;
- hosted payment pages;
- QR-code payments;
- virtual terminals;
- MOTO;
- Tap to Pay;
- card machines;
- invoice payments;
- Open Banking;
- recurring payments;
- payment gateways;
- merchant acquiring;
- CRM integration;
- booking-system integration;
- accounting and ERP integration;
- payment APIs;
- settlement;
- reporting; and
- reconciliation.
For software businesses wanting to offer payment acceptance to their own users, the requirement can move beyond ordinary merchant processing into an embedded-payment model.
Read our Embedded Payments guide for that use case.
Sources & References
- Stripe – Payment Links – current provider documentation showing that businesses can create hosted payment pages and accept payments without operating a website.
- PayPal UK – Payment Links and Buttons – current information on hosted payment links, QR codes and website-optional payment acceptance.
- Square UK – Payment Links – current guidance on hosted payment pages, payment links, QR codes and no-website payment acceptance.
- Mastercard – Tap on Phone – current information on using compatible NFC-enabled smartphones to accept contactless cards and wallets without separate terminal hardware.
- GOV.UK – Online and Distance Selling – UK government guidance covering information businesses must provide when selling remotely, including sales by phone or text.
- Financial Conduct Authority – Strong Customer Authentication – guidance on authentication requirements for electronic payment transactions.
- PCI Security Standards Council – Virtual Payment Terminals and SAQ C-VT – PCI DSS guidance covering merchant environments where staff manually enter cardholder data into hosted virtual terminals.
- Merchant Advice Service – Pay by Link for Merchants – detailed guidance on hosted payment links, security, integrations and reconciliation.
- Merchant Advice Service – Manual Card Payments – guidance on virtual terminals, MOTO and remote card payments.
- Merchant Advice Service – Invoice Payment Processing – guidance on invoice payments, ERP integration and accounts-receivable automation.
- Merchant Advice Service – Integrated Payments – guidance on connecting payments with ERP, CRM, booking software and other business systems.
- Merchant Advice Service – Embedded Payments – guidance for SaaS, ISVs and platforms building payment acceptance into their software.
- Merchant Advice Service – Editorial & Research Policies
Editorial & Commercial Disclosure
This guide provides general information about taking card and online payments without operating a conventional ecommerce website.
Payment functionality, merchant eligibility, pricing, settlement, authentication and technical requirements vary between payment providers.
Using a hosted payment link or another outsourced payment service does not automatically remove a merchant's PCI DSS, consumer-law or other responsibilities.
Businesses should not use MOTO or virtual-terminal transactions as a way of bypassing ecommerce authentication requirements. The payment channel should accurately reflect how the customer initiated and completed the transaction.
Merchant Advice Service does not process payments or determine merchant-account approval.
MAS is an independent payments information and provider-matching service. MAS may receive a referral fee or commission from some payment providers where a business proceeds following an introduction. Commercial relationships do not determine the factual information or provider-selection principles contained within this guide.
Providers determine their own underwriting, pricing, technical functionality and contractual terms.
Information is provided for general guidance and should not be treated as legal, regulatory, accounting or information-security advice.