When a customer clicks the pay button on your website, the purchase seems to happen instantly. In those few seconds, though, several organizations exchange messages to decide whether the payment goes through. Understanding the basic roles helps when you are choosing a payment provider, reading a statement or figuring out why a payment failed.
The main players
Terminology varies, and many modern providers bundle several roles together, but the traditional parts are these:
- The cardholder. Your customer, paying with a card.
- The issuing bank. The bank or institution that issued the customer’s card and decides whether to approve the charge.
- The card network. The brand on the card, which routes transactions between banks and sets many rules.
- The acquiring bank. The bank that receives card payments on behalf of the business.
- The payment processor. The company that handles the technical movement of transaction data between the parties.
- The payment gateway. The technology that securely captures payment details from your website or checkout and passes them along.
Many popular providers for small businesses act as gateway, processor and merchant account all in one, so you sign up once and they handle the rest.
What happens when a customer pays
At a high level, a card payment moves through two stages.
Authorization. The customer enters their card details. The gateway securely sends them onward through the processor and card network to the issuing bank. The bank checks whether the card is valid, whether funds or credit are available and whether anything looks suspicious. It responds with an approval or a decline. All of this typically happens in moments.
Capture and settlement. After approval, the payment is captured, meaning the business confirms it wants to collect the funds. Some stores capture immediately. Others authorize at checkout and capture when the order ships. Captured payments are then settled, and funds move to the business’s account, minus fees, usually after a short delay that depends on the provider.
Why payments are declined
Declines come from many sources. The issuing bank may suspect fraud, the card may be expired or over its limit, or the details entered may not match. Some declines are triggered by the payment provider’s own fraud screening. When customers report a decline, the provider’s dashboard often shows a reason code that helps explain it. If declines suddenly increase, contact the provider, since a configuration issue may be the cause.
Choosing a provider
When comparing payment providers, look beyond the headline rate. Consider:
- How well it integrates with your website or store platform.
- Which payment methods it supports, including digital wallets.
- How quickly funds reach your account.
- Its tools for fraud screening, refunds and disputes.
- How it handles security, including whether card data ever touches your website.
- The quality and availability of its support.
Always read the current fee schedule and terms directly from the provider. With the roles clear, conversations about payments become much less confusing.
Following One Order From Click to Deposit
A worked example helps connect the roles. Imagine a customer buys a gift from a small online shop on a Monday evening.
- Checkout. The customer enters card details into a payment form provided by the shop’s payment provider. On many modern setups, that form is hosted or embedded by the provider, so the card number goes directly to the provider rather than being stored by the shop’s website.
- Authorization. The provider sends the request onward through the card network to the customer’s bank. The bank approves it, and the customer sees a confirmation page.
- Order notification. The store marks the order as paid or authorized and sends the confirmation email.
- Capture. Because this shop captures when it ships, the payment is captured on Wednesday, when the package leaves.
- Settlement and payout. The captured funds are settled, and after the provider’s usual delay, a payout arrives in the shop’s bank account, with fees deducted.
Two things are worth noticing. First, the money the customer sees as charged and the money that reaches the business are separated by time and fees. Second, the payout often groups many orders together, so matching a single deposit to individual orders takes a report from the provider. Most dashboards offer one that lists every transaction included in each payout.
Authorize Now, Capture Later: Things to Know
Capturing at shipment can be useful for stores that sometimes cannot fulfill an order, since canceling an uncaptured authorization is often cleaner than issuing a refund. It comes with a few cautions:
- Authorizations do not last forever. If too much time passes before capture, the hold may expire. Check your provider’s rules, especially for back orders and preorders.
- Customers may see a pending charge on their statement before capture and ask about it. A line in your confirmation email explaining when the charge will finalize can head off questions.
- Someone has to remember to capture, or the setting has to do it automatically when an order is marked shipped. Test that step.
Security and Your Responsibilities
Card payments come with security standards set by the card industry, known as PCI DSS. Even when a provider handles most of the work, businesses that accept cards generally have some responsibilities, such as completing a yearly self-assessment questionnaire depending on how payments are accepted. Your provider can tell you what applies to your setup.
The simplest way to reduce your burden is to make sure card details never touch your own website or servers. Hosted payment pages and embedded fields from your provider are designed for exactly this. Never ask customers to send card numbers by email, chat or contact form.
Reading a Payment Dashboard
Spend a few minutes getting to know your provider’s dashboard before you need it in a hurry. Find where to:
- Look up a single payment by customer email, amount or order number.
- See the decline reason for a failed payment.
- Issue a full or partial refund.
- View payouts and the transactions in each one.
- Respond to a dispute and upload evidence.
- Manage which team members have access, and at what level.
Questions Store Owners Ask
Why does a refund take days to reach the customer?
The refund is sent quickly from the provider’s side, but it has to travel back through the network to the customer’s bank, which then posts it to their account. Timing depends on the bank, so tell customers when you issued it and that their bank controls the rest.
Can we switch payment providers later?
Usually, though it takes planning. Saved cards, subscriptions and stored customer payment methods can be the hardest part to move. Ask any new provider how migration works before committing.
Should we offer more than one provider?
Some stores offer a card provider plus a popular wallet or alternative method. More options can help, but each one is another setup to test, reconcile and secure.



