Key takeaways
- A card payment usually moves through several parties: the merchant, processor or payment service provider, acquiring bank, card network, and the customer’s issuing bank.
- Authorization happens in seconds, but settlement and funding usually happen later.
- The price a merchant pays can include interchange, network fees, processor markup, gateway or platform fees, and other account-specific charges.
- The “best” processor depends on the business model, payment channels, monthly volume, risk profile, countries served, and the level of support required.
Credit card processing can feel complicated because a payment that looks instant to a customer is actually a short chain of messages and money movements between several companies. The good news is that the basic flow is fairly consistent once you understand the roles.
This guide explains what happens from the moment a customer presents a card until the merchant receives funds, where processing fees come from, and what businesses should pay attention to when comparing providers.
What happens when a customer pays by card?
1. The customer starts the payment. The customer taps, inserts, swipes, or enters card details online. The merchant’s point-of-sale system, checkout page, or payment gateway securely passes the transaction information into the payment system.
2. The transaction is sent for authorization. The processor or payment service provider routes the request through the appropriate card network to the bank that issued the customer’s card.
3. The issuing bank checks the transaction. The issuer may evaluate whether the account is valid, whether sufficient credit or funds are available, and whether the payment appears suspicious. It then returns an approval or decline response.
4. The merchant receives the response. An approved transaction allows the sale to continue. The customer may see the purchase as pending even though the merchant has not yet received the money.
5. The transaction is captured and settled. Approved transactions are later submitted for settlement. Funds move through the payment system, fees are applied, and the merchant receives the net deposit according to the provider’s funding schedule.
The exact architecture varies. Some modern payment companies bundle several of these roles together, while traditional merchant-account setups may involve separate providers for the merchant account, gateway, processor, and point-of-sale system.
The main parties in a card transaction
| Party | What it generally does |
|---|---|
| Merchant | The business accepting the card payment. |
| Customer / cardholder | The person or business using the card to make the purchase. |
| Payment processor or payment service provider | Connects the merchant’s payment flow to the broader card-payment system and handles transaction routing and related services. |
| Acquiring bank | The financial institution on the merchant side of the transaction. Depending on the provider, the merchant may interact with the acquirer directly or through a processor or platform. |
| Card network | Networks such as Visa or Mastercard route transaction messages between the acquiring side and issuing side and set network rules and fees. |
| Issuing bank | The bank or financial institution that issued the customer’s card and makes the authorization decision. |
| Payment gateway | Technology that securely transmits payment information, especially for ecommerce and other card-not-present transactions. It may be bundled into the processor’s platform. |
Authorization, capture, settlement, and funding
These terms are related, but they describe different stages of a payment.
Authorization is the approval step. The issuer is effectively saying that the transaction can proceed at that moment. An authorization can place a hold on the customer’s available credit or funds, but it is not the same thing as the merchant receiving money.
Capture is the merchant’s confirmation that the approved payment should be finalized. Some businesses capture immediately. Others, such as hotels or companies that ship goods later, may authorize first and capture after the final amount is known.
Settlement is the process of reconciling approved transactions and moving funds through the card-payment system.
Funding is when the processor or acquiring side deposits the merchant’s net proceeds into the merchant’s bank account. Funding speed depends on the provider, risk profile, transaction timing, weekends and holidays, and the merchant’s agreement.
Where credit card processing fees come from
A merchant’s processing cost is rarely a single fee paid to one company. Several components can be combined into the final price.
| Fee component | What it represents |
|---|---|
| Interchange | Fees associated with the issuing side of card transactions. Rates can vary based on card type, transaction type, merchant category, and other factors. |
| Network or assessment fees | Fees charged in connection with the card networks. |
| Processor markup | The provider’s own margin for processing and related services. |
| Gateway or platform fees | Charges for ecommerce gateways, software, payment orchestration, recurring billing, or other technology. |
| Account and service fees | Depending on the provider, this can include monthly fees, statement fees, PCI-related fees, chargeback fees, equipment costs, or other charges. |
This is why comparing only the advertised transaction rate can be misleading. Two providers can quote similar headline rates but produce very different total costs once volume, average ticket size, card mix, monthly fees, and contract terms are considered.
Common pricing models
Flat-rate pricing charges a relatively simple published rate for a category of transactions. It is easy to understand and often attractive to smaller businesses that value predictability and fast setup.
Interchange-plus pricing separates underlying interchange and network costs from the processor’s markup. It can make the provider’s margin easier to see and may become attractive as processing volume grows.
Subscription or membership pricing typically combines a monthly platform or membership fee with transaction-level charges. Whether it saves money depends heavily on volume and the specific agreement.
Custom enterprise pricing is common for larger merchants. Rates and contract terms may be negotiated around volume, geography, risk, payment methods, integration requirements, and support needs.
Why card payments get declined
A decline does not automatically mean something is wrong with the processor. The issuing bank makes many authorization decisions, and a transaction can be declined for insufficient funds or credit, an expired or replaced card, incorrect details, suspected fraud, account restrictions, or other issuer rules.
Merchants should pay attention to decline rates over time, especially in ecommerce and subscription businesses. Good payment infrastructure can help with areas such as card updating, retry logic, fraud controls, and clear decline information, but no processor can force an issuer to approve a transaction.
Card-present versus card-not-present payments
Card-present transactions occur when the card or a digital wallet is physically used at the point of sale, such as with a chip, contactless tap, or mobile wallet. These transactions generally provide stronger proof that the payment credential was present.
Card-not-present transactions include ecommerce, phone orders, and many recurring payments. Because the merchant cannot physically inspect the card, fraud and dispute risk can be different. Pricing and risk controls may also differ.
A processor that is excellent for a retail counter is not automatically the best choice for a subscription company or international ecommerce business. The payment channel matters.
Chargebacks and disputes
A chargeback occurs when a cardholder disputes a transaction through the issuing side of the card system and the dispute proceeds through the network process. Merchants may need to provide evidence showing that the transaction was legitimate and that the product or service was delivered as agreed.
High dispute rates can increase costs and may lead to additional monitoring, reserves, restrictions, or account termination. Businesses with elevated chargeback exposure should evaluate a provider’s fraud tools, dispute-management capabilities, underwriting experience, and support before signing up.
Security and PCI compliance
Businesses that accept payment cards have security responsibilities. The Payment Card Industry Data Security Standard, commonly called PCI DSS, establishes requirements for protecting cardholder data and maintaining secure payment environments.
The simplest approach for many merchants is to reduce how much sensitive card data their own systems handle. Hosted checkout pages, tokenization, properly designed point-of-sale systems, and provider-managed payment components can reduce exposure, although they do not eliminate every merchant responsibility.
Security should be part of the processor decision, especially for businesses building custom integrations or storing customer payment credentials for future use.
How quickly does a merchant get paid?
Funding speed varies by provider. Some merchants may receive funds the next business day or even faster in certain programs, while other arrangements take longer. New accounts, unusual transaction patterns, elevated risk, weekends, bank holidays, or reserve requirements can affect availability.
Faster funding can be valuable, but it should not be evaluated in isolation. A business should also understand whether faster deposits cost extra, whether the provider can place reserves, and what circumstances can delay settlement.
What should a business compare before choosing a processor?
Total cost. Look beyond the advertised percentage. Consider transaction fees, monthly charges, gateway costs, equipment, chargeback fees, and any minimums or incidental charges that apply to your business.
Contract terms. Understand the contract length, cancellation provisions, equipment obligations, auto-renewal language, and any early-termination fees.
Business-model fit. Confirm that the provider supports your industry, monthly volume, average transaction size, countries, currencies, ecommerce or POS requirements, recurring billing needs, and risk profile.
Underwriting and reserves. Businesses in higher-risk categories should understand how the processor evaluates risk, when reserves may be required, and what circumstances could result in holds or account closure.
Support. Payment problems can stop revenue. Consider whether the provider offers the level of support your business requires and whether complex issues can reach knowledgeable staff.
Technology. Ecommerce merchants may care about APIs, integrations, tokenization, subscription tools, fraud prevention, and international payment methods. Retailers may care more about terminals, POS reliability, inventory integration, and in-person support.
The bottom line
Credit card processing is a coordinated system rather than a single transaction between a merchant and one bank. Authorization happens quickly, settlement happens afterward, and several parties can participate in the economics and risk of each payment.
For merchants, the practical question is not simply “Who has the lowest rate?” It is “Which processor is the best fit for how this business actually gets paid?” A provider that fits your volume, industry, payment channels, geography, risk profile, and support needs is usually more valuable than a provider chosen on a headline rate alone.
This guide is general educational information. Processing terms, network rules, underwriting requirements, and pricing vary by provider and merchant.