Online Payments and Invoicing: How Payment Workflows Work

The problem: payments that are slow, manual and disconnected

A customer agrees to buy. The business sends a bank transfer request by email, or an invoice as a document attachment, and then waits. Payment arrives days later, perhaps without a reference, and someone must match it to the customer, update the spreadsheet, send a receipt and start the work. When a payment fails or is late, chasing it depends on somebody remembering. Every manual step delays cash flow and adds room for error.

Educational introduction: how online payments work

Taking a card or bank payment online involves several parties. The customer provides payment details. A payment gateway securely transmits them. A payment processor communicates with the card networks and banks, and funds are eventually settled to the merchant's bank account. Many payment providers bundle these roles into a single service, so a business signs up with one provider and receives a checkout, dashboard and payouts.

You do not need to understand every layer to use payments well, but it helps to know that fees, security requirements and payout timing are determined by your payment provider and vary by country and plan.

Why this problem exists

• Payment tools are separate from customer tools. The provider knows who paid; your CRM may not.
• Invoices and quotes are prepared by hand in word processors.
• Different payment situations need different methods: one-off payments, deposits, instalments and subscriptions.
• Follow-up depends on people, so overdue reminders are irregular.
• Reconciliation is manual, taking time at month end.

The traditional approach

Traditionally, businesses accepted cash, cheques, bank transfers and card terminals. Invoices were created in word processors or accounting software and sent by post or email. Online, many added a payment button to their website, linked to a provider's hosted page. That works and is secure, but the connection between payment and the rest of the business remains manual.

Limitations of disconnected tools

• No automatic record. A successful payment does not update the contact, pipeline stage or order.
• Duplicate data entry between the payment provider, accounting software and CRM.
• Delayed onboarding, because someone must confirm receipt before starting.
• Inconsistent branding if the payment page looks different from your website.
• Limited insight into revenue by source or campaign.
• Failed payments go unnoticed, especially for subscriptions.

The modern integrated approach

The modern approach connects payment events to the customer record. When a checkout succeeds, the system marks the order as paid, updates the contact and pipeline, sends a receipt, grants access if relevant and starts follow-up. When a payment fails, an automatic message invites the customer to update their details. Reporting can then show revenue by product, source and period. Integrated platforms may include payment features and integrations with providers; other setups use webhooks or connectors to link a payment provider to a CRM. Our explainer on how APIs and webhooks connect tools describes the mechanics.

Feature breakdown: the parts of a payment system

Online payments

Online payments let customers pay by card, bank debit or wallet, depending on your provider and country. Offer the methods your customers prefer, while remembering that each method carries different fees and dispute processes.

Payment links

A payment link is a shareable web address that opens a payment page for a fixed amount or product. It requires no website integration and is useful for quick sales, deposits and invoices sent by message.

Invoices

An invoice requests payment for goods or services and typically includes an invoice number, date, itemised charges, tax information, payment terms and instructions. Online invoicing systems generate them from templates, email them, offer a pay-now button and track status: draft, sent, viewed, paid, overdue. Tax and invoice requirements vary by country, so check what applies to you.

Products

Product records store names, descriptions, prices and, where relevant, tax settings and images. A well-organised product list prevents pricing errors and makes reporting meaningful.

Checkout

Checkout is where the purchase is completed. Good checkout pages are clear about what is being bought, the total price including taxes and shipping, the payment options and what happens next. Reduce steps, avoid surprises and make the page work well on phones. Our sales funnel guide covers how checkout fits the customer journey.

Subscriptions

Subscriptions charge customers at regular intervals for continuing access or service. They suit memberships, maintenance plans and software. Set clear terms about renewal, cancellation and price changes, and remind customers before renewal where required.

Recurring billing

Recurring billing automates repeated charges, including instalment plans for larger purchases. Look for handling of failed payments: automatic retries, notifications and a way for customers to update card details.

Customer payment history

A customer's payment history, including invoices, payments, refunds and subscriptions, should be visible on their record so that staff can answer questions and see context without switching systems.

Payment automation

Automations triggered by payment events include sending receipts, updating the pipeline, granting access, notifying staff, requesting reviews and reminding customers about overdue invoices. See how workflow triggers and actions work.

Payment providers

Several payment providers operate globally and regionally, with varying fees, supported countries and features. When comparing, consider fee structures, payout timing, supported payment methods, dispute handling, security and compliance features, integration options and support. Platforms often integrate with more than one provider. Fees and availability change, so read the current terms.

Sales-to-payment workflow

The workflow from agreement to payment can be shortened by generating a payment link or invoice at the moment a deal is won, sending it automatically and updating the pipeline when it is paid.

Step-by-step workflow: from checkout to follow-up

1. Customer. A person decides to buy, following a quote, a booking or a product page.
2. Checkout. They complete a secure payment page.
3. Payment. The provider confirms the transaction.
4. Receipt. A receipt or confirmation is sent automatically.
5. CRM update. The contact is tagged as a customer, the opportunity is marked won and the order is stored.
6. Follow-up. Onboarding messages, delivery details or a review request begin.

A real-world example

A photography studio sells portrait sessions. Previously, the owner emailed a price list, waited for a bank transfer and then booked the session, sometimes only to find that payment had not arrived. She now sends a payment link for a deposit when the client chooses a date. When the deposit is paid, the session is confirmed, the contact is tagged and a preparation guide is sent automatically. A balance invoice is issued the day before the shoot and a reminder goes out if it is unpaid three days later.

She spends less time chasing and matching payments, and can see at a glance which sessions are confirmed and which invoices are outstanding. The system cannot change whether clients want to buy, but it removes friction between yes and paid.

Benefits

• Faster payment and clearer cash flow visibility.
• Fewer manual steps and reconciliation errors.
• Payment status visible on the customer record.
• Automated receipts and reminders.
• Better reporting on revenue by product and source.

Things to consider

• Fees. Compare transaction fees, monthly fees, currency conversion and dispute charges.
• Payout timing. Understand when money reaches your bank account.
• Security and compliance. Use hosted payment forms provided by a reputable provider, so card details do not touch your own servers. Understand your provider's requirements, including PCI-related obligations.
• Tax and invoicing rules that apply in your location.
• Refund and dispute handling. Write a refund policy and know how chargebacks work.
• Customer data. Decide what payment information is stored in the CRM. Card numbers should not be.
• Availability by country. Check that your provider supports your business location and your customers' payment methods.

Common mistakes

• Storing card details in spreadsheets or messages.
• Hidden fees or unclear totals at checkout.
• No refund or cancellation policy.
• Unclear subscription terms.
• Not testing the whole payment flow before launch.
• Ignoring failed subscription payments.
• Mismatched product names and prices between systems.
• Poor mobile checkout.
• No receipts or confirmations.

Questions to ask a provider before you choose

Payment terms are precise, so read them and ask for anything unclear in writing:

• What are the transaction fees, and are there monthly, setup, currency-conversion or dispute fees?
• When are funds paid out, and can payouts be held or delayed?
• Which countries, currencies and payment methods are supported?
• How are failed subscription payments retried, and what notifications are sent?
• What tools exist for refunds, disputes and chargebacks?
• How does the provider meet security and compliance requirements, and what is my responsibility?
• How does the payment system connect to my CRM and accounting software?
• Can I export transaction and customer data, and can I migrate stored payment details if I switch?

How to measure whether your payment process is working

Payment processes are easy to measure because they leave a clear trail. Useful measures include:

• Days to get paid, from invoice sent or checkout to funds received.
• Overdue rate: the share of invoices unpaid after the due date, and average days overdue.
• Checkout completion: of the people who start a purchase, how many finish? Drop-offs often point to unexpected costs, missing payment methods or an awkward mobile experience.
• Failed payment recovery for subscriptions: what share of failed charges are recovered after reminders?
• Refund and dispute rates, which can indicate unclear descriptions or delivery problems.
• Fees as a share of revenue, so that you notice when pricing terms change.

Reconcile these against your accounting records each month; discrepancies are usually easier to fix while they are recent.

A practical first-week plan

1. List every way customers currently pay you and what each costs in fees and effort.
2. Create clear product or service records with prices and tax settings.
3. Set up one payment link or checkout and complete a small live test transaction.
4. Write your refund and cancellation terms in plain language and link them at checkout.
5. Connect the payment event to a receipt message and a customer record update.
6. Add an overdue reminder that goes out a few days after the due date.

Implementation checklist

• Choose a payment provider that supports your country and customers.
• Create products with clear names, prices and tax settings.
• Set up a checkout or payment link and test it with a real, small transaction.
• Create an invoice template with the required details.
• Write refund, cancellation and subscription terms in plain language.
• Connect payment events to the CRM.
• Automate receipts, failed-payment notices and overdue reminders.
• Restrict who can issue refunds and view payment reports.
• Reconcile payments with accounting each month.
• Review fees and terms yearly.

Comparison table: ways to take payment

Frequently asked questions about payments and invoicing

Related guides and further learning

Related category guides

Supporting explainers

• How APIs and Webhooks Connect Business ToolsA non-technical explanation of APIs, webhooks, polling and no-code connectors, and how they move customer data between the tools a business uses.
• How to Evaluate Business Software Before You CommitA vendor-neutral method for comparing CRM, automation and marketing platforms: requirements, trials, data portability, pricing models, support and lock-in.
• How Workflow Triggers and Actions WorkUnderstand how automation workflows are built from triggers, conditions and actions, with examples, design tips and common mistakes to avoid.

Practical guide and glossary

• Business Software Evaluation ScorecardA vendor-neutral scorecard to compare CRM, website, automation, payment and other business platforms on requirements, integrations, cost, data portability and support.
• Glossary: Payment gatewayA plain-language definition you can refer back to while reading.