A customer finds a product in an online store late in the evening. They are ready to buy, but instead of completing checkout, they are asked to contact a manager and request payment details. The customer might wait until the following day, or they might find the same product elsewhere. Online payments reduce this friction and allow a business to accept orders even when its staff are not working.

For the merchant, collecting money is only part of the process. The business needs a confirmed order, accurate inventory, customer notifications and instructions for its warehouse or digital product platform. All these processes must work together with the payment provider without depending on the customer keeping a browser window open or sending a screenshot of a transfer.

1. How online payments work

The store creates an order, determines the amount, currency and reference, and sends the required information to the payment provider. The customer enters their payment details through a supported interface and completes any additional authentication required by their bank. The provider processes the transaction and communicates the result to the website.

A payment gateway is not necessarily part of the store itself. The provider handles payment processing under its agreement with the merchant. WooCommerce, by contrast, manages products, checkout, orders and customer interaction. Connecting these systems requires a compatible gateway extension or a dedicated integration.

Online payment journey: order, payment provider, confirmation and fulfillment.The order is fulfilled according to the verified payment result.

Creating an order does not mean that payment has been received. An order may remain unpaid if the customer closes the bank's page, fails authentication or receives a declined transaction. These are normal situations that need to be handled just as carefully as successful payments. A reliable checkout should let the customer understand whether the transaction is complete or whether further action is required.

2. Which payment methods should a business offer?

The appropriate choices depend on the seller's country, its customers, its currencies and the nature of the business. Options can include bank cards, mobile wallets, local payment methods, bank transfers, payment on delivery and payment by invoice. Some methods give immediate confirmation, while others require additional time or manual verification.

There is no need to enable every payment service at once. A small store serving a local audience may benefit from a few familiar and clearly explained options rather than a long list of alternatives. An international business, on the other hand, may need to support payment methods commonly used in its customers' markets.

Products sold under negotiated conditions may require payment only after the final price has been agreed. For example, a furniture manufacturer making items to customer specifications may display indicative rather than final prices. The sales team confirms the order and creates an invoice or individual checkout that can subsequently be paid online. Our comparison of product catalogues and online stores explains this distinction in more detail.

3. How to choose a payment provider

Before connecting a provider, check whether it supports the merchant's legal status, country of registration, product category and required currencies. The availability of Stripe, PayPal, local bank acquiring and other services is not the same in every country. The existence of a WooCommerce plugin does not guarantee that a particular merchant can open a commercial account.

Compare more than the advertised transaction percentage. Costs may include fixed per-transaction fees, currency conversion, refund terms, dispute handling and the time required to receive settlements in the business bank account. The cost of the gateway extension, maintenance and additional integrations should also be considered separately.

Suppose a store accepts euros while its business bank account uses a different currency. The merchant needs to understand which currency is used for the transaction and for the payout, which party performs conversion and how the resulting amounts appear in financial reports. These questions are best resolved before development rather than after the first sale.

The payment provider's account should belong to the merchant, not the website developer. The business owner completes the required verification and retains access to financial information. Developers receive only the permissions necessary for configuration and testing. Always check the provider's current eligibility, pricing and terms before launching a live integration.

4. Hosted checkout or an integrated payment form

Some payment solutions redirect customers to the provider's secure hosted payment page. Others embed provider-managed payment components within the store's checkout. Both approaches can provide a convenient experience when implemented according to the provider's documentation. The choice depends on the available extension and the requirements of the website.

A hosted payment page can simplify implementation because the provider manages the necessary payment fields and authentication steps. Embedded components can offer a more continuous checkout experience, but they must be compatible with the checkout implementation, mobile devices and other site extensions. In either case, the payment button should clearly communicate what the customer is buying.

Do not store full card details in WordPress, collect them through a standard contact form or request that customers send them by email. Use supported provider mechanisms designed to handle payment information. This reduces certain risks but does not eliminate the merchant's responsibilities for website security, account access and personal data. Our WordPress and WooCommerce security guide covers the wider technical issues.

5. Payment and order statuses in WooCommerce

WooCommerce uses order statuses to show staff what stage an order has reached. An unpaid order can remain pending payment. A confirmed and paid order requiring shipment commonly moves into processing, while a fulfilled order can be marked completed. Exact behaviour depends on the gateway, the products and the configuration of the store.

Declined payments, delayed confirmations and cancelled checkout sessions must also be accounted for. Some payment methods do not confirm transactions immediately. Shipping a product or granting access to a course before the intended payment confirmation can expose the business to avoidable losses. Holding every successful order for manual approval, however, introduces unnecessary delay.

Example payment states and merchant actions: waiting, confirmed, failed and refunded.The verified payment state determines the next action.

A reliable integration receives confirmation from the provider, for example through a webhook, a server-to-server notification about an event. It must verify the authenticity of the notification and match the amount, currency and transaction reference. Receiving the same event more than once should not trigger duplicate fulfilment, grant access twice or create additional stock adjustments.

Do not rely solely on the customer's return to a thank-you page. Someone can close their browser immediately after a successful payment. The website should be able to recognise the confirmed transaction and perform the appropriate business action even if the customer never loads that final page.

6. Payments for different types of websites

For a WooCommerce online store, payment is associated with an order containing products, shipping, discounts and the final total. Once confirmed, the system can notify the sales team, perform configured inventory actions and pass order information to a CRM or fulfilment provider.

A landing page advertising a single service may need a simpler flow. The customer chooses an offer, enters the required contact details and pays. Even in this case, the integration needs to associate the transaction with a specific request, so the business knows what has been purchased. Where pricing depends on individual requirements, it may be better to agree the terms before collecting the full payment.

A website with online booking must also manage time slots. If a booking requires a deposit, the system needs a rule for how long the selected time is reserved and what happens if payment is not completed. This helps prevent two people from booking the same appointment or unpaid reservations from blocking the calendar indefinitely.

For a ticketed event, the same principle applies to capacity rather than time slots. A payment integration needs to work with availability and registration so that the organiser can identify paid participants, manage cancellations and prevent the issue of duplicate tickets. The appropriate flow should be tested before advertising the event.

7. Digital products, courses and subscriptions

Payment for a digital product can trigger automatic delivery. A customer receives an account, a download link or access to the course once payment has been confirmed. Staff do not need to send the material manually to every individual. However, the system must address what happens in the event of a refund, cancellation or integration error.

Subscriptions require an additional renewal mechanism. Not every payment gateway that supports a standard card purchase can automatically collect recurring payments. Both the subscription extension and the provider must support the desired method. Automatic renewal is also different from manual renewal, in which the customer actively pays for each new billing period.

The merchant should define the access period, renewal frequency, cancellation options and the response to failed payments. For example, if a renewal fails, the website can notify the customer to update their payment method and apply a predefined rule for access. Learn more about this kind of project on our online learning platforms page.

8. Refunds, disputes and reconciliation

A website owner should understand in advance how full and partial refunds are handled. Supported WooCommerce payment extensions can submit refund requests to their providers, but an extension that supports only manual refunds does not transfer money back simply because an order status was changed. The actual refund result should be verified in the provider's records.

A transaction may become the subject of a payment dispute, for example when a customer challenges a charge through their bank. Merchants should retain appropriate order confirmations, delivery records and customer communications. The handling process, possible fees and applicable deadlines depend on the payment provider and the circumstances of the transaction.

Regular reconciliation of store orders, transactions, refunds and bank settlements can identify discrepancies. Gross successful payments for a day might not equal the payout received because of fees, settlement schedules and refunds. Recordkeeping and documentation requirements also depend on the jurisdiction and business circumstances. Discuss these requirements with a qualified accountant rather than relying on the gateway to provide an entire accounting solution.

9. Testing the integration before launch

When a provider offers a sandbox or test mode, use it before accepting real money. Test successful payments, declined transactions, interrupted authentication, retries, refunds and temporary provider failures. A single successful test purchase is not enough to demonstrate that the full payment workflow is ready for customers.

Test checkout on a phone and a desktop computer. Change shipping methods, apply discount codes and check currency selection where applicable. Verify that the final order total matches the amount passed to the payment provider and that the confirmation page and customer email contain the expected details. Include both guest checkout and account-based checkout if the store offers them.

A staging site should not accidentally send real shipments, notifications to actual customers or live financial transactions. Keep live and test configuration separate. Before switching to production, verify the account connection, provider notification settings, HTTPS, available payment methods and an agreed end-to-end live test with the merchant.

Repeat key scenarios on a staging copy before releasing important WooCommerce, theme or gateway updates. A storefront may still appear to work normally even when a change to checkout has prevented customers from completing their purchases. Periodic checks make these problems easier to detect before they affect significant numbers of orders.

10. Integration costs and ongoing maintenance

The cost of adding online payments depends on whether a compatible extension already exists, which methods are required, and whether the site needs custom order rules, subscriptions, booking deposits, partial payments or an external accounting integration. Connecting a standard gateway to an existing WooCommerce store differs from integrating multiple providers, currencies and complex order workflows.

Consider the costs after launch: provider fees, extension licensing where needed, compatibility checks and maintenance in response to changes. A website running on its own hosting may avoid compulsory platform subscription fees, but that does not mean payment processing is free or that the business has no ongoing operating expenses.

At CianBay Studio, we integrate payment gateways according to the website's requirements, choose solutions agreed with the client and account for relevant testing scenarios. Where payment triggers other business processes, consider the integration as part of broader website automation. Payment then becomes part of a structured sales system rather than an isolated button.

Frequently asked questions

Do I need an online store to accept payments on my website?

Not necessarily. Payments can be integrated into a landing page, service website, learning platform or payment link, provided the chosen provider supports the arrangement. The payment should still be connected to a specific order, registration or request.

Can I use two payment providers at the same time?

Yes, if both support the merchant and are compatible with the website. Check the requirements and pricing of each provider, and ensure payment confirmation and refund tracking work correctly for both integrations.

Can a course be unlocked automatically after payment?

Yes. A platform can grant access after receiving verified payment confirmation under the configured rules. Refunds, failed payments and repeated notifications must also be handled correctly.

What makes online payments on a website reliable?

In 2027, online payments can make purchasing, appointment booking and digital product sales more convenient. Reliability depends not only on the provider selected but also on correct order management, event handling, security and testing. A well-designed website allows customers to complete payment independently while giving the business a clear and manageable sales process.

Sources and documentation

Originally published at CianBay Studio.

Disclosure: This article was prepared with AI assistance.