Also called: Checkout flow, Online checkout, Payment checkout
What checkout is
Checkout is the stage where a customer reviews an order, provides or confirms details, chooses a payment method and submits payment. In a store, that happens at a register or payment terminal. Online, it happens on a website or in an app, using a hosted page or payment fields built into your site.
For a card purchase, checkout starts the payment request. Your business sends transaction details through its payment processor and acquiring bank to the card network and issuing bank. The issuer approves or declines the authorization. An approval reserves funds, while capture tells the payment system to collect them. The order should move to fulfillment only after your system receives confirmation that payment was completed.
Checkout design does not set your card rates, but it determines how easily customers reach a paid order.
How checkout works
A checkout flow connects the order customers see with the payment request your business submits. The order details include items, quantities and total due. The payment request includes the information needed to process the selected method. If a customer pays online, the transaction is a card-not-present transaction, even when the cardholder is standing nearby.
Some checkouts run on a page hosted by a payment provider; others place payment fields within your own website. The choice affects the customer experience and how payment data is handled. A hosted page moves payment entry away from your site, while embedded fields keep more of the experience on your site. Either way, your systems need to connect the successful payment to the right order.
Why checkout matters to your business
A confusing checkout can leave customers unsure of the total, unable to find a suitable payment method or uncertain whether an order went through. Each extra step creates another point where a customer can stop before paying. A clear total, readable error messages and a working mobile layout address concrete problems that otherwise interrupt payment submission.
Checkout design does not set interchange, network assessments or your processor’s markup. Those charges attach to processed transactions, not to the checkout screen itself. Checkout affects costs indirectly: an approved sale produces processing fees and revenue, while an abandoned checkout produces neither. Separate software or service charges depend on your contract, not on a universal checkout fee.
Where checkout can go wrong
If your website treats a button click as proof of payment, you risk shipping an unpaid order. Use a confirmed payment event to trigger fulfillment, and keep an order identifier with the payment record so your team can reconcile the two. A completed payment and an authorization are different stages when your setup captures funds separately.
Payment fields also affect your security responsibilities. PCI DSS version 4.0.1 is current, and the future-dated requirements in version 4.0 became mandatory on March 31, 2025. If your checkout uses scripts on an e-commerce payment page, requirements 6.4.3 and 11.6.1 address script controls and detection of unauthorized changes. Your integration determines which controls apply to your environment.
What you can actually change
- Test the full flow. Place a real test order on a phone and a computer. Confirm the total, payment confirmation, order record and fulfillment trigger all match.
- Review failed payments. Track where customers see errors or leave before submitting payment. Fix unclear totals, broken fields and error messages that do not explain the next step.
- Check data handling. Document whether payment fields are hosted or embedded, then confirm the PCI DSS controls for your setup. Review e-commerce payment-page scripts against requirements 6.4.3 and 11.6.1.
- Separate fees from design. Review your processing statement for transaction charges and your software invoices for platform charges. Checkout itself is not a standard card-network fee.
Frequently asked questions
Is checkout a payment-processing fee?
No. Checkout describes the purchase flow where a customer confirms an order and submits payment. Card-processing charges apply to transactions, while any separate checkout software charge depends on the service contract.
What is the difference between checkout and payment processing?
Checkout is the customer-facing stage for reviewing an order and submitting payment. Payment processing carries the transaction request through the processor, acquiring bank, card network and issuer, then returns an approval or decline.
Does a hosted checkout page reduce PCI requirements?
A hosted page moves payment entry to a provider-controlled page, but your specific PCI DSS responsibilities depend on how your site and payment integration work. Identify where card data is entered and which scripts affect the payment page.