How to Accept Credit Cards on Your Website Without an Online Store

On this page 9 sections

1. What Accepting Credit Cards on Your Website Actually Requires
2. Payment Buttons and Payment Links: Fastest to Set Up
3. Hosted Payment Pages: The Default Choice for Most Service Firms
4. Embedded Payment Forms: Your Branding, More Responsibility
5. Invoice Links: When Every Amount Is Different
6. Accept Payments on Wix or Squarespace With Your Own Merchant Account
7. PCI Scope Grows as Card Data Gets Closer to Your Server
8. Fees, Payout Timing and What Underwriters Check
9. Matching the Setup to Your Billing Pattern

Key takeaways

• If your merchant account was approved only for in-person sales, tell your processor before adding a pay button. A sudden shift to online payments can trigger reviews or holds.
• For most service businesses, a hosted payment page works best. It accepts any amount and keeps card entry off your site.
• Embedded forms look more polished, but they make your own web pages part of your security work.
• Flat-rate pricing and a gateway account cost the same at one monthly volume. Find that break-even point from two real quotes before you choose.

You don't need a shopping cart to start accepting credit cards on your website. A service business can take cards through a pay button, a hosted payment page, a form embedded on one of its own pages, or a pay link on each invoice, and none of these requires an online store. Two questions decide which one fits. Do customers pay fixed amounts or variable ones? And how much security work are you willing to own?

Carts are built for product catalogs and shipping rates. Most service firms have neither. An accountant billing for a tax engagement, a roofer collecting a deposit and a home care agency billing a family each week all need the same small thing: a secure page where the customer enters the amount and an invoice number, then types in a card.

What Accepting Credit Cards on Your Website Actually Requires

Every option below sits on the same foundation. You need a merchant account approved for card-not-present sales, meaning sales where the card isn't physically in front of you, plus a payment gateway, the software that carries card data from a web page to the processor. Your website does less than you'd think. It only has to link to the page where the customer enters the card, or display that page.

Here's the rule that catches established businesses off guard. A merchant account opened for a countertop terminal was underwritten for in-person sales, and online and keyed payments carry more fraud and dispute risk than tapped or dipped cards. Adding a pay button changes your risk profile. Tell your processor before you go live, because a sudden run of online payments on an account set up for card-present sales can lead to funding holds and account reviews. Online transactions also usually cost more to process; our breakdown of card-present vs. card-not-present fees explains why.

Payment Buttons and Payment Links: Fastest to Set Up

A payment button is just a link styled to look like a button. Clicking it opens a checkout page run by your payment provider, often with the amount already filled in. That works well when everyone pays the same price: a set consultation fee, say, or a refundable deposit that holds a project start date.

The limits show up fast. Each fixed amount needs its own button, and most button tools leave little room to collect an invoice number or a job address. If your prices change from job to job, you'll end up making a fresh link for every customer, and at that point you're really sending invoices. For using links outside your website, see our guide to payment links for businesses without a checkout.

Hosted Payment Pages: The Default Choice for Most Service Firms

A hosted payment page is a checkout page your gateway runs on its own servers. You pick the fields, typically the amount and an invoice number, add your logo, and put a "Pay Your Invoice" link in your website menu. The customer enters the card on the gateway's page. Your site never touches the card number.

For a brochure site, this is usually the best trade-off. Because customers type in any amount, one page covers every invoice you'll ever send. Setup takes an afternoon. Your security obligations stay small since the gateway handles card entry, and most customers won't mind the brief change in page address when the page carries your logo and business name.

MannyPay sets up payment gateways, including Authorize.net gateway accounts and NMI. When you request a quote, ask whether the hosted page supports custom fields and emailed receipts. Bill repeat customers? Then also ask about saving a card for later charges.

Embedded Payment Forms: Your Branding, More Responsibility

An embedded form puts the card fields directly on your own page, so the customer never leaves your domain. Modern versions usually load those fields from the gateway inside a frame or through a script, which means your server still never stores card numbers.

The catch: your website now delivers the payment experience. A compromised plugin or a malicious script injected into that page could capture card data as the customer types it, so the site itself, along with every plugin and piece of third-party code on the payment page, becomes part of your security picture. Embedded forms suit a SaaS firm or a busy agency with a developer on call and a real reason to want a fully branded checkout. A small plumbing company rarely gets enough from the extra polish to justify the upkeep.

Invoice Links: When Every Amount Is Different

Contractors, staffing agencies and most professional firms bill a different amount every time. For them, the best payment channel may be an email rather than the website. An invoice with a "Pay Now" link that opens a hosted page lets the customer pay the exact amount due with the invoice number already attached. Reconciliation gets much easier.

Many firms run both. The website keeps a general "Make a Payment" page for customers who arrive on their own, while invoices carry direct links. Our comparison of payment links vs. invoices vs. virtual terminals covers when each one fits. Some customers will still call in a card number, and staff can handle those through a virtual terminal opened in any browser. Expect keyed pricing on those calls.

Accept Payments on Wix or Squarespace With Your Own Merchant Account

Wix and Squarespace both offer built-in payment tools, but those tools tie you to the builder's payment partners and pricing, and they're often designed around a store. To use your own merchant account, take the route that works on any builder: create a hosted payment page in your gateway, then add a button or menu item that links to it. No plugin. No custom code. The payment page stays entirely outside your site.

Embedded forms are a different story on these builders, since the gateway's embed code has to run on the page. Check whether your plan allows custom code or embed blocks before you commit.

WordPress Gives You More Routes

Linking to a hosted page works on WordPress exactly the same way. You can also connect a form plugin to your gateway, or set up WooCommerce with a single "pay an invoice" item where the customer enters the amount. WooCommerce is built as a store, so it's more machinery than a pay page needs, though it makes sense if you later plan to sell packages or recurring plans. Whatever you install, keep it updated. Plugins you no longer use should be deleted, since they sit close to your payment page.

PCI Scope Grows as Card Data Gets Closer to Your Server

PCI DSS, the card industry's data security standard, is a set of industry rules enforced through your processor, not a law. It applies to every merchant that accepts cards. Most small merchants confirm compliance each year with a self-assessment questionnaire, and how long that questionnaire runs depends on how card data moves through your systems.

Pay links and hosted pages keep card entry entirely on your provider's systems, as do invoice links that open a hosted page. Those setups generally qualify for the shortest questionnaire. Embedded forms are different: the card fields live inside your web page, so the page itself has to be protected, which can add requirements around scripts and site security. Deepest of all is a form that posts card data to your own server. Few service businesses should build one. Questionnaire eligibility changes as the standard is updated, so confirm with your processor which one fits your setup before you choose.

Two habits matter more than the paperwork. Stop accepting card numbers by email or text, and reply with your payment link instead. And if you bill the same customer repeatedly, store the card with your gateway after getting the customer's written authorization, never in a spreadsheet. Our guide to storing a customer's card on file safely and legally walks through the consent steps.

Some industries need extra care. Home healthcare and staffing agencies should keep care details out of payment descriptions and receipt fields, and confirm their privacy obligations with a compliance advisor. Law firms face state bar rules on where client funds may be deposited, so check with your bar before connecting a pay page to an operating account. Treat this section as general information, not legal advice.

Fees, Payout Timing and What Underwriters Check

Online credit card processing costs fall into two buckets. Flat-rate tools charge one percentage, often plus a per-transaction fee, on every payment. A merchant account with a gateway usually separates processing costs from the gateway's own fees. Payout timing depends on your processor and account terms, so ask when funds land after a batch settles. Large tickets can trigger holds, which is why a contractor collecting a big progress payment should read our guide to avoiding holds on big-ticket card sales before sending the link.

For card-not-present approval, underwriters typically review your website. They look for what you sell, how you price it, how a customer can reach you, and whether refund and privacy policies are posted. A brochure site without a refund policy can slow approval.

Many processors add 3D Secure authentication for online payments, which helps when a cardholder claims a payment was fraudulent. It does nothing for a customer who says the work was never done. That's one of the most common disputes service businesses face, and our guide to chargebacks for services rendered covers how to defend against it.

A Worked Example: Finding Your Break-Even Volume

Flat-rate pricing has no monthly fee but a higher percentage. A gateway account usually pairs a lower effective rate (your total processing fees divided by your volume) with a fixed monthly gateway fee. Somewhere between those two structures is a monthly volume where they cost the same. You can find it with two quotes and a calculator.

1. Write down the flat-rate tool's percentage and per-transaction fee from its published pricing.
2. Ask the processor for the effective rate you'd likely pay on your card mix, its per-transaction fee, and every monthly fee, gateway included.
3. Subtract the gateway account's percentage from the flat rate. That gap is your saving on each dollar processed.
4. Divide the gateway account's total monthly fees by that gap. The answer is your break-even monthly volume.
5. Compare it with your actual online volume from last quarter.

Well above the line, the gateway account wins, and the margin widens as you grow. Below it, flat rate is usually cheaper and simpler. Per-transaction fees can tip a close call: a firm taking many small payments feels them far more than one taking a few large progress payments, so multiply each fee by your monthly payment count before you decide.

Two more levers can change the math. Firms that bill business customers can sometimes lower costs by passing invoice data with Level 2 and Level 3 processing. Others use MannyPay's surcharging programs where state law and card network rules permit, with the required disclosure shown before the customer pays.

Matching the Setup to Your Billing Pattern

Pull last quarter's invoices and sort them. Mostly fixed amounts? Pay buttons will do. If amounts vary, set up a hosted payment page and add pay links to your invoices. Recurring retainers, common for web design agencies and home healthcare and staffing agencies, call for stored cards backed by written authorization. Save the embedded form for the case where a branded checkout clearly wins you business.

Then bring those numbers to a processor: monthly online volume, average ticket and your largest single payment. The first two drive your pricing, and the last shapes how underwriting treats the account. Request a free quote, and a MannyPay specialist will respond within one business day.

DF

About the author

Daniel Foster

Daniel Foster is Product & Payments Technology Editor for Beyond the Swipe, covering POS systems, payment gateways, virtual terminals, mobile payments and integrations.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.