To accept online payments, choose a payment provider, complete its business verification, connect your business bank account, and give customers a payment page tied to what they owe. For individually priced service jobs, an invoice with a payment link is often a practical starting point.

You do not need a full online store or a new operating system just to collect a payment. First check whether your current invoicing software already supports online payments. The useful upgrade may be configuring that tool properly—not buying another one.

Start with the bill, not the button.

Before adding “Pay now,” decide what the customer owes, when it is due, and how the payment will be matched to the correct customer and job.

Invoice link, hosted checkout, or customer portal?

These are different ways to present payment, not necessarily different providers. A hosted checkout is a payment page operated by the provider; invoice links and shareable payment links can both lead to provider-hosted pages.

Invoice link: for a specific customer and amount
A useful fit for a completed cleaning job, an approved landscaping project, or a website build. The customer sees the bill and pays its balance. Keep the invoice number and job reference together so the office can identify it later.
Payment link or checkout: for a defined purchase
A useful fit for a clearly described fixed-price service or agreed deposit. A generic reusable link needs a reliable way to identify the customer and work. Do not assume it settles an existing invoice unless that connection is actually configured.
Customer portal: for an ongoing billing relationship
A useful fit when customers need several invoices, receipts, or payment-method updates in one place. It can complement direct invoice links. A portal adds access and support considerations, so use one because customers need it—not simply because it is available.

For example, Stripe’s hosted invoice page lets customers review invoice details, pay with enabled methods, and download an invoice or receipt. Its Payment Links documentation distinguishes a bill for a particular customer from a reusable purchase link. Other providers have their own options and limitations.

A Stripe customer portal can handle billing details, invoices, and supported subscription actions. That does not automatically provide a service calendar or job history. Our customer portal guide helps you decide whether the broader experience is worthwhile.

Set up online payments in five steps

  1. Write down when you bill. Is payment due after completion, before a visit, or at agreed project stages? Make the amount and scope clear before requesting money. For staged projects, record deposits and the remaining balance separately.
  2. Compare the tools you already use. Ask about payment methods, total fees, invoice matching, refunds, support, and data exports. A built-in invoice link may be enough for a small volume of work.
  3. Set up the business account. Use accurate business details and a bank account the business controls. Complete the provider’s verification. Keep owner access, enable multifactor authentication, and give staff only the access they need.
  4. Make the customer experience recognizable. Check the business name, logo, service description, amount, currency, due date, receipt, and contact details. Confirm how your business will appear on a card statement. Do not send a live link until those details are right.
  5. Connect payment to your records and test it. Decide who checks payments, handles exceptions, and reconciles payouts. If an integration updates your operating system, verify that it updates the right invoice—not merely a customer-level “paid” flag.

Use the provider’s supported payment fields or hosted page. Do not collect full card details in an ordinary contact form, text message, or spreadsheet. Stripe’s security guide explains that lower-risk integrations can keep sensitive card information off your server, but compliance remains a shared responsibility. Hosted payments do not remove all of the business’s security obligations.

Have your accountant or qualified adviser review tax treatment and bookkeeping; confirm payment, cancellation, and refund terms for your situation. This article is a setup guide, not legal or tax advice.

What does accepting online payments cost?

Look beyond the advertised card rate. Ask about processing, invoicing or subscription charges, monthly software costs, optional features, refunds, disputes, and payout options. Your business type, payment method, country, and contract can change the total.

As checked September 28, 2026, Stripe’s standard U.S. pricing lists 2.9% + 30¢ for a successful domestic-card transaction and Invoicing Starter at 0.4% per paid invoice. Verify your own account’s pricing before choosing a setup.

Example: a $500 invoice

At those listed rates, card processing would be $14.80: ($500 × 2.9%) + $0.30. If Invoicing Starter also applies, its $2 fee brings the illustrated total to $16.80, leaving $483.20 before any other applicable costs or adjustments.

This is a calculation for the stated assumptions—not a quote, a universal rate, or a promised bank payout. Different products, payment methods, add-ons, or negotiated terms change the result.

MU Extension’s market-channel cost guide explains why processing costs should be compared by provider and payment channel, alongside recurring expenses. It is written for farm businesses; the relevant principle for a service owner is to compare the whole collection cost without counting the same expense twice.

Also consider the office work involved. A cheaper transaction may still require someone to identify the payment and update a bill manually. Estimate that effort honestly; do not assume automation will save a particular amount before measuring it.

A success page is not the payment record

A customer might finish paying and close the browser before returning to your site. Another might cancel checkout. Your records must not depend only on which page they visit.

Stripe’s fulfillment documentation calls for server-side payment events when automating the follow-up. Your developer should verify the event, match it to the right record, check payment status, and prevent repeated notifications from applying the same payment twice. Some methods, including ACH debit, can remain processing before success or failure is known.

For a simple manual setup, check the provider’s actual payment record before marking an invoice paid. For an integrated setup, agree on how pending, failed, refunded, and disputed payments are represented and who reviews exceptions.

A successful payment and money arriving in your bank are also different events. Stripe’s payout documentation distinguishes payment settlement, payout schedules, and bank availability. Check your account’s expected deposit dates rather than promising yourself immediate access to every payment.

Keep records for the gross amount, fees, adjustments, and bank deposit. Missouri State University’s efactory financial-statements guide explains the different roles of revenue, expenses, cash flow, and cash on hand. Applying that distinction here: an invoice total is not the same thing as spendable cash or profit. Ask your bookkeeper how to reconcile the provider’s reports with your accounts.

Example: from completed work to a matched payment

A hypothetical window-cleaning job

  1. The office reviews the completed work and prepares the correct invoice.
  2. The customer receives a private invoice link showing the business, job, and amount due.
  3. The payment provider handles checkout. The customer gets a receipt after confirmed payment.
  4. The payment is matched to that invoice in the business’s records. A pending payment stays pending; a cancelled attempt does not mark the bill paid.
  5. The office reconciles the provider’s payout and fees with the bank deposit.

This is an illustrative workflow, not a claim about a particular client’s setup or results. Its value is the connection between the bill, payment, and record—not just adding another payment button.

Before you send a real customer a payment link

Use your provider’s test environment where available. Do not run real charges simply to check whether a page works.

  • Correct bill: verify the customer, service, amount, currency, and any deposit already received.
  • Phone experience: open the link on a phone and check that the details and payment controls are readable.
  • Successful payment: confirm one payment produces the right receipt and updates only the intended invoice.
  • Cancelled or failed attempt: keep the balance accurate and provide a working path back to the business or bill.
  • Delayed confirmation: if supported methods can process asynchronously, test that “processing” is not mistaken for “paid.”
  • Repeated events: ask your developer to test retries without duplicate payment records or duplicate follow-up actions.
  • Refunds and access: confirm who can issue refunds, where adjustments appear, and that private billing records are not publicly accessible.
  • Launch settings: verify live account details and notification settings separately from test settings before accepting real payments.

After launch, review the first genuine payments and payouts. Keep a visible business contact option for customers who need help. A payment link should make paying easier, not replace a person when a bill needs explanation.

When does a connected website and operating system help?

If your current invoice tool already collects payment and keeps balances accurate, you may not need more software. The bigger opportunity appears when staff repeatedly copy amounts, search for receipts, or update job and customer records in several places.

We built Pebble Creek’s website and operating system around our lawn and property-care business. That same approach starts with your actual workflow: who approves work, who sends the invoice, where customers pay, and where the team checks the result.

A connected system can be designed to keep those steps together while using a payment provider for payment processing. Available integrations, support, and scope need to be evaluated for your business; custom software does not eliminate processing fees or payment-provider requirements.

Explore a connected website and custom operating system if getting paid still means manually piecing together several tools.

Sources and further reading

Reviewed September 28, 2026. Fees and product features can change. Examples and checklists are practical guidance, not guarantees of results. These organizations do not endorse Pebble Creek Media.

  1. Refining Market Channel Selections Based on CostMU Extension · processing and recurring costs, in a farm-business context.
  2. Understanding Your Small Business’s Financial StatementsMissouri State University’s efactory · revenue, expenses, cash flow, and cash on hand.
  3. Hosted invoice pageStripe · invoice details, payment options, and receipts.
  4. Payment LinksStripe · shareable checkout and comparison with invoicing.
  5. Customer portalStripe · billing capabilities and limitations.
  6. Pricing and feesStripe · current pricing to check against your own account terms.
  7. Fulfill ordersStripe · reliable payment confirmation, delayed methods, and repeated events.
  8. Receive payoutsStripe · settlement timing and bank payouts.
  9. Integration security guideStripe · lower-risk integrations and shared security responsibilities.