National payment processing guide
How Does Credit Card Processing Work?
A card payment is a sequence of messages and financial steps, not one instant transfer. Understanding authorization, capture, clearing, settlement, and reconciliation helps a merchant locate problems and ask the right provider.
The short answer
A payment moves through several participants and checkpoints
The customer presents a card or supported digital credential. The merchant's checkout sends transaction information through its acceptance setup. An authorization request is routed toward the card issuer, which returns an approval or decline. Approved transactions are then captured and submitted for clearing and settlement. The merchant later reconciles sales, adjustments, provider reports, and bank activity.
Participants
Who is involved in a typical card transaction?
Customer and issuer
The customer uses a payment credential. The issuer maintains the card account and decides whether to approve or decline the authorization request using its controls.
Merchant and acceptance system
The merchant starts the transaction through a terminal, point-of-sale system, online checkout, virtual terminal, or another supported channel.
Acquirer and processor
An acquirer provides settlement for eligible merchant transactions. Processors can route or handle transaction messages for merchants, acquirers, or issuers. The same organization may perform more than one role.
Payment network
A card network supplies rules and infrastructure that route transaction information among participating organizations for authorization, clearing, and settlement.
Transaction sequence
From checkout to a reconciled payment
1. Payment is initiated
The merchant enters the amount and the customer presents a credential. The acceptance system prepares the transaction data required by the merchant's configured provider path.
2. Data is protected and transmitted
The system sends the request through the merchant's payment setup. Merchants remain responsible for understanding where card data is stored, processed, or transmitted and for following current PCI requirements.
3. Authorization is requested
The request is routed through the relevant processor and network path to the issuer. The issuer evaluates the request and returns an approval or decline response.
4. The transaction is captured
Capture confirms that an authorized transaction should be submitted for later processing. Some workflows capture immediately; others wait for an order action or a batch close.
5. Clearing and settlement occur
Clearing delivers transaction data and calculates obligations among participants. Settlement transfers the resulting amounts among participating financial institutions. These are distinct steps.
6. The merchant reconciles
The merchant compares transaction records, batches, refunds, adjustments, provider reports, and bank activity. Merchant-facing deposit timing and presentation depend on the account agreement and operating setup.
Operational controls
What should a merchant verify?
Acceptance path
Document which terminal, checkout, gateway, POS system, network connection, and provider portal participate in each sales channel.
Capture and batch rules
Confirm whether capture is automatic or manual, when batches close, who can change settings, and how an unsubmitted transaction appears.
Record identifiers
Keep non-sensitive transaction references, timestamps, batch numbers, order records, and approval responses available for research without copying protected card data.
Reconciliation routine
Compare daily sales with captured transactions, submitted batches, adjustments, and bank activity. Investigate differences using the provider's official reports and support path.
Troubleshooting map
Match the symptom to the stage
No authorization response
Check the terminal or checkout status, connectivity, provider notices, and whether other payment types are affected. Avoid repeatedly submitting the same sale until its status is known.
Approved but not captured
Review the order state, capture controls, open batches, and void or expiration status in the provider's own system.
Captured but absent from a batch
Confirm batch membership, close time, cutoff settings, and whether the transaction appears in a later or separate batch.
Batch and bank activity differ
Reconcile refunds, reversals, adjustments, and provider reports. Use the account-specific report definitions before drawing a conclusion.
Related resources
Continue with the part of the workflow you need
Common questions
Credit card processing FAQ
Does an approval mean the money is final?
No. Approval is an authorization response. Capture, clearing, settlement, merchant crediting, adjustments, and disputes are separate concepts.
Are the processor and card network the same?
Not necessarily. A processor handles or routes transaction data for participants, while a network supplies the infrastructure and rules connecting participants.
Why can two transactions follow different paths?
Sales channel, card type, credential, provider arrangement, capture choice, and account configuration can change the systems and procedures involved.
What information is safest to share with support?
Start with a non-sensitive transaction reference, amount, timestamp, batch number, device or channel, and exact error. Do not send full card numbers, security codes, passwords, bank credentials, or API keys through a general form.
Last editorial review: August 12, 2026. Sources reviewed: current Federal Reserve definitions and commentary, Visa payment-process materials, and PCI SSC merchant security guidance.
Next step
Draw your actual payment path
List each checkout, system, provider handoff, capture rule, report, and support contact. That map gives your team a safer starting point for evaluation and troubleshooting.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US