How online payments work
A plain-English walkthrough of what happens between a customer clicking "Buy" and the money arriving in your bank account.
When a customer clicks "Pay now" on your website, a lot happens in about two seconds. Understanding the journey helps you make better decisions about your payment setup and troubleshoot problems when they arise.
Quick summary
A customer's card details travel through several systems — your website, a payment gateway, a payment processor, and the card networks — before the money settles in your bank. Each step adds a small fee. The whole process usually takes seconds to authorize and one to three business days to deposit.
The players involved
Before we trace the journey, here are the main parties:
| Party | What they do |
|---|---|
| Customer | Enters their card details and confirms the purchase |
| Your website | Collects the payment form and sends it securely onward |
| Payment gateway | The secure tunnel that moves card data to the processor |
| Payment processor | Requests authorization from the card network |
| Card network | Visa, Mastercard, American Express — routes the request to the bank |
| Issuing bank | The customer's bank — approves or declines the charge |
| Your bank | Where the money lands after the processor pays out |
Modern tools like Stripe combine the gateway and processor roles into one product, which simplifies things considerably.
The payment journey, step by step
Customer enters their card details. Your website shows a secure payment form. The form is usually hosted by your payment processor (Stripe, PayPal, etc.) rather than your own server — this keeps sensitive card data off your systems.
The payment gateway encrypts and forwards the data. The card number, expiry, and security code are encrypted and sent to the payment processor. This happens over a secure connection (HTTPS/TLS).
The processor asks the card network to authorize the charge. The processor sends an authorization request to Visa, Mastercard, or whichever network issued the card.
The card network routes the request to the customer's bank. The issuing bank checks the customer's available balance, looks for fraud signals, and sends back an approval or a decline.
The result returns in seconds. If approved, the customer sees a success message. If declined, they see an error and can try another card.
The funds are "captured." Authorization holds the money. Capture actually moves it. Most online stores capture immediately at checkout. Some (hotels, for example) authorize first and capture later.
Settlement happens overnight. At the end of each business day, processors batch and settle all captured transactions. The net amount (sale minus fees) moves toward your bank account.
The money arrives in your bank. Depending on your processor and settings, this takes one to three business days. Stripe's standard schedule is two business days in the US.
Authorization vs capture
These two steps are easy to confuse.
- Authorization reserves the funds on the customer's card. The money has not moved yet.
- Capture actually moves the money. This is when the charge appears on the customer's statement.
For most e-commerce stores, authorization and capture happen at the same moment. But if you run a business that ships goods after confirming stock, you may want to authorize first and capture only when the item ships.
Why you might see two entries on a bank statement
Sometimes customers see a "pending" charge (the authorization) and then a "completed" charge (the capture). The pending entry usually disappears within a few days once the capture settles.
Why payments sometimes fail
A declined payment does not always mean the customer lacks funds. Common reasons include:
- The card number, expiry date, or security code was entered incorrectly
- The customer's bank flagged the transaction as potentially fraudulent
- The card has a foreign transaction restriction
- The billing address did not match the bank's records
- The card has reached its daily spending limit
Most processors return a decline code. Stripe's dashboard shows a human-readable reason, which helps diagnose the issue.
What "processing fees" are
Every party in the chain charges a small fee for their role. These fees are usually bundled together and deducted from your payout. You never pay them separately — you simply receive slightly less than the full sale amount.
See Payment fees explained for a full breakdown of every fee type.
Common questions
Related guides
- Payment processors explained
- Payment fees explained
- Stripe basics for business owners
- PayPal basics for business owners
- Payment security & PCI compliance
- Accepting credit cards (WooCommerce)
Need a hand?
Learn more
Accepting payments online, explained
Everything you need to know about taking payments on your website — from how money moves to fees, security, and common processors like Stripe and PayPal.
Payment processors explained
What a payment processor does, how it differs from a payment gateway, and how to choose the right one for your business.