Credit Card Transaction Flow

Learn the fundamentals of credit card transactions, the complete payment ecosystem, key participants, card components, transaction types, and how credit card payments work in modern financial systems.

Introduction

Every day, billions of dollars are exchanged using credit cards. Whether purchasing groceries, booking airline tickets, shopping online, paying utility bills, or subscribing to streaming services, customers expect payments to complete within seconds.

Behind every successful credit card payment lies a sophisticated financial ecosystem involving multiple organizations that work together securely and efficiently.

A typical credit card transaction involves:

Cardholder
Merchant
Payment Gateway
Payment Processor
Acquiring Bank
Card Network
Issuing Bank

Although customers only see a simple "Payment Successful" message, numerous verification, authentication, authorization, and routing steps occur before a transaction is approved.

Understanding this lifecycle is essential for professionals working in:

Banking
Financial Services
FinTech
Payment Gateways
E-Commerce
Digital Wallets
Retail Platforms

This article focuses on the business domain knowledge of credit card transaction processing rather than implementation details.

Learning Objectives

After completing this article, you will understand:

What is a credit card transaction?
Participants involved in payment processing
Credit card ecosystem
Card components
Card-present vs Card-not-present transactions
Online vs in-store payments
Types of credit card transactions
Business responsibilities of each participant
End-to-end payment flow overview

What is a Credit Card Transaction?

A credit card transaction is the process through which a customer purchases goods or services using a credit card issued by a financial institution.

Instead of paying immediately from a bank account, the issuing bank temporarily pays the merchant on behalf of the customer.

The customer later repays the issuing bank according to the credit card agreement.

Simply put,

A credit card transaction is a short-term credit arrangement between the issuing bank and the customer, facilitated by multiple payment participants.

Real-World Example

Emily visits an online electronics store and purchases a laptop worth $1,250.

She enters:

Credit Card Number
Expiration Date
CVV
Billing Address

Within a few seconds:

The payment request reaches the merchant.
The payment gateway validates the request.
The payment processor forwards the transaction.
Visa routes the request.
Emily's issuing bank verifies her account.
The bank approves the transaction.
The approval travels back to the merchant.

Emily only sees:

Payment Successful

However, numerous organizations participated behind the scenes.

Credit Card Payment Ecosystem

flowchart LR

Cardholder

Cardholder --> Merchant

Merchant --> PaymentGateway

PaymentGateway --> PaymentProcessor

PaymentProcessor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Approval

Approval --> Merchant

Every participant performs a specific business responsibility.

Key Participants

Cardholder

The Cardholder is the customer using the credit card.

Responsibilities:

Initiates payment
Protects card information
Authenticates identity
Repays the issuing bank

Examples:

Online shoppers
Retail customers
Travelers
Corporate employees

Merchant

A Merchant sells products or services and accepts credit card payments.

Responsibilities include:

Accept customer payments
Submit payment requests
Deliver products
Handle refunds
Resolve disputes

Examples:

Amazon
Walmart
Airlines
Restaurants
Hotels

Payment Gateway

The payment gateway securely receives payment information from merchants.

Responsibilities:

Encrypt payment information
Validate requests
Perform fraud screening
Tokenize sensitive data
Route payment requests

The payment gateway does not approve transactions.

Payment Processor

The payment processor acts as the communication bridge between payment gateways and acquiring banks.

Responsibilities include:

Format payment messages
Route transactions
Track processing status
Return responses
Support settlement processing

Acquiring Bank

The acquiring bank provides payment services to merchants.

Responsibilities:

Maintain merchant accounts
Receive transaction requests
Forward requests to card networks
Receive settlement funds
Deposit money into merchant accounts

The acquiring bank represents the merchant during payment processing.

Card Network

Card networks operate the global payment infrastructure.

Popular examples include:

Visa
Mastercard
American Express
Discover

Responsibilities:

Route authorization requests
Define payment standards
Manage interchange rules
Support dispute processing
Enable global interoperability

Card networks do not issue cards directly (except for some closed-loop models).

Issuing Bank

The issuing bank provides the credit card to customers.

Responsibilities include:

Issue credit cards
Verify customer identity
Check available credit
Detect fraud
Approve or decline transactions
Bill customers

Examples include:

Chase
Bank of America
Capital One
Citi
Wells Fargo

How Participants Work Together

flowchart TD

Cardholder

Cardholder --> Merchant

Merchant --> Gateway

Gateway --> Processor

Processor --> Acquirer

Acquirer --> CardNetwork

CardNetwork --> Issuer

Issuer --> Approval

Approval --> Merchant

Merchant --> Cardholder

Each participant performs a specialized business function.

Anatomy of a Credit Card

A credit card contains multiple pieces of information.

Example

----------------------------

BANK NAME

4111 1111 1111 1111

VALID THRU

12/28

CARDHOLDER NAME

CVV

----------------------------

Primary Account Number (PAN)

The Primary Account Number (PAN) uniquely identifies the card.

Example

4111 1111 1111 1111

The PAN identifies:

Issuing bank
Card network
Customer account

Cardholder Name

The printed customer name identifies the authorized card user.

Example

Emily Johnson

Expiration Date

Every credit card has an expiration date.

Example

12 / 28

Expired cards cannot be used for new transactions.

CVV

The Card Verification Value (CVV) is a security code.

Purpose:

Verify physical possession of the card
Reduce online fraud

Merchants should never permanently store CVV values.

EMV Chip

Modern credit cards contain an embedded EMV chip.

Benefits:

Dynamic authentication
Stronger security
Reduced counterfeit fraud
Secure in-store transactions

Contactless Payments

Many cards support contactless payments.

Examples include:

Tap-to-Pay
NFC Payments
Mobile Wallets

Benefits:

Faster checkout
Better customer experience
Reduced physical contact

Digital Wallets

Credit cards may also be stored in digital wallets.

Examples:

Apple Pay
Google Pay
Samsung Wallet

Instead of sharing the real card number, digital wallets generally use payment tokens.

Types of Credit Card Transactions

Credit card transactions can be categorized based on how the payment occurs.

Purchase Transaction

The customer buys products or services.

Examples:

Shopping
Dining
Travel
Utilities

Refund Transaction

The merchant returns money to the customer.

Examples:

Product returned
Order cancellation

Authorization Only

The bank reserves funds without collecting them immediately.

Common industries:

Hotels
Car rentals
Fuel stations

Capture Transaction

Previously authorized funds are collected by the merchant.

Void Transaction

Cancels an authorized transaction before settlement.

Chargeback

The issuing bank reverses a transaction after a customer dispute.

Card-Present Transactions

A Card-Present (CP) transaction occurs when the physical card is available during payment.

Examples:

Grocery stores
Restaurants
Retail stores
Gas stations

Payment methods include:

Chip
Tap
Swipe

Card-Present Flow

flowchart LR

Customer

Customer --> POS

POS --> Merchant

Merchant --> Gateway

Gateway --> Processor

Card-present transactions generally have lower fraud risk.

Card-Not-Present Transactions

A Card-Not-Present (CNP) transaction occurs when the physical card is not presented.

Examples:

Online shopping
Mobile applications
Subscription services
Telephone orders

Instead, customers enter payment information manually.

Card-Not-Present Flow

flowchart LR

Customer

Customer --> Website

Website --> Gateway

Gateway --> Processor

Because the physical card is absent, these transactions typically involve higher fraud risk.

Online vs In-Store Payments

Feature	Online Payment	In-Store Payment
Physical Card	Not Required	Required
Payment Device	Website/App	POS Terminal
Authentication	CVV, OTP, 3DS	Chip, PIN, Tap
Fraud Risk	Higher	Lower
Customer Presence	Remote	Physical

Closed-Loop vs Open-Loop Networks

Open-Loop Network

The card network connects many issuing banks and acquiring banks.

Examples:

Visa
Mastercard

Characteristics:

Global acceptance
Multiple participating banks
Broad merchant network

Closed-Loop Network

The same organization often acts as both the card issuer and network.

Examples:

American Express (selected markets and products)
Discover (selected markets)

Characteristics:

Greater operational control
Integrated customer experience
Direct relationship with cardholders and merchants

Common Credit Card Brands

Brand	Global Acceptance	Typical Use Cases
Visa	Very High	Consumer and Business
Mastercard	Very High	Consumer and Business
American Express	High	Premium Customers
Discover	Moderate	Consumer Markets

Benefits of Credit Cards

Benefits for Customers

Buy now, pay later
Fraud protection
Rewards programs
Global acceptance
Emergency purchasing power

Benefits for Merchants

Higher sales
Faster payments
Global customer reach
Reduced cash handling
Better customer convenience

Benefits for Banks

Interest income
Transaction fees
Customer loyalty
Cross-selling opportunities

Common Business Challenges

Credit card payment ecosystems also face challenges.

Examples include:

Card fraud
Stolen cards
Counterfeit cards
Chargebacks
Network outages
Cross-border regulations
High transaction volumes
Customer disputes

Every participant collaborates to minimize these risks while ensuring a seamless payment experience.

Key Takeaways

A credit card transaction involves multiple organizations working together.
The issuing bank provides credit to the customer.
The acquiring bank supports the merchant.
Card networks securely route payment messages.
Payment gateways and processors enable secure communication.
Card-present and card-not-present transactions have different risk profiles.
Modern credit cards support EMV chips, contactless payments, and digital wallets.
Understanding the ecosystem is essential before learning the authorization, clearing, and settlement lifecycle.

Business Interview Questions

What is a credit card transaction?
Who are the major participants in a credit card payment ecosystem?
What is the role of an issuing bank?
What is the role of an acquiring bank?
What responsibilities does a card network perform?
What is the difference between a payment gateway and a payment processor?
What information is stored on a credit card?
What is the difference between card-present and card-not-present transactions?
What are open-loop and closed-loop payment networks?
Why are EMV chips more secure than magnetic stripe cards?

Credit Card Authorization Flow

After understanding the participants involved in a credit card payment ecosystem, the next step is learning how a transaction is authorized.

Authorization is one of the most important phases of a credit card transaction because it determines whether the customer has sufficient available credit and whether the transaction should be approved or declined.

Most authorization requests are completed within 2–5 seconds, even though multiple organizations participate in the process.

What is Authorization?

Authorization is the process where the issuing bank verifies whether a credit card transaction is valid and reserves the required amount from the customer's available credit limit.

Authorization answers questions such as:

Is the card valid?
Is the card active?
Has the card expired?
Is sufficient credit available?
Does the transaction appear fraudulent?
Should the payment be approved?

Important: Authorization does not transfer money. It only reserves the credit limit for the transaction amount.

Complete Authorization Flow

flowchart LR

Customer

Customer --> Merchant

Merchant --> PaymentGateway

PaymentGateway --> PaymentProcessor

PaymentProcessor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Approval

Approval --> CardNetwork

CardNetwork --> AcquiringBank

AcquiringBank --> PaymentProcessor

PaymentProcessor --> PaymentGateway

PaymentGateway --> Merchant

Merchant --> Customer

Authorization Lifecycle

The authorization process consists of several business steps.

Customer initiates payment
Merchant validates the order
Payment gateway receives the request
Tokenization and encryption
Fraud screening
Payment processor forwards the request
Acquiring bank receives the transaction
Card network routes the request
Issuing bank performs authorization
Authorization response returns
Merchant receives approval
Customer receives confirmation

Step 1 – Customer Initiates Payment

The payment process begins when the customer chooses to pay using a credit card.

Example

Emily purchases a laptop worth $1,250.

She enters:

Card Number
Expiration Date
CVV
Billing Address

The merchant creates a payment request.

Payment Information Collected

Typical payment details include:

Field	Example
Merchant ID	MID-10025
Order ID	ORD-450012
Transaction Amount	$1,250
Currency	USD
Card Number	** ** 1234
Expiration Date	12/28
CVV	***
Billing ZIP	78240

Step 2 – Merchant Validation

Before contacting financial institutions, merchants perform basic validation.

Examples include:

Product availability
Valid shopping cart
Correct amount
Customer account verification
Shipping information
Duplicate order detection

If validation fails, no authorization request is sent.

Step 3 – Payment Gateway Receives Request

The merchant forwards the payment request to the payment gateway.

Gateway responsibilities include:

Validate request structure
Authenticate merchant
Encrypt payment information
Generate transaction identifiers
Prepare routing

The gateway acts as the secure entry point into the payment ecosystem.

Gateway Validation

The payment gateway performs several checks.

Examples include:

Merchant account active
Supported currency
Required fields present
Transaction limits
Valid payment method
Correct request format

Invalid requests are rejected immediately.

Step 4 – Encryption

Sensitive information is encrypted before transmission.

flowchart LR

CardData

CardData --> Encryption

Encryption --> SecureTransmission

SecureTransmission --> Gateway

Protected information includes:

Card Number
CVV
Customer Information
Billing Address

Encryption protects payment information during communication.

Step 5 – Tokenization

Many payment gateways replace the actual card number with a payment token.

Example

Card Number

4111111111111111

↓

Payment Token

TK_72HFD91AB

Benefits include:

Improved security
Reduced PCI DSS scope
Safer recurring payments
Lower fraud exposure

Step 6 – Fraud Screening

Before contacting banks, fraud checks are performed.

Common fraud checks include:

Velocity rules
Device fingerprint
IP reputation
Billing and shipping mismatch
High-risk country
Merchant fraud rules
Customer history

Transactions identified as suspicious may require additional verification.

Example Fraud Detection

Customer

↓

15 Transactions

↓

2 Minutes

↓

Review Required

Step 7 – Payment Processor

The payment processor receives the transaction from the gateway.

Responsibilities include:

Standardize payment messages
Select communication channels
Track transaction status
Manage processor routing
Return authorization responses

Processors communicate with acquiring banks.

Step 8 – Acquiring Bank

The acquiring bank represents the merchant.

Responsibilities include:

Receive payment request
Verify merchant account
Forward authorization request
Receive approval
Support merchant settlement

The acquiring bank does not decide whether a transaction is approved.

Step 9 – Card Network

Card networks act as the global payment infrastructure.

Examples:

Visa
Mastercard
American Express
Discover

Responsibilities include:

Route authorization requests
Apply network rules
Format payment messages
Maintain interoperability

Card Network Flow

flowchart LR

AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

Step 10 – Issuing Bank Authorization

The issuing bank performs the most important decision.

Typical verification includes:

Card active
Card expired?
Available credit
Daily limits
Fraud detection
Customer authentication
Card blocked?
Account standing

The bank decides:

Approve
Decline
Request Authentication

Authorization Decision

flowchart TD

AuthorizationRequest

AuthorizationRequest --> CardValid

CardValid --> CreditAvailable

CreditAvailable --> FraudCheck

FraudCheck --> Decision

Decision --> Approved

Decision --> Declined

Available Credit Check

Suppose a customer has:

Credit Limit

$10,000

Current Balance

$7,900

Available Credit

$2,100

Purchase Amount

$1,250

Result

Approved

Because sufficient credit exists.

Authorization Hold

Once approved, the issuing bank places an authorization hold.

Example

Credit Limit

$10,000

Available Credit Before Purchase

$8,500

Purchase

$600

Available Credit After Authorization

$7,900

Money has not yet moved.

Only the available credit has been reserved.

Common Decline Reasons

Transactions may be declined for many reasons.

Decline Reason	Explanation
Insufficient Credit	Available credit too low
Expired Card	Card no longer valid
Incorrect CVV	Security verification failed
Fraud Suspected	High-risk transaction
Card Blocked	Lost or stolen card
Daily Limit Exceeded	Spending restriction
Incorrect PIN	Authentication failure
Issuer Unavailable	Temporary bank issue

Authorization Response

The issuing bank returns an authorization response.

Possible responses include:

Approved
Declined
Authentication Required
Call Issuer
Pick Up Card
Do Not Honor

The response follows the reverse path.

flowchart LR

IssuingBank

IssuingBank --> CardNetwork

CardNetwork --> AcquiringBank

AcquiringBank --> Processor

Processor --> Gateway

Gateway --> Merchant

Customer Notification

The merchant receives the authorization result.

Customer sees:

Payment Successful

Payment Declined

If approved:

Inventory reserved
Order confirmed
Receipt generated
Shipment preparation begins

Authorization Timeout

Occasionally the issuing bank does not respond.

Possible reasons:

Network failure
Bank maintenance
Communication timeout
Infrastructure outage

The payment gateway determines the next action.

Retry Logic

Temporary failures may trigger retries.

flowchart LR

Failure

Failure --> Retry

Retry --> Success

Retry --> Failure

Retry is appropriate for:

Timeout
Temporary processor outage
Network interruption

Retry should not occur for:

Expired card
Fraud decline
Invalid card
Insufficient credit

Smart Routing

Some payment providers support intelligent routing.

flowchart TD

Gateway

Gateway --> ProcessorA

Gateway --> ProcessorB

Gateway --> ProcessorC

Routing decisions may consider:

Processor availability
Geographic region
Card brand
Currency
Historical success rate

Smart routing improves authorization rates.

Idempotency

Customers sometimes click the Pay button multiple times.

Without idempotency:

Click

↓

Click Again

↓

Click Again

↓

Three Transactions

With idempotency:

Click

↓

Duplicate Request

↓

Existing Transaction

↓

Return Previous Response

Idempotency prevents duplicate charges.

Duplicate Transaction Detection

Payment systems identify duplicate requests using:

Transaction ID
Order ID
Merchant ID
Customer ID
Timestamp
Idempotency Key

Authorization Response Codes

Response	Business Meaning
00	Approved
05	Do Not Honor
14	Invalid Card Number
51	Insufficient Funds or Credit
54	Expired Card
57	Transaction Not Permitted
91	Issuer Unavailable

Response codes help merchants determine the appropriate next action.

Real-World Example

Emma purchases a smartphone worth $950 from an online retailer.

The following sequence occurs:

Emma submits her card information.
The merchant validates the order.
The payment gateway encrypts and tokenizes the payment data.
Fraud screening is performed.
The payment processor forwards the request.
The acquiring bank sends the request to Visa.
Visa routes the authorization request to Emma's issuing bank.
The issuing bank verifies the card, available credit, and fraud indicators.
The bank approves the transaction and places an authorization hold.
The approval response travels back through Visa, the acquiring bank, the processor, and the gateway.
The merchant confirms the order.
Emma sees Payment Successful within a few seconds.

Key Takeaways

Authorization determines whether a transaction should be approved.
No money moves during authorization; only credit is reserved.
The issuing bank makes the final authorization decision.
Payment gateways secure and validate requests before routing them.
Fraud screening helps reduce financial losses.
Smart routing improves payment success rates.
Retry logic handles temporary failures.
Idempotency prevents duplicate charges.

Business Interview Questions

What is credit card authorization?
Why is authorization different from settlement?
What is an authorization hold?
What validations occur before an authorization request reaches the issuing bank?
What responsibilities does the payment gateway perform during authorization?
How does the issuing bank determine whether to approve a transaction?
What are common reasons for authorization declines?
What is smart routing in payment processing?
Why is idempotency important in credit card transactions?
How does fraud screening improve authorization success and security?

Capture, Clearing, and Settlement

Authorization is only the first phase of a credit card transaction.

After a transaction is authorized, the merchant still has not received the money.

Several additional financial processes occur before funds reach the merchant's bank account:

Capture
Batch Processing
Clearing
Settlement
Merchant Funding
Reconciliation

These processes involve acquiring banks, card networks, issuing banks, and payment processors working together to move money securely.

Transaction Lifecycle Overview

flowchart LR

Customer

Customer --> Authorization

Authorization --> Capture

Capture --> Clearing

Clearing --> Settlement

Settlement --> MerchantFunding

MerchantFunding --> Reconciliation

Authorization reserves funds.

Settlement transfers funds.

Authorization vs Capture

Many people confuse authorization and capture.

They are two different business events.

Authorization	Capture
Verifies card	Collects approved funds
Checks available credit	Initiates financial movement
Places authorization hold	Converts hold into payment
No money transferred	Settlement process begins
Usually completed in seconds	May occur immediately or later

Why Separate Authorization and Capture?

Separating these steps provides flexibility for merchants.

Examples include:

Hotels
Airlines
Car Rentals
Restaurants
Online Retailers

A merchant may want to:

Verify the card today
Ship products tomorrow
Capture payment only after shipment

This reduces unnecessary refunds and improves customer experience.

Real-World Example

Sarah purchases a television worth $950.

Day 1

Merchant requests authorization.
Issuing bank approves.
$950 is reserved from Sarah's available credit.

Day 2

Merchant ships the television.

Merchant sends a capture request.

Day 3

Settlement begins.

Merchant receives payment according to the settlement schedule.

What is Capture?

Capture is the process where the merchant confirms that previously authorized funds should now be collected.

The merchant tells the acquiring bank:

"Please collect the funds that were authorized earlier."

Only captured transactions proceed to settlement.

Capture Flow

flowchart LR

Merchant

Merchant --> PaymentGateway

PaymentGateway --> PaymentProcessor

PaymentProcessor --> AcquiringBank

AcquiringBank --> Settlement

Immediate Capture

Many businesses capture immediately after authorization.

Examples:

Grocery Stores
Fuel Stations
Fast Food
Convenience Stores

Business Flow

Authorization

↓

Capture

↓

Settlement

Delayed Capture

Some merchants delay capture.

Examples:

Industry	Reason
Hotels	Final bill unknown
Airlines	Ticket confirmation
Car Rentals	Final rental amount
Online Shopping	Wait until shipment
Furniture	Backordered inventory

Partial Capture

Sometimes merchants capture less than the authorized amount.

Example

Authorized Amount

$500

Captured Amount

$420

Unused authorization

$80

The remaining authorization is released back to the customer's available credit.

Multiple Capture

Some industries capture multiple times.

Example

Hotel Stay

Authorization

↓

Room Charges

↓

Restaurant Charges

↓

Laundry Charges

↓

Final Capture

This depends on merchant agreements and network rules.

Authorization Expiration

Authorization holds do not remain forever.

If capture is not performed within the allowed time, the authorization expires.

Consequences include:

Reserved credit released
Merchant must request new authorization
Possible customer inconvenience

Batch Processing

Merchants typically do not settle every transaction individually.

Instead, they collect transactions into batches.

flowchart LR

Transaction1

Transaction1 --> Batch

Transaction2 --> Batch

Transaction3 --> Batch

Batch --> Settlement

Batch processing improves efficiency.

Why Batch Processing?

Benefits include:

Lower processing costs
Reduced network traffic
Easier reconciliation
Operational efficiency

Most merchants submit settlement batches several times per day.

Batch Closing

At scheduled times:

The merchant sends all approved transactions to the acquiring bank.

Example

Morning Sales

+

Afternoon Sales

+

Evening Sales

↓

Settlement Batch

Clearing

After capture, the transaction enters the Clearing phase.

Clearing is the process of exchanging financial information between financial institutions before money is transferred.

During clearing:

Transaction records are exchanged.
Fees are calculated.
Settlement amounts are determined.
Banks validate payment information.

Clearing Flow

flowchart LR

Merchant

Merchant --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

Information Exchanged During Clearing

Examples include:

Transaction Amount
Merchant ID
Card Number (Tokenized)
Currency
Authorization Code
Settlement Date
Transaction Timestamp

Settlement

Settlement is the movement of money between financial institutions.

Unlike authorization, settlement transfers actual funds.

flowchart LR

IssuingBank

IssuingBank --> CardNetwork

CardNetwork --> AcquiringBank

AcquiringBank --> Merchant

Settlement Timeline

A typical timeline looks like this:

Day	Activity
Day 1	Authorization
Day 1	Capture
Day 2	Clearing
Day 2–3	Settlement
Day 2–4	Merchant Funding

Actual timing depends on:

Card Network
Merchant Agreement
Country
Banking Holidays
Payment Method

Merchant Funding

After settlement, the acquiring bank deposits money into the merchant's account.

Example

Customer Purchase

$1,000

Merchant Fees

$25

Merchant Receives

$975

Settlement Account

Merchants maintain a settlement account.

Funds received include:

Sales
Refund Adjustments
Chargeback Adjustments
Processing Fees

Finance teams reconcile these amounts daily.

Merchant Discount Rate (MDR)

Merchants pay a fee for accepting credit card payments.

This fee is known as the Merchant Discount Rate (MDR).

Example

Purchase Amount

$500

MDR

2.5%

Merchant Receives

$487.50

Components of MDR

Merchant Discount Rate typically includes:

Interchange Fee
Assessment Fee
Processor Fee
Gateway Fee
Acquirer Margin

Interchange Fee

The Interchange Fee is paid to the issuing bank.

Purpose:

Compensate the issuer
Cover fraud risk
Fund rewards programs
Support payment infrastructure

Interchange varies based on:

Card Type
Merchant Category
Country
Transaction Type

Assessment Fee

Assessment fees are charged by the card network.

Examples:

Visa Network Fee
Mastercard Assessment

Purpose:

Maintain network infrastructure
Support global payment systems
Fund compliance programs

Processor Fee

Payment processors charge merchants for processing services.

Examples include:

Transaction routing
Message formatting
Operational support
Reporting
Settlement services

Gateway Fee

Payment gateways may charge fees for:

Secure payment processing
Tokenization
Fraud screening
Merchant dashboard
API usage

Settlement Example

Customer Purchase

$1,000

Interchange Fee

$16

Assessment Fee

Gateway Fee

Processor Fee

Merchant Receives

$975

Cross-Border Settlement

International payments involve additional complexity.

Additional considerations include:

Currency Conversion
Foreign Exchange
Local Banking Regulations
Cross-Border Fees
Tax Requirements

Settlement timelines may also be longer.

Settlement Risks

Settlement involves several operational risks.

Examples include:

Processor Outages
Banking Delays
Network Failures
Duplicate Settlement
Currency Fluctuations

Payment providers continuously monitor settlement health.

End-of-Day Reconciliation

Finance teams compare records across multiple systems.

Typical reconciliation compares:

Merchant Orders
Gateway Transactions
Processor Reports
Bank Statements
Settlement Reports

Any mismatch requires investigation.

Reconciliation Flow

flowchart TD

MerchantOrders

MerchantOrders --> Compare

GatewayReports --> Compare

ProcessorReports --> Compare

BankStatement --> Compare

Compare --> ReconciliationReport

Common Reconciliation Issues

Examples include:

Issue	Possible Cause
Missing Transaction	Batch failure
Duplicate Payment	Retry issue
Settlement Difference	Fees deducted
Refund Mismatch	Timing difference
Currency Difference	Exchange rate

Importance of Daily Reconciliation

Benefits include:

Detect financial discrepancies
Identify failed settlements
Track chargebacks
Verify merchant funding
Support financial audits
Improve reporting accuracy

Business KPIs

Finance and operations teams monitor settlement performance.

Important metrics include:

KPI	Description
Settlement Time	Time until merchant receives funds
Funding Success Rate	Successful merchant deposits
Batch Success Rate	Successful batch processing
Reconciliation Accuracy	Matching transaction records
Average Settlement Value	Average funds transferred
Processing Cost	Total transaction fees
Settlement Exceptions	Transactions requiring manual review

Real-World Example

An online retailer processes 20,000 credit card payments during a holiday sale.

Customers complete purchases throughout the day.
Each transaction is authorized instantly.
Orders ready for shipment are captured.
At the end of the day, transactions are grouped into settlement batches.
The acquiring bank sends batch details to the card network.
The card network coordinates clearing with issuing banks.
Issuing banks transfer settlement funds.
The acquiring bank deposits the net amount into the merchant's account after deducting agreed fees.
The retailer reconciles settlement reports against internal order records.

Although customers receive instant order confirmations, the movement of money occurs later through clearing and settlement.

Key Takeaways

Authorization reserves credit; capture initiates payment collection.
Only captured transactions enter clearing and settlement.
Batch processing improves efficiency and reduces processing costs.
Clearing exchanges financial information between participating institutions.
Settlement transfers actual funds from issuing banks to acquiring banks.
Merchant funding occurs after settlement, usually according to agreed schedules.
Merchant Discount Rate (MDR) consists of interchange, assessment, processor, and gateway fees.
Daily reconciliation ensures financial accuracy and operational transparency.

Business Interview Questions

What is the difference between authorization and capture?
Why do some merchants delay capture?
What happens if an authorization expires before capture?
What is batch processing, and why is it important?
What activities occur during the clearing process?
How does settlement differ from clearing?
What is Merchant Discount Rate (MDR)?
What are the major components of MDR?
Why is reconciliation important for merchants?
What operational risks can affect settlement?

Refunds, Voids, Chargebacks, and Transaction Exceptions

Not every credit card transaction ends successfully.

Customers may:

Cancel orders
Return products
Dispute transactions
Report fraud
Claim duplicate charges

Similarly, merchants may:

Cancel shipments
Process refunds
Reverse authorizations
Respond to chargebacks

The payment ecosystem includes well-defined processes to handle these situations while protecting both customers and merchants.

Transaction Exception Lifecycle

flowchart LR

Purchase

Purchase --> Authorization

Authorization --> Capture

Capture --> Settlement

Settlement --> Refund

Settlement --> Chargeback

Authorization --> Void

Types of Transaction Exceptions

Exception	Purpose
Void	Cancel before settlement
Refund	Return money after settlement
Chargeback	Forced reversal initiated by issuer
Retrieval Request	Request transaction evidence
Representment	Merchant challenges chargeback
Arbitration	Card network makes final decision

What is a Void Transaction?

A Void cancels an authorized transaction before settlement.

Since money has not yet moved, the authorization hold is released.

Example:

A customer orders a laptop but immediately cancels the order.

The merchant voids the authorization.

The customer's available credit is restored.

Void Flow

flowchart LR

Authorization

Authorization --> Merchant

Merchant --> Void

Void --> IssuingBank

IssuingBank --> ReleaseHold

Characteristics of a Void

Occurs before settlement
No money transferred
Authorization hold removed
Faster than refunds
Usually invisible on the customer's statement after processing

What is a Refund?

A Refund returns money to the customer after settlement has completed.

Unlike a void, funds have already reached the merchant.

The merchant must initiate a new transaction to return the money.

Refund Flow

flowchart LR

Merchant

Merchant --> Gateway

Gateway --> Processor

Processor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Customer

Common Refund Scenarios

Product returned
Duplicate payment
Wrong item shipped
Service cancellation
Billing error
Order not fulfilled

Full Refund

Entire transaction amount is returned.

Example

Purchase

$250

Refund

$250

Customer receives the full amount.

Partial Refund

Only part of the payment is returned.

Example

Purchase

$800

Returned Item

$150

Refund

$150

The remaining payment remains unchanged.

Multiple Refunds

Some merchants issue several refunds against one transaction.

Example

Purchase

$1,000

Refund 1

$200

Refund 2

$300

Remaining Amount

$500

Refund Timeline

Typical refund timeline

Step	Activity
Day 1	Customer requests refund
Day 1	Merchant approves
Day 2	Refund submitted
Day 3–5	Bank credits customer

Actual timing depends on:

Card issuer
Card network
Banking holidays
Merchant agreement

Void vs Refund

Void	Refund
Before settlement	After settlement
Releases authorization	Returns transferred funds
Faster	Usually slower
No money movement	Money transferred back
Removes authorization hold	Creates refund transaction

What is a Chargeback?

A Chargeback is a payment reversal initiated by the issuing bank after a customer disputes a transaction.

The bank temporarily removes funds from the merchant while the dispute is investigated.

Why Chargebacks Occur

Common reasons include:

Unauthorized transaction
Product not received
Service not delivered
Duplicate billing
Incorrect amount charged
Fraud
Subscription cancellation issues

Chargeback Flow

flowchart LR

Customer

Customer --> IssuingBank

IssuingBank --> CardNetwork

CardNetwork --> AcquiringBank

AcquiringBank --> Merchant

Chargeback Lifecycle

flowchart TD

CustomerDispute

CustomerDispute --> Issuer

Issuer --> Chargeback

Chargeback --> Merchant

Merchant --> Representment

Representment --> Issuer

Issuer --> FinalDecision

Step 1 – Customer Dispute

Customer contacts the issuing bank.

Example

"I don't recognize this transaction."

"I never received the product."

Step 2 – Issuing Bank Investigation

The issuer reviews:

Customer history
Transaction details
Merchant category
Fraud indicators

If appropriate, a chargeback is initiated.

Step 3 – Merchant Notification

The merchant receives:

Chargeback reason
Transaction details
Response deadline
Required documentation

Step 4 – Representment

The merchant may challenge the chargeback.

Evidence may include:

Delivery confirmation
Signed receipt
Invoice
Customer communication
Tracking information
Authentication logs

Step 5 – Final Decision

Possible outcomes:

Customer wins
Merchant wins

If the merchant successfully proves the transaction was valid, funds may be returned.

Retrieval Request

Sometimes the issuing bank requests information before initiating a chargeback.

Examples requested:

Sales receipt
Invoice
Shipment tracking
Proof of delivery

This is called a Retrieval Request.

Arbitration

If the merchant and issuing bank disagree, the dispute may be escalated.

The card network reviews:

Merchant evidence
Customer evidence
Network rules

The card network issues the final decision.

Common Chargeback Reason Categories

Category	Example
Fraud	Unauthorized card use
Authorization	Invalid approval
Processing Error	Duplicate billing
Consumer Dispute	Product not received
Credit Not Processed	Refund missing
Cardholder Dispute	Service dissatisfaction

Friendly Fraud

Friendly fraud occurs when a legitimate customer disputes a valid purchase.

Example

Customer:

Receives product

↓

Uses product

↓

Requests chargeback

↓

Claims transaction was unauthorized

This creates financial loss for merchants.

First-Party vs Third-Party Fraud

Fraud Type	Description
First-Party Fraud	Legitimate customer misuses dispute process
Third-Party Fraud	Criminal uses stolen card information

Lost or Stolen Card

If a customer reports a card as lost or stolen:

Issuer blocks the card
Replacement card is issued
Future transactions are declined
Fraud monitoring increases

Expired Card

Transactions using expired cards are typically declined.

Customers must update payment information.

Common example:

Subscription renewal fails because the stored card has expired.

Duplicate Transactions

Duplicate charges may occur due to:

Customer clicking twice
Network retries
POS communication failure
Merchant system error

Payment systems use:

Transaction IDs
Idempotency Keys
Duplicate detection rules

to prevent duplicate billing.

EMV Liability Shift

EMV chip technology significantly reduced counterfeit card fraud.

General principle:

If the merchant does not support EMV when required, the merchant may bear liability for certain counterfeit fraud.
If EMV is properly used, liability often shifts according to card network rules.

This encourages merchants to adopt secure payment terminals.

Transaction Statuses

Status	Description
Authorized	Credit reserved
Captured	Funds requested
Settled	Money transferred
Voided	Authorization cancelled
Refunded	Money returned
Charged Back	Disputed transaction
Reversed	Transaction cancelled

Merchant Best Practices

Successful merchants:

Process refunds promptly
Respond to chargebacks quickly
Maintain detailed transaction records
Use fraud prevention tools
Implement 3-D Secure where applicable
Verify customer identity when appropriate
Monitor suspicious transaction patterns
Reconcile payments daily

Chargeback Prevention

Merchants can reduce chargebacks by:

Providing accurate product descriptions
Shipping promptly
Offering responsive customer support
Sending order confirmations
Using delivery tracking
Clearly displaying billing descriptors
Detecting fraud before authorization

Business KPIs

Payment operations teams monitor:

KPI	Description
Refund Rate	Percentage of refunded transactions
Chargeback Rate	Percentage of disputed transactions
Fraud Rate	Fraudulent transaction percentage
Dispute Win Rate	Merchant success in representment
Duplicate Transaction Rate	Duplicate payment frequency
Average Refund Time	Time to complete refunds
Customer Complaint Rate	Support issues related to payments

Real-World Scenario

A customer purchases a $600 smartphone from an online retailer.

Scenario 1 – Customer Cancels Immediately

The order has not shipped.

Merchant performs a Void.

Authorization hold is released.

Scenario 2 – Customer Returns Product

The phone is delivered and later returned.

Merchant issues a Refund.

Customer receives $600 back after the refund is processed.

Scenario 3 – Customer Claims Unauthorized Purchase

The customer contacts the issuing bank.

A Chargeback is initiated.

The merchant submits:

Shipping confirmation
Delivery signature
Order invoice
Customer communication

The issuing bank reviews the evidence and makes a decision based on applicable card network rules.

Key Takeaways

A Void cancels an authorized transaction before settlement.
A Refund returns money after settlement has completed.
A Chargeback is initiated by the issuing bank after a customer dispute.
Retrieval requests allow issuers to request additional evidence before escalating disputes.
Representment gives merchants the opportunity to challenge chargebacks.
EMV chip technology helps reduce counterfeit card fraud.
Strong fraud prevention, clear customer communication, and accurate records reduce payment disputes.

Business Interview Questions

What is the difference between a void and a refund?
When should a merchant issue a refund instead of a void?
What is a chargeback?
What are the most common reasons for chargebacks?
What is a retrieval request?
What is representment?
How does arbitration work in card payment disputes?
What is friendly fraud?
What is the EMV liability shift?
Which KPIs help merchants measure payment exception performance?

Credit Card Transaction Glossary, Comparison Tables, and Complete Lifecycle Summary

Congratulations! You have completed the Credit Card Transaction Flow series. This final chapter summarizes all key concepts discussed throughout the article and serves as a quick reference for professionals preparing for interviews or working in Banking, Financial Services, FinTech, and Payment Systems.

Complete Credit Card Transaction Lifecycle

flowchart LR

Customer

Customer --> Merchant

Merchant --> PaymentGateway

PaymentGateway --> PaymentProcessor

PaymentProcessor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Authorization

Authorization --> Merchant

Merchant --> Capture

Capture --> Clearing

Clearing --> Settlement

Settlement --> MerchantFunding

Complete Payment Lifecycle

flowchart TD

Purchase

Purchase --> Authorization

Authorization --> Capture

Capture --> Clearing

Clearing --> Settlement

Settlement --> Funding

Funding --> Reconciliation

Settlement --> Refund

Settlement --> Chargeback

Participants in the Credit Card Ecosystem

Participant	Primary Responsibility
Cardholder	Initiates purchase and repays issuer
Merchant	Sells goods/services and accepts payments
Payment Gateway	Secures, validates, and routes payment requests
Payment Processor	Exchanges payment messages between parties
Acquiring Bank	Represents the merchant and receives settlement funds
Card Network	Routes authorization and settlement messages
Issuing Bank	Issues cards and approves or declines transactions

Credit Card Transaction Timeline

Stage	Activity
1	Customer initiates payment
2	Merchant validates order
3	Gateway encrypts and tokenizes data
4	Fraud screening performed
5	Processor forwards request
6	Acquirer sends request to network
7	Network routes to issuer
8	Issuer authorizes transaction
9	Authorization response returned
10	Merchant captures funds
11	Clearing performed
12	Settlement completed
13	Merchant receives funding
14	Daily reconciliation

Authorization vs Capture vs Settlement

Feature	Authorization	Capture	Settlement
Purpose	Reserve available credit	Confirm collection of funds	Transfer money
Money Movement	No	Begins process	Yes
Customer Credit	Reserved	Still reserved	Reduced
Merchant Receives Money	No	No	Yes
Typical Time	Seconds	Seconds to days	1–3 business days

Authorization Hold

flowchart LR

AvailableCredit

AvailableCredit --> Authorization

Authorization --> HoldPlaced

HoldPlaced --> Capture

Capture --> Settlement

An authorization hold temporarily reduces the customer's available credit until the transaction is captured or expires.

Payment Gateway vs Payment Processor

Payment Gateway	Payment Processor
Collects payment information	Routes payment messages
Encrypts sensitive data	Connects with acquiring bank
Performs tokenization	Exchanges financial messages
Executes fraud screening	Supports clearing and settlement
Returns merchant-friendly responses	Returns processor responses

Acquiring Bank vs Issuing Bank

Acquiring Bank	Issuing Bank
Works for the merchant	Works for the customer
Maintains merchant account	Issues credit card
Receives settlement	Pays merchant through network
Handles merchant onboarding	Handles customer credit
Supports merchant funding	Bills the cardholder

Card Network Responsibilities

Examples:

Visa
Mastercard
American Express
Discover

Responsibilities:

Route authorization requests
Define payment rules
Calculate interchange
Support dispute resolution
Coordinate settlement
Maintain global interoperability

Transaction Types

Transaction	Description
Purchase	Customer buys goods or services
Authorization	Reserve available credit
Capture	Confirm payment collection
Settlement	Transfer funds
Refund	Return money to customer
Void	Cancel before settlement
Chargeback	Forced payment reversal
Reversal	Cancel authorization or transaction

Card Present vs Card Not Present

Card Present	Card Not Present
Physical card available	Physical card absent
EMV Chip	Manual entry
Lower fraud risk	Higher fraud risk
Retail Stores	Online Shopping
Restaurants	Mobile Applications
POS Terminal	Website

Credit Card vs Debit Card

Credit Card	Debit Card
Uses bank-issued credit	Uses customer's bank balance
Customer repays later	Funds deducted immediately
Credit limit available	Bank balance required
Monthly statement	Immediate account debit
Interest may apply	No credit interest

Open Loop vs Closed Loop Networks

Open Loop	Closed Loop
Multiple issuing banks	Same organization often acts as issuer and network
Multiple acquiring banks	Direct merchant relationships
Examples: Visa, Mastercard	Examples: American Express, Discover (selected markets)
Broad global acceptance	More integrated ecosystem

Tokenization vs Encryption

Tokenization	Encryption
Replaces sensitive data	Converts data into ciphertext
Reduces PCI scope	Protects data confidentiality
Safe for storage	Used during storage and transmission
Original value stored securely in a vault	Original value recovered with decryption keys

Refund vs Void

Refund	Void
After settlement	Before settlement
Money returned	Authorization cancelled
Customer receives refund	Hold released
Creates refund transaction	No financial settlement

Chargeback Lifecycle

flowchart TD

CustomerDispute

CustomerDispute --> Issuer

Issuer --> Chargeback

Chargeback --> Merchant

Merchant --> Representment

Representment --> Arbitration

Arbitration --> FinalDecision

Fraud Prevention Techniques

Common techniques include:

Tokenization
Encryption
EMV Chips
CVV Verification
3-D Secure
Velocity Checks
Device Fingerprinting
Geolocation Analysis
AI-Based Fraud Detection
Risk Scoring

Common Response Codes

Response	Meaning
00	Approved
05	Do Not Honor
14	Invalid Card Number
51	Insufficient Credit
54	Expired Card
57	Transaction Not Permitted
91	Issuer Unavailable

Merchant Daily Activities

Typical operational activities include:

Monitor payment success rate
Review failed transactions
Process refunds
Respond to chargebacks
Perform reconciliation
Review fraud alerts
Generate settlement reports
Monitor processor health

Merchant KPIs

KPI	Description
Authorization Rate	Approved transactions
Payment Success Rate	Completed payments
Fraud Rate	Fraud percentage
Chargeback Rate	Customer disputes
Refund Rate	Refunded transactions
Settlement Time	Time until merchant funding
Reconciliation Accuracy	Matching financial records
Average Transaction Value	Average purchase amount

Common Business Challenges

Payment organizations manage challenges such as:

Card fraud
Processor outages
Bank downtime
Duplicate transactions
Chargebacks
International regulations
Currency conversion
Cross-border payments
Network latency
Peak transaction volumes

End-to-End Business Scenario

A customer purchases a $800 laptop using a credit card.

The customer enters payment details on the merchant's website.
The payment gateway encrypts and tokenizes the card data.
Fraud checks are performed.
The payment processor forwards the request to the acquiring bank.
The card network routes the request to the issuing bank.
The issuing bank approves the transaction and places an authorization hold.
The approval travels back through the payment ecosystem.
The merchant confirms the order.
Once the laptop ships, the merchant captures the payment.
The transaction enters clearing and settlement.
The acquiring bank receives funds and deposits the net amount into the merchant's account.
Finance teams reconcile transaction records with settlement reports.
If the customer later returns the laptop, the merchant issues a refund. If the customer disputes the charge, the chargeback process begins.

This sequence illustrates the complete lifecycle of a typical credit card transaction.

Learning Checklist

After completing this series, you should be able to explain:

✅ Credit card payment ecosystem
✅ Roles of issuers, acquirers, gateways, processors, and card networks
✅ Card-present vs card-not-present transactions
✅ Authorization process
✅ Authorization holds
✅ Capture process
✅ Clearing and settlement
✅ Merchant funding
✅ Merchant Discount Rate (MDR)
✅ Refunds and voids
✅ Chargebacks and dispute resolution
✅ Fraud prevention techniques
✅ Tokenization and encryption
✅ Payment reconciliation
✅ Key payment metrics and operational KPIs

Business Interview Questions

Fundamentals

Explain the complete credit card transaction lifecycle.
What are the roles of the issuing bank and acquiring bank?
How does a card network differ from a payment processor?
What is the purpose of a payment gateway?
What information is validated during authorization?

Authorization

What is an authorization hold?
Why doesn't authorization transfer money?
What are common reasons for transaction declines?
How does tokenization improve security?
What is idempotency in payment processing?

Settlement

What is the difference between capture and settlement?
Why do merchants use batch processing?
What happens during clearing?
What is Merchant Discount Rate (MDR)?
What are interchange and assessment fees?

Exceptions

What is the difference between a void and a refund?
What is a chargeback?
What is representment?
What is arbitration?
What is friendly fraud?

Operations

What KPIs are most important for payment operations?
How do merchants reduce chargebacks?
Why is reconciliation performed daily?
How do payment gateways detect fraud?
What operational risks exist in payment systems?

Series Summary

Congratulations! You have completed Credit Card Transaction Flow, one of the most important topics in the Payment Domain Knowledge series.

You now understand:

The complete credit card payment ecosystem
Roles and responsibilities of every participant
Authorization, capture, clearing, and settlement
Merchant funding and reconciliation
Refunds, voids, and chargebacks
Fraud prevention and security controls
Operational metrics and business KPIs
Real-world payment scenarios
Business interview preparation

These concepts provide the foundation for understanding enterprise payment platforms used by banks, card networks, payment gateways, and FinTech companies.

24-DebitCardTransactionFlow.md

In the next article, you'll learn:

What is a debit card transaction?
Debit card ecosystem
Debit card vs credit card
PIN-based vs signature-based debit
Authorization flow
Real-time balance verification
ATM transactions
Clearing and settlement
Interchange fees
Refunds and disputes
Common business scenarios
Banking interview questions

By the end of the next article, you'll understand how debit card payments differ from credit card transactions and why they are processed differently within the banking ecosystem.