Phesky brand emerald P iconPhesky

Website payments

How to Accept Online Payments on Your Website Without Building an Online Shop

By Phesky

You can accept online payments on your website without building an online shop. For many service businesses, a 'Pay now' button that opens a payment link, or a checkout embedded on a single page, does everything a full shop would, with a fraction of the set-up and upkeep.

This guide explains the lightweight options, how they compare with a full e-commerce store, and what to think about for mobile checkout, security and customer information. It also explains exactly what Phesky's link and embed features do, and what they do not.

Why you may not need a full online shop

An online shop is built around products: a catalogue, a basket, stock levels, shipping rules and order management. That makes sense if you sell many physical items. It is often unnecessary if you sell a handful of services, take deposits, accept bookings or have a few fixed-price packages.

In those cases, what visitors really need is a clear description of what they are buying and a simple way to pay for it. Everything else is work you have to build, test and keep up to date.

Lightweight ways to take payments on a website

There are three common approaches, and you can mix them.

Website payment links

A payment link is a web address for a checkout page with a set amount. You can add it to any page as an ordinary link, so it works with almost every website builder.

Website payment buttons

A payment button is simply a styled link. Most website builders let you add a button and point it at a URL, so you can create a 'Pay deposit' or 'Book and pay' button without code.

Embedded checkout

An embedded checkout shows the payment form inside your page, usually through an iframe, so visitors do not leave your site to pay. It needs a page where you can paste HTML, which most builders support through an 'embed' or 'custom code' block.

Payment pages versus full online shops

A payment page sells one thing at one price. It is quick to create, easy for customers to understand and simple to share elsewhere, such as in emails or on social media. The trade-off is that customers cannot combine several items in a basket, and there is no built-in stock or delivery handling.

A full shop handles complex orders, product variations and shipping, but costs more time and often more money to run. A sensible path for many small businesses is to start with payment pages and move to a shop only when the number of products makes it worthwhile.

Mobile checkout matters most

Many visitors will arrive on a phone, often from social media. Make sure your payment button is easy to tap, the price is visible before they click, and checkout works without typing long card numbers on a small screen.

Mobile wallets help here: with Apple Pay or Google Pay the customer confirms with a face scan, fingerprint or passcode. Test your payment page yourself on both an iPhone and an Android phone before sharing it.

Payment security and customer information

The safest approach for a small business is to never handle card details at all. A hosted or embedded checkout from an established payment provider means card information is entered into the provider's systems, not your website, which keeps it out of your hands and your hosting.

Make sure your website uses HTTPS, keep your website builder and any plugins updated, and only collect the personal information you need. If you collect names, emails or addresses, the UK GDPR applies; the Information Commissioner's Office publishes practical guidance for small businesses.

Be clear on your page about what the customer is paying for, your refund policy and how to contact you. Clear information builds trust and reduces disputes.

Website integration considerations

Check that your website builder allows external links on buttons and, for embedded checkout, custom HTML or iframe blocks. Some builders restrict these on free plans.

Wallet payments in an iframe need the right permission. The embed code should include an allow attribute for payments, and some browsers still limit wallets inside frames, so always offer a plain link as a fallback and test on real devices.

Finally, decide how you will confirm each payment and follow up. Your payment dashboard should be the source of truth, not an email from the customer.

A simple setup example

Imagine a dog groomer in Leeds with a five-page website made on a popular website builder. She offers three fixed-price packages and wants customers to pay a £15 deposit when booking.

She creates one payment link per package deposit, each with a clear name such as 'Full groom deposit, small dog'. On her services page she adds a 'Pay deposit' button under each package and points it at the matching link. On her booking page she pastes the embed code for her most popular package so visitors can pay without leaving the site. She then tests every button on her own iPhone and her partner's Android phone, checks that each test shows up correctly in her dashboard, and refunds the test payments.

The whole job takes an afternoon rather than the weeks a full shop might take, and she can change prices by creating new links without touching the rest of her site.

Writing a payment page customers trust

Visitors decide quickly whether to pay. Put the price and exactly what it covers right next to the button, avoid surprises such as extra charges that appear later, and use the same business name on your website and your checkout so customers recognise it.

Add short answers to the questions people ask before paying: when the service will happen, what happens if they need to cancel, and how they can contact you. A real email address or phone number and a visible refund policy do more for trust than any badge or logo.

After payment, tell customers what happens next. A confirmation message from you, sent once the payment shows as successful in your dashboard, closes the loop and reduces anxious follow-up emails.

When a full shop does make sense

Payment pages stop being enough when customers regularly want to buy several items at once, when you need to track stock across many products, or when delivery costs vary by location and weight. At that point a dedicated e-commerce platform will save you time.

Even then, payment links remain useful alongside a shop for custom quotes, deposits and one-off orders that do not fit the catalogue.

How Phesky's payment links and website embed work

In Phesky you create a payment link with an amount and an optional product name, description and image. You can paste that link behind any button on your site, share it by message or email, or show it as a QR code.

From the Website Embed Code option in settings, Phesky also gives you an iframe snippet for a payment link. Paste it into an HTML or embed block on your page and visitors can pay without leaving your site, where their browser supports wallet payments inside the frame. Phesky does not provide website-builder plugins, baskets, stock control or shipping.

Phesky uses Stripe Connect direct charges. Each payment is made on the merchant's own connected Stripe account, so the money belongs to that account and is paid out by Stripe under the merchant's Stripe terms. Phesky does not hold, pool or pay out merchant funds; it only receives its application fee.

Phesky's application fee is £0.16 on a successful payment below £30 and 0.60% on a payment of £30 or more. That is Phesky's share only: Stripe's processing fees apply separately under your Stripe terms, so add both together to work out what a sale really costs. The Phesky pricing page shows worked examples.

Phesky checkout supports Apple Pay and Google Pay only, with no form for typing in card numbers. A wallet button appears only when the customer's device, browser and wallet set-up support it and Stripe confirms the payment method is available. Some in-app browsers inside messaging and social apps restrict wallets, so customers may need to open the link in Safari or Chrome.

Conclusion

If you sell services, deposits or a few fixed-price items, you probably do not need an online shop to take payments on your website. A payment button or embedded checkout is quicker to set up, easier to maintain and simpler for customers. Start with one payment page, test it on your own phone, and add more only as you need them. You can create a free Phesky account to try it.

Frequently asked questions

Can I take payments on my website without an online shop?

Yes. A payment link on a button, or an embedded checkout, lets visitors pay a set amount without a basket, stock system or shop platform.

Does Phesky have a website plugin?

Phesky does not offer platform plugins. It provides a payment link you can put behind any button, and an embed code (an iframe) for a payment link that you can paste into a page.

Will my website handle card details?

No. Checkout is hosted by Stripe through Phesky, so card details are not entered into or stored on your website.