21. Payment Domain Fundamentals

Learn Payment Domain Fundamentals as part of the Domain Knowledge learning path for software engineers and architects.

Introduction

Every day, billions of payment transactions occur across the globe. People purchase groceries, order food online, pay utility bills, transfer money to friends, subscribe to streaming services, and shop on e-commerce websites. Behind every successful payment lies a sophisticated ecosystem involving banks, merchants, payment processors, gateways, card networks, regulators, and technology providers.

Although customers experience a payment in just a few seconds, multiple organizations collaborate behind the scenes to authorize, process, clear, settle, and reconcile the transaction.

For software engineers working in Banking, FinTech, Retail, Healthcare, Telecommunications, Travel, or E-Commerce, understanding the payment domain is just as important as understanding system architecture.

This article introduces the business concepts of the payment industry. It explains how money moves, who participates in the payment process, common payment methods, and the terminology every software engineer should know.

Note: This article focuses on business domain knowledge rather than APIs, microservices, databases, or software architecture.

Learning Objectives

After reading this article, you will understand:

What is a payment
Importance of payment systems
Evolution of payments
Payment ecosystem
Key payment participants
Common payment methods
Online and offline payments
Payment business terminology
Business value of payment systems
Payment lifecycle overview

What is a Payment?

A payment is the transfer of monetary value from one party to another in exchange for goods, services, or financial obligations.

Simply put,

A payment is the movement of money from the payer to the payee.

Examples include:

Purchasing groceries
Paying rent
Shopping online
Buying airline tickets
Paying hospital bills
Utility bill payments
Subscription renewals
Salary payments
Sending money to family members
Loan repayments

Payments can occur between:

Individual → Business
Individual → Individual
Business → Business
Government → Citizen
Business → Government

Every modern economy depends on secure, reliable, and efficient payment systems.

Why are Payment Systems Important?

Imagine a world without digital payments.

Customers would have to carry cash everywhere.

Businesses would struggle to receive payments instantly.

International commerce would become significantly slower.

Online shopping would almost disappear.

Modern payment systems enable:

E-commerce
Mobile banking
Digital wallets
Contactless payments
International trade
Government benefits
Salary deposits
Tax collection
Utility bill payments
Subscription businesses

Without payment systems, today's digital economy could not function.

Evolution of Payments

Payments have evolved dramatically over the past several decades.

flowchart LR

Cash

Cash --> Checks

Checks --> DebitCards

DebitCards --> CreditCards

CreditCards --> InternetBanking

InternetBanking --> MobilePayments

MobilePayments --> DigitalWallets

DigitalWallets --> RealTimePayments

Cash Era

For thousands of years, physical cash was the primary method of payment.

Advantages

Simple
Immediate exchange
No technology required

Limitations

Theft risk
Difficult to transport
No transaction history
No remote payments

Check Payments

Banks introduced paper checks to simplify large-value transactions.

Benefits

Safer than carrying large amounts of cash
Bank verification

Challenges

Slow processing
Manual verification
Fraud
Lost checks

Card Payments

Debit and credit cards revolutionized consumer payments.

Benefits

Fast
Secure
Accepted worldwide
Easy online purchases

Today, card payments account for a significant percentage of global electronic payments.

Online Payments

The rise of the Internet introduced online payment platforms.

Examples include

Online shopping
Airline bookings
Hotel reservations
Utility payments
Insurance premiums

Mobile Payments

Smartphones transformed payment experiences.

Examples

Apple Pay
Google Pay
Samsung Wallet

Users can now pay using:

Mobile phones
Smart watches
Tablets

Real-Time Payments

Modern payment systems now process transactions within seconds.

Examples

UPI (India)
RTP (United States)
Faster Payments (United Kingdom)
PIX (Brazil)

These systems enable instant money transfers between bank accounts.

What is the Payment Industry?

The payment industry is a global network of organizations that facilitate the movement of money between individuals, businesses, financial institutions, and governments.

The industry includes:

Banks
Payment processors
Payment gateways
Card networks
Merchants
Digital wallet providers
Regulatory authorities
FinTech companies

Together, these organizations ensure that payments are:

Secure
Fast
Reliable
Accurate
Compliant with regulations

Payment Ecosystem

The payment ecosystem consists of all organizations involved in moving money from a customer to a merchant.

flowchart LR

Customer

Customer --> Merchant

Merchant --> PaymentGateway

PaymentGateway --> PaymentProcessor

PaymentProcessor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Approval

Approval --> Merchant

Every participant performs a unique business function.

Objectives of a Payment System

A payment system is designed to achieve several important business goals.

Secure Money Transfer

The system must ensure that only authorized users can initiate payments.

Accurate Processing

Every transaction should be processed correctly without duplication or loss.

Fast Processing

Customers expect payments to complete within seconds.

Fraud Prevention

Payment providers continuously monitor suspicious activities.

Regulatory Compliance

Payment providers must comply with financial regulations.

Customer Convenience

The payment experience should be simple and seamless.

Characteristics of a Good Payment System

A high-quality payment system should have the following characteristics.

Characteristic	Description
Secure	Protects customer information
Reliable	Available 24×7
Fast	Processes payments quickly
Accurate	Eliminates processing errors
Scalable	Handles millions of transactions
Compliant	Meets regulatory requirements
User Friendly	Easy for customers to use
Cost Effective	Minimizes processing costs

Types of Payment Transactions

Payments can be classified based on the parties involved.

Consumer to Business (C2B)

A customer purchases products from a merchant.

Examples

Amazon
Walmart
Netflix
Uber

Business to Consumer (B2C)

Businesses send money to customers.

Examples

Refunds
Insurance claim payments
Cashback rewards

Consumer to Consumer (C2C)

Money transfers between individuals.

Examples

Friends splitting dinner expenses
Family remittances
Peer-to-peer payments

Business to Business (B2B)

Payments between businesses.

Examples

Supplier payments
Vendor invoices
Manufacturing contracts

Government Payments

Government agencies send or receive funds.

Examples

Tax collection
Pension payments
Social security benefits
Business licenses

Common Payment Channels

Customers can initiate payments through multiple channels.

Channel	Example
Retail Store	POS Terminal
ATM	Cash Withdrawal
Mobile Banking	Bank App
Internet Banking	Web Portal
E-Commerce Website	Amazon
QR Code	Restaurant Payment
Digital Wallet	Apple Pay
Contactless Card	NFC Payment

Payment Business Models

Organizations participate in the payment industry through different business models.

Merchant Services

Enable businesses to accept payments.

Examples

Stripe
Square
Adyen

Consumer Banking

Provide payment services to retail customers.

Examples

Checking accounts
Debit cards
Credit cards

Payment Service Providers (PSPs)

Offer payment infrastructure to merchants.

Responsibilities include:

Payment routing
Fraud prevention
Currency conversion
Merchant onboarding

Digital Wallet Providers

Store customer payment credentials securely.

Examples

Apple Pay
Google Pay
PayPal

Buy Now Pay Later Providers

Allow customers to purchase products immediately and pay over time.

Examples

Affirm
Klarna
Afterpay

Business Benefits of Digital Payments

Digital payments provide significant advantages to customers, merchants, and financial institutions.

Benefits for Customers

Faster checkout
Secure transactions
Cashback and rewards
Digital transaction history
Contactless payments
Mobile convenience

Benefits for Merchants

Increased sales
Reduced cash handling
Faster settlements
Better customer experience
Lower operational costs
Global customer reach

Benefits for Banks

Increased transaction volume
Service fees
Customer retention
Cross-selling opportunities
Improved digital engagement

Benefits for Governments

Reduced cash economy
Improved tax compliance
Financial transparency
Financial inclusion
Efficient welfare distribution

Key Business Terminology

Understanding payment terminology is essential before learning transaction processing.

Term	Meaning
Payment	Transfer of money
Payer	Person sending money
Payee	Person receiving money
Merchant	Business accepting payments
Transaction	Individual payment event
Settlement	Transfer of funds
Authorization	Approval of payment
Refund	Returning money
Chargeback	Reversal initiated by issuing bank
Merchant Account	Account used to receive electronic payments

Payment Lifecycle

Every payment follows a well-defined business lifecycle before money reaches the merchant.

Although customers see only a "Payment Successful" message, multiple organizations work together behind the scenes to authorize, verify, process, settle, and reconcile the payment.

Understanding the payment lifecycle is one of the most important topics for software engineers working in:

Banking
FinTech
Payment Gateways
E-Commerce
Retail
Digital Wallets
Card Networks

Complete Payment Lifecycle

flowchart LR

Customer

Customer --> Checkout

Checkout --> Authorization

Authorization --> Authentication

Authentication --> Approval

Approval --> Capture

Capture --> Clearing

Clearing --> Settlement

Settlement --> Reconciliation

Reconciliation --> Merchant

Every stage has a specific business purpose.

Step 1 — Customer Checkout

The payment journey begins when a customer decides to purchase a product or service.

Examples

Buying a laptop online
Paying electricity bill
Booking a hotel
Purchasing movie tickets
Ordering food

The customer selects a payment method such as:

Credit Card
Debit Card
UPI
Digital Wallet
Bank Transfer
Buy Now Pay Later

Information Collected During Checkout

The merchant collects information required for processing.

Typical information includes

Information	Example
Customer Name	John Smith
Amount	$250
Currency	USD
Card Number	** ** 1234
Expiration Date	MM/YY
CVV	***
Billing Address	Customer Address
Merchant ID	Unique Merchant Identifier

For digital wallets, tokenized payment credentials are usually used instead of the actual card number.

Step 2 — Payment Authorization

Authorization determines whether the customer has sufficient funds or credit and whether the payment should be approved.

It is NOT the movement of money.

Instead, it is a permission granted by the issuing bank.

Authorization Flow

flowchart LR

Customer

Customer --> Merchant

Merchant --> Gateway

Gateway --> Processor

Processor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Decision

Decision --> Merchant

Authorization Checks

During authorization, the issuing bank performs several checks.

Examples include

Is the card valid?
Is the card expired?
Is the CVV correct?
Is sufficient balance available?
Is enough credit available?
Has the customer exceeded limits?
Is the transaction suspicious?
Is the merchant legitimate?

Only after these checks does the bank approve or decline the payment.

Possible Authorization Responses

Response	Meaning
Approved	Transaction can continue
Declined	Transaction rejected
Insufficient Funds	Balance unavailable
Card Expired	Card no longer valid
Incorrect CVV	Security verification failed
Suspected Fraud	Fraud rules triggered
Do Not Honor	Generic issuer decline

Real-World Example

Sarah purchases a laptop worth $1,200.

The issuing bank verifies:

Sarah's card is active.
Her credit limit is sufficient.
The CVV matches.
The transaction is not suspicious.

The bank approves the payment.

However,

No money has moved yet.

Only an authorization has been granted.

Authorization Hold

When authorization succeeds, the bank usually places an authorization hold on the customer's account.

Example

Available Credit:

Credit Limit

$5,000

Purchase

-$1,200

Available Credit

$3,800

The merchant still hasn't received any money.

The amount is only reserved.

Why Authorization Exists

Authorization protects:

Customers

Prevents unauthorized spending
Detects fraud
Verifies identity

Merchants

Ensures payment capability
Reduces failed orders

Banks

Prevents overdrafts
Detects suspicious activity

Authentication

Authentication verifies who is making the payment.

Authorization verifies whether payment is allowed.

These are different concepts.

Authentication Methods

Common authentication mechanisms include

PIN
Password
OTP
Fingerprint
Face Recognition
3-D Secure
Biometric Authentication

Example

Customer enters:

Card Number
Expiry
CVV

The issuing bank sends an OTP.

Customer enters OTP.

Identity is confirmed.

Only then is authorization performed.

Step 3 — Payment Approval

Once authentication and authorization succeed, the merchant receives an approval response.

The customer sees:

Payment Successful

The merchant now prepares the order.

Examples

Ship product
Confirm hotel reservation
Issue movie ticket
Activate subscription

Step 4 — Payment Capture

Authorization only reserves funds.

Capture instructs the bank to actually collect those funds.

Why Capture Exists

Sometimes merchants cannot immediately deliver products.

Examples

Airline Booking

Customer books ticket today.

Flight occurs two months later.

Merchant captures funds later.

Hotel Reservation

Hotel authorizes payment.

Actual capture happens after checkout.

Online Shopping

Merchant captures payment after shipment.

Authorization vs Capture

Authorization	Capture
Checks funds	Collects funds
Reserves amount	Transfers amount
Temporary hold	Permanent debit
Customer still owns money	Merchant begins receiving payment

Step 5 — Clearing

After capture, transaction information is exchanged among financial institutions.

This stage is called Clearing.

Clearing includes:

Transaction validation
Fee calculation
Network processing
Message exchange

Clearing Participants

flowchart LR

Merchant

Merchant --> Acquirer

Acquirer --> CardNetwork

CardNetwork --> Issuer

Issuer --> ClearingFiles

Information Shared During Clearing

Examples include

Merchant ID
Transaction Amount
Currency
Card Number Token
Timestamp
Authorization Code
Fees
Settlement Instructions

Why Clearing Matters

Clearing ensures

Every participant agrees on the transaction.
Processing fees are calculated.
Settlement instructions are created.
Disputes can be resolved later.

Step 6 — Settlement

Settlement is the actual movement of money between financial institutions.

This is where funds move.

Settlement Flow

flowchart LR

IssuingBank

IssuingBank --> CardNetwork

CardNetwork --> AcquiringBank

AcquiringBank --> Merchant

Settlement Activities

Settlement includes

Fund transfer
Fee deduction
Merchant payout
Network settlement
Bank accounting

Example

Laptop Price

$1,200

Processing Fee

$20

Merchant Receives

$1,180

The merchant receives funds after deducting agreed fees.

Settlement Frequency

Settlement schedules vary.

Examples

Immediate
Hourly
Daily
Weekly

Most merchants receive settlements daily.

Merchant Payout

After settlement,

Funds are deposited into the merchant account.

Merchant can now:

Pay suppliers
Purchase inventory
Pay employees
Withdraw funds

Step 7 — Reconciliation

Reconciliation verifies that all transaction records match.

This is an accounting activity.

Reconciliation Process

flowchart LR

MerchantRecords

MerchantRecords --> Compare

BankRecords --> Compare

Compare --> Differences

Differences --> Resolution

What is Compared?

Examples

Merchant Sales Report

↓

Gateway Transactions

↓

Processor Records

↓

Bank Statement

↓

Settlement Report

All records should match.

Why Reconciliation is Important

Without reconciliation,

Businesses may experience

Missing payments
Duplicate settlements
Incorrect fees
Accounting errors
Financial losses

Refunds

Sometimes payments must be returned.

Common reasons

Customer cancellation
Product return
Service unavailable
Duplicate payment
Pricing error

Refunds usually follow the reverse payment path.

Refund Flow

flowchart LR

Merchant

Merchant --> Acquirer

Acquirer --> CardNetwork

CardNetwork --> Issuer

Issuer --> Customer

Partial Refund

Merchant can refund only part of a payment.

Example

Purchase

$500

Returned Product

$150

Refund

$150

Remaining Purchase

$350

Full Refund

Entire payment is returned.

Example

Original Purchase

$900

Refund

$900

Final Cost

Chargebacks

A chargeback occurs when the customer disputes a transaction with the issuing bank.

Unlike refunds,

Chargebacks are initiated by the bank.

Common Reasons for Chargebacks

Fraud
Product not delivered
Duplicate charge
Incorrect amount
Unauthorized transaction
Merchant dispute

Chargeback Process

flowchart LR

Customer

Customer --> Issuer

Issuer --> CardNetwork

CardNetwork --> Acquirer

Acquirer --> Merchant

Merchant --> Evidence

Evidence --> Decision

Merchant Responsibilities During Chargebacks

Merchants may provide

Invoice
Shipping Proof
Delivery Confirmation
Customer Communication
Receipt
Refund History

The issuing bank decides the outcome.

Payment Failures

Not every payment succeeds.

Common reasons include

Insufficient funds
Card expired
Network timeout
Incorrect CVV
Fraud detection
Authentication failure
Merchant configuration issues

Handling failures gracefully improves the customer experience.

Payment Statuses

Status	Meaning
Initiated	Customer started payment
Pending	Awaiting processing
Authorized	Bank approved transaction
Captured	Merchant collected funds
Settled	Funds transferred
Refunded	Money returned
Chargeback	Customer dispute initiated
Failed	Transaction unsuccessful
Cancelled	Payment stopped before completion

End-to-End Example

Emma purchases a smartphone for $950.

Emma selects Credit Card.
Merchant sends authorization request.
Issuing bank authenticates Emma.
Authorization succeeds.
Merchant ships the phone.
Merchant captures payment.
Clearing messages are exchanged.
Settlement transfers funds.
Merchant receives payment.
Accounting team reconciles records.
Transaction is successfully completed.

Key Takeaways

Every payment follows a structured lifecycle.
Authorization reserves funds but does not move money.
Authentication verifies customer identity.
Capture requests the actual payment.
Clearing exchanges transaction information.
Settlement transfers funds.
Reconciliation matches accounting records.
Refunds and chargebacks are post-payment processes.
Understanding the payment lifecycle is essential for engineers building payment platforms.

Business Interview Questions

What are the stages of a payment lifecycle?
What is the difference between authentication and authorization?
What is an authorization hold?
Why is payment capture required?
What happens during clearing?
How is settlement different from clearing?
What is reconciliation?
What is the difference between a refund and a chargeback?
Why do payment failures occur?
Why is understanding the payment lifecycle important for software engineers?

Merchant Onboarding

Before a business can accept digital payments, it must establish a relationship with a payment service provider or acquiring bank. This process is known as Merchant Onboarding.

Merchant onboarding ensures that the business is legitimate, financially stable, and compliant with applicable financial regulations before it begins accepting customer payments.

Without proper onboarding, payment providers would expose themselves to fraud, money laundering, and financial risk.

Why Merchant Onboarding is Important

Merchant onboarding helps payment providers:

Verify business legitimacy
Prevent fraudulent merchants
Comply with financial regulations
Reduce financial risk
Protect customers
Ensure tax compliance
Enable secure payment processing

Merchant Onboarding Process

flowchart LR

Application

Application --> Verification

Verification --> RiskAssessment

RiskAssessment --> Compliance

Compliance --> Approval

Approval --> MerchantAccount

MerchantAccount --> LivePayments

Step 1 – Merchant Application

The business submits an application to a payment provider.

Typical information includes:

Business name
Business registration number
Tax identification number
Business address
Industry category
Website URL
Owner information
Expected transaction volume
Average transaction amount
Annual revenue
Bank account details

Step 2 – Business Verification

The payment provider verifies the submitted information.

Verification includes:

Business registration validation
Tax registration verification
Identity verification
Bank account verification
Address verification
Website review
Product review

Step 3 – Risk Assessment

Not every merchant has the same level of risk.

The payment provider evaluates:

Business type
Transaction volume
Chargeback history
Industry regulations
Fraud risk
Geographic risk
Creditworthiness

High-Risk Industries

Examples include:

Online gaming
Cryptocurrency
Gambling
Adult entertainment
Travel agencies
Digital subscriptions
Gift cards
Electronics resale

These businesses may require additional review or higher processing fees.

Step 4 – Compliance Review

Compliance teams verify that the merchant satisfies regulatory and legal requirements.

Checks include:

KYC (Know Your Customer)
AML (Anti-Money Laundering)
Sanctions screening
Beneficial ownership
Business licensing
Tax compliance

Step 5 – Merchant Account Creation

After approval, the merchant receives:

Merchant ID (MID)
Merchant account
Payment gateway access
API credentials
Settlement configuration
Reporting dashboard

The merchant is now ready to accept payments.

Merchant Categories (MCC)

Every merchant is assigned a Merchant Category Code (MCC).

The MCC identifies the type of business.

Examples:

MCC	Industry
5411	Grocery Stores
5812	Restaurants
5732	Electronics Stores
4111	Transportation
4814	Telecommunications
7011	Hotels

The MCC influences:

Processing fees
Fraud rules
Card rewards
Compliance requirements

Merchant Account

A Merchant Account is a special bank account that temporarily holds payment funds before settlement.

It differs from a standard business checking account.

Functions include:

Receiving card payments
Holding settlement funds
Managing refunds
Processing chargebacks
Reporting transactions

Merchant Dashboard

Most payment providers offer a merchant dashboard.

Common features:

Transaction history
Settlement reports
Refund management
Chargeback tracking
Customer reports
Payment analytics
Dispute management

Payment Fees

Processing electronic payments involves multiple organizations.

Each participant charges a fee for its services.

These fees together form the Merchant Discount Rate (MDR).

Common Payment Fees

Fee	Description
Interchange Fee	Paid to issuing bank
Assessment Fee	Paid to card network
Processing Fee	Paid to processor
Gateway Fee	Paid to gateway
Merchant Discount Rate	Total processing cost
Cross-Border Fee	International transaction fee
Currency Conversion Fee	Foreign exchange fee
Chargeback Fee	Dispute handling fee

Merchant Discount Rate (MDR)

The Merchant Discount Rate is the total fee deducted from each payment.

Example:

Customer Purchase

$500

Processing Fees

$12

Merchant Receives

$488

Interchange Fee

The interchange fee compensates the Issuing Bank.

It covers:

Credit risk
Fraud prevention
Customer services
Card issuance

Typically, it represents the largest component of payment processing costs.

Assessment Fee

Assessment fees are collected by the card network.

Examples:

Visa
Mastercard
Discover
American Express

These fees support:

Network infrastructure
Rule enforcement
Brand operations

Gateway Fee

Payment gateways charge merchants for:

Secure payment transmission
Tokenization
Payment APIs
Transaction routing
Fraud screening

Gateway pricing models vary depending on the provider.

Processor Fee

Payment processors charge for:

Transaction processing
Settlement
Reconciliation
Network connectivity
Reporting

Cross-Border Fees

International transactions usually incur additional fees.

Reasons include:

Currency conversion
Additional fraud monitoring
International settlement
Regulatory compliance

Currency Conversion Fees

When customer and merchant currencies differ:

Customer

USD

↓

Conversion

↓

Merchant

EUR

Foreign exchange rates determine the converted amount.

Payment Security

Payment security is one of the most critical aspects of the payment industry.

Millions of payment transactions occur daily.

Protecting customer financial information is essential.

Security Objectives

Payment security aims to:

Protect customer information
Prevent fraud
Prevent identity theft
Prevent unauthorized transactions
Ensure secure communication
Maintain customer trust

Sensitive Payment Information

Sensitive payment data includes:

Card Number (PAN)
CVV
PIN
Expiration Date
Authentication Tokens
Bank Account Numbers

This information must be protected throughout the payment lifecycle.

Common Security Technologies

Modern payment systems use multiple security mechanisms.

Examples:

Encryption
Tokenization
TLS
EMV Chips
Dynamic CVV
Multi-Factor Authentication
Biometric Authentication

Encryption

Encryption converts readable payment information into unreadable data.

Only authorized systems can decrypt the information.

Benefits:

Confidentiality
Data protection
Secure communication

Tokenization

Tokenization replaces sensitive card information with a randomly generated token.

Example:

Original Card

4111 1111 1111 1111

↓

Token

TK_8FD62X91A4

The merchant stores only the token, reducing the risk of data exposure.

EMV Chip Cards

EMV cards generate dynamic transaction information.

Benefits:

Difficult to clone
Strong fraud protection
Secure authentication

EMV significantly reduced counterfeit card fraud worldwide.

PCI DSS

Payment Card Industry Data Security Standard (PCI DSS)

PCI DSS is a global security standard established by major card networks.

Its purpose is to protect cardholder data.

PCI DSS Objectives

Organizations must:

Build secure networks
Protect stored card data
Encrypt transmission
Restrict data access
Monitor systems
Test security regularly
Maintain security policies

Failure to comply may result in:

Financial penalties
Increased processing costs
Loss of card acceptance privileges

KYC (Know Your Customer)

Financial institutions must verify customer identities.

KYC helps prevent:

Identity fraud
Financial crime
Terrorist financing
Account misuse

KYC Information

Typical information includes:

Government ID
Passport
Driver's License
Address Proof
Date of Birth
Tax Identification
Selfie Verification

AML (Anti-Money Laundering)

AML regulations prevent criminals from disguising illegally obtained funds.

Financial institutions monitor transactions for suspicious activity.

AML Activities

Examples include:

Transaction monitoring
Large cash reporting
Suspicious Activity Reports
Sanctions screening
Risk scoring

Sanctions Screening

Banks verify customers and merchants against international sanctions lists.

Common sources include:

OFAC
United Nations
European Union
Local financial regulators

Fraud Prevention

Fraud prevention combines technology, analytics, and operational processes.

Goals include:

Blocking fraudulent payments
Detecting stolen cards
Preventing account takeover
Reducing chargebacks

Common Fraud Types

Examples include:

Card Not Present (CNP) Fraud
Card Present Fraud
Identity Theft
Friendly Fraud
Account Takeover
Synthetic Identity Fraud
Phishing
Merchant Fraud

Fraud Detection Techniques

Payment providers use:

Velocity checks
Device fingerprinting
Geolocation analysis
Behavioral analytics
Machine learning
Risk scoring
Blacklists
Whitelists

Example Fraud Rule

If:

Five failed payments
Within ten minutes
From the same device

↓

Flag as suspicious

↓

Require additional authentication.

Payment Regulations

Payment providers operate in highly regulated environments.

Compliance helps:

Protect consumers
Prevent financial crime
Maintain market stability

Common Regulations

Examples include:

PCI DSS
KYC
AML
PSD2 (Europe)
GDPR
Consumer Protection Laws
Local Banking Regulations

Business Challenges

Payment providers face many operational challenges.

Examples:

Increasing fraud
Chargebacks
Cybersecurity threats
Regulatory changes
Cross-border compliance
High transaction volumes
Merchant risk
Customer expectations
Real-time payment demands

Real-World Example

A new online electronics retailer wants to accept credit card payments.

The company:

Applies for a merchant account.
Completes KYC verification.
Passes AML screening.
Receives a Merchant ID.
Integrates with a payment gateway.
Becomes PCI DSS compliant.
Begins accepting payments.
Transactions are monitored continuously for fraud.
Daily settlements are deposited into the merchant account.
Finance teams reconcile transactions and investigate any chargebacks.

Key Takeaways

Merchant onboarding ensures businesses can safely accept digital payments.
Payment providers evaluate business legitimacy, financial risk, and regulatory compliance.
Payment processing involves multiple fees shared among banks, card networks, gateways, and processors.
Security technologies such as encryption, tokenization, and EMV protect payment information.
PCI DSS, KYC, and AML are essential compliance frameworks.
Fraud prevention is a continuous process combining technology, analytics, and operational controls.

Business Interview Questions

What is merchant onboarding?
Why is risk assessment important during onboarding?
What is a Merchant Category Code (MCC)?
What is the purpose of a merchant account?
What is the Merchant Discount Rate (MDR)?
What is the difference between interchange and assessment fees?
How does tokenization improve payment security?
What is PCI DSS, and why is it important?
What are KYC and AML?
What techniques are commonly used for payment fraud detection?

Real-World Payment Scenarios

Understanding payment concepts becomes much easier when viewed through real-world business scenarios. Every payment follows the same fundamental lifecycle, but different industries introduce unique business rules and customer experiences.

This section explores how payments work across various industries and what happens behind the scenes.

Scenario 1 – Online Shopping

Sarah purchases a laptop worth $1,200 from an online electronics store.

Business Flow

flowchart LR

Customer

Customer --> EcommerceWebsite

EcommerceWebsite --> PaymentGateway

PaymentGateway --> Processor

Processor --> AcquiringBank

AcquiringBank --> CardNetwork

CardNetwork --> IssuingBank

IssuingBank --> Approval

Approval --> Merchant

Merchant --> Warehouse

Warehouse --> Customer

Step-by-Step Process

Sarah adds the laptop to her shopping cart.
She enters her credit card information.
The merchant sends the payment request.
The issuing bank authorizes the transaction.
The merchant receives approval.
The warehouse ships the laptop.
Payment is captured.
Funds are settled.
Merchant receives payment.

Scenario 2 – Restaurant Payment

John finishes dinner at a restaurant.

Total Bill

$80

Tip

$15

Final Payment

$95

Unlike e-commerce, restaurants often authorize the payment first and capture the final amount after the customer adds the tip.

Business Flow

Authorization

↓

Customer Adds Tip

↓

Capture

↓

Settlement

Scenario 3 – Hotel Reservation

Hotels commonly use authorization holds.

Example

Hotel Stay

4 Nights

Estimated Cost

$900

Security Deposit

$200

Authorization Hold

$1,100

Only after checkout is the final payment captured.

Unused authorization is released.

Scenario 4 – Fuel Station

Gas stations usually authorize a higher amount before fueling begins.

Example

Authorization Hold

$150

Actual Fuel Purchase

$48

Settlement

$48

Remaining authorization is removed after settlement.

Scenario 5 – Subscription Payment

Netflix, Spotify, and similar services use recurring payments.

Example

Monthly Subscription

$19.99

Business Flow

Customer

↓

Stored Payment Method

↓

Automatic Authorization

↓

Capture

↓

Subscription Renewal

Recurring payments continue until cancellation.

Scenario 6 – Airline Booking

Customer books a flight six months before travel.

Business Process

Booking

↓

Authorization

↓

Ticket Confirmation

↓

Flight Date

↓

Settlement

Airlines may have different capture strategies depending on their business policies.

Scenario 7 – Digital Wallet Payment

Customer pays using Apple Pay.

Instead of transmitting the real card number:

Customer

↓

Wallet Token

↓

Payment Gateway

↓

Bank

↓

Approval

This significantly reduces card exposure.

Scenario 8 – Peer-to-Peer Transfer

Example

Alice sends $200 to Bob.

Business Flow

Alice

↓

Payment App

↓

Bank

↓

Bob's Bank

↓

Bob

Money is transferred directly between customer accounts.

Examples include:

Zelle
Venmo
Cash App
UPI

Scenario 9 – International Payment

Customer in USA purchases products from a merchant in Germany.

Additional processing includes:

Currency conversion
Foreign exchange rates
Cross-border settlement
International compliance
Fraud screening

International payments generally involve higher processing costs.

Scenario 10 – Refund

Customer returns shoes purchased online.

Business Flow

Merchant

↓

Gateway

↓

Processor

↓

Bank

↓

Customer

The original transaction is reversed and funds are returned.

Scenario 11 – Chargeback

Customer claims:

"I never purchased this product."

Business Process

Customer

↓

Issuing Bank

↓

Card Network

↓

Acquiring Bank

↓

Merchant

↓

Evidence Review

↓

Decision

Chargebacks protect customers but also introduce operational costs for merchants.

Common Payment KPIs

Payment organizations continuously monitor business performance using Key Performance Indicators (KPIs).

Authorization Rate

Measures the percentage of payment requests successfully approved.

Formula

Approved Transactions
------------------------
Total Authorization Requests

Higher authorization rates generally improve customer experience and merchant revenue.

Payment Success Rate

Measures successfully completed payments.

Example

Total Payments

10,000

Successful

9,850

Success Rate

98.5%

Settlement Time

Measures the time required for merchants to receive funds.

Examples

Same Day
Next Day
Two Business Days

Faster settlement improves merchant cash flow.

Refund Rate

Percentage of transactions refunded.

High refund rates may indicate:

Product quality issues
Customer dissatisfaction
Incorrect pricing
Operational problems

Chargeback Rate

Measures customer disputes.

Formula

Chargebacks

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

Completed Transactions

Card networks typically expect merchants to maintain low chargeback ratios.

Fraud Rate

Measures fraudulent transactions.

Organizations continuously monitor fraud rates to improve fraud prevention strategies.

Average Transaction Value (ATV)

Average amount spent per payment.

Formula

Total Sales

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

Number of Transactions

Used to evaluate customer purchasing behavior.

Payment Conversion Rate

Percentage of customers who complete payment after initiating checkout.

Low conversion may indicate:

Poor checkout experience
Technical issues
Limited payment methods
Customer trust issues

Customer Payment Failure Rate

Tracks failed payment attempts.

Common reasons:

Insufficient funds
Network errors
Fraud rules
Authentication failures

Business Reports

Payment providers generate many operational reports.

Examples include:

Daily Settlement Report
Merchant Sales Report
Chargeback Report
Refund Report
Fraud Report
Gateway Performance Report
Authorization Report
Currency Conversion Report
Reconciliation Report

These reports help finance, operations, compliance, and customer support teams.

Business Best Practices

Successful payment organizations follow industry best practices.

Offer Multiple Payment Methods

Customers prefer flexibility.

Examples

Credit Cards
Debit Cards
Digital Wallets
Bank Transfers
Buy Now Pay Later

Minimize Checkout Steps

Shorter checkout processes improve conversion rates.

Monitor Fraud Continuously

Fraud detection should operate in real time.

Use:

Velocity checks
Device analysis
Risk scoring
Machine learning

Protect Customer Data

Never expose sensitive payment information.

Use:

Encryption
Tokenization
Secure authentication

Improve Authorization Rates

Reduce unnecessary declines through:

Better fraud models
Updated card information
Intelligent routing

Perform Daily Reconciliation

Verify that:

Sales
Settlements
Refunds
Chargebacks

all match accounting records.

Ensure Regulatory Compliance

Regularly review compliance with:

PCI DSS
AML
KYC
Consumer protection regulations

Provide Excellent Customer Support

Customers expect quick assistance with:

Failed payments
Refunds
Chargebacks
Billing questions

Excellent service improves customer loyalty.

Payment Industry Trends

The payment industry continues to evolve rapidly.

Current trends include:

Contactless payments
Real-Time Payments (RTP)
Digital wallets
Embedded finance
Open Banking
Buy Now Pay Later
Artificial Intelligence
Machine Learning Fraud Detection
Biometric Authentication
Tokenization Everywhere

Skills Software Engineers Should Learn

Developers working in payment systems should understand:

Business Knowledge

Payment lifecycle
Merchant onboarding
Card processing
Settlement
Chargebacks
Fraud

Technical Knowledge

REST APIs
Event-driven architecture
Distributed systems
High availability
Idempotency
Messaging
Security
Observability

Compliance

PCI DSS
KYC
AML
Data privacy

Career Opportunities

Payment domain knowledge is valuable in companies such as:

Banking

JPMorgan Chase
Bank of America
Wells Fargo
Capital One

Card Networks

Visa
Mastercard
American Express
Discover

FinTech

Stripe
PayPal
Adyen
Block (Square)

Technology

Oracle
Amazon
Microsoft
Google

Retail

Walmart
Costco
Target

Key Takeaways

Every payment follows a structured business lifecycle.
Different industries implement payment flows based on their operational needs.
Payment KPIs help organizations measure performance and customer experience.
Security, compliance, and fraud prevention are fundamental to payment processing.
Payment engineers require both business knowledge and technical expertise.
Modern payment systems continue to evolve with real-time processing, digital wallets, and AI-driven fraud detection.

Business Interview Questions

Payment Fundamentals

What are the stages of a payment lifecycle?
What is the difference between authorization and settlement?
Why do merchants need acquiring banks?
What is a payment gateway?
What is a payment processor?

Merchant Operations

What is merchant onboarding?
Why is Merchant Category Code (MCC) important?
What is the Merchant Discount Rate (MDR)?

Security

What is PCI DSS?
What is tokenization?
Why is encryption important?
What is the difference between KYC and AML?

Fraud

What are common payment fraud types?
What is a chargeback?
How do payment providers detect fraud?

Business

What KPIs are important in payment processing?
Why is reconciliation important?
What causes payment failures?
What are the biggest challenges facing the payment industry today?
Why is payment domain knowledge valuable for software engineers?

Summary

The payment industry powers the global economy by enabling secure and efficient movement of money between customers, merchants, financial institutions, and governments. Although a payment appears simple to the customer, it involves a complex ecosystem of authorization, authentication, processing, settlement, reconciliation, security, compliance, and fraud prevention.

By understanding payment fundamentals, merchant onboarding, payment fees, security standards, regulatory requirements, and real-world payment scenarios, software engineers gain the business knowledge required to build reliable payment platforms, troubleshoot production issues, communicate effectively with business stakeholders, and design scalable financial systems.

This foundational knowledge prepares you for advanced topics such as payment gateways, card networks, settlement systems, digital wallets, fraud engines, and enterprise payment architecture.

Payment Glossary

The payment industry uses many specialized terms. Understanding these terms helps software engineers communicate effectively with business analysts, payment operations teams, merchants, and financial institutions.

A

Acquirer (Acquiring Bank)

A financial institution that provides merchant accounts and receives payments on behalf of merchants.

Example:

A restaurant accepts Visa cards through an acquiring bank.

Acquirer BIN

The Bank Identification Number assigned to an acquiring bank.

Used to identify the acquiring institution during payment processing.

ACH (Automated Clearing House)

An electronic network used primarily in the United States for bank-to-bank transfers.

Common Uses

Salary deposits
Utility payments
Mortgage payments
Vendor payments

Authorization

The process of determining whether a payment should be approved.

Authorization verifies:

Card validity
Available funds
Available credit
Fraud rules

Authorization does not transfer money.

Authorization Hold

A temporary reservation placed on customer funds until the merchant captures the payment.

Common Examples

Hotels
Car Rentals
Fuel Stations

B

BIN (Bank Identification Number)

The first six to eight digits of a payment card identifying the issuing bank.

Example

411111XXXXXX1234

^^^^^^

BIN

Billing Address

The address associated with the customer's payment card.

Used during fraud verification.

Business Day

A working day during which banks process financial transactions.

Settlement often occurs on business days only.

C

Capture

The process of collecting funds after authorization.

Unlike authorization, capture begins the movement of money.

Card Network

Organizations that connect issuing banks and acquiring banks.

Examples

Visa
Mastercard
American Express
Discover

Cardholder

The individual who owns and uses a payment card.

Card Present (CP)

A payment where the physical card is available.

Examples

Grocery store
Restaurant
Retail POS

Card Not Present (CNP)

A payment where the physical card is not available.

Examples

Amazon
Netflix
Airline Booking

CNP transactions generally carry higher fraud risk.

Chargeback

A payment reversal initiated by the issuing bank after a customer dispute.

Clearing

Exchange of payment information between financial institutions before settlement.

CVV

Card Verification Value.

Usually printed on the back of payment cards.

Provides additional security.

D

Debit Card

A payment card linked directly to a customer's bank account.

Funds are deducted immediately after settlement.

Digital Wallet

An application that securely stores payment credentials.

Examples

Apple Pay
Google Pay
Samsung Wallet

Dispute

A customer complaint regarding a transaction.

Disputes may result in chargebacks.

E

EMV

Global standard for chip-enabled payment cards.

Provides stronger protection than magnetic stripe cards.

Encryption

Converts readable payment information into unreadable encrypted data.

F

Fraud Detection

Processes used to identify suspicious payment activities.

Techniques include:

Velocity Checks
Device Fingerprinting
AI Models
Behavioral Analysis

Friendly Fraud

Occurs when customers dispute legitimate purchases.

G

Gateway

A payment gateway securely transmits payment information between merchants and payment processors.

I

Interchange Fee

Fee paid by the acquiring bank to the issuing bank.

Usually the largest component of payment processing costs.

Issuer (Issuing Bank)

The bank that provides payment cards to customers.

Responsibilities include:

Authentication
Authorization
Fraud Detection
Credit Management

K

KYC

Know Your Customer.

Verification process confirming customer identity.

M

Merchant

A business accepting customer payments.

Examples

Amazon
Walmart
Starbucks
Netflix

Merchant Account

A special account used to receive electronic payments before settlement.

Merchant Discount Rate (MDR)

Total processing fee deducted from merchant payments.

Merchant ID (MID)

Unique identifier assigned to every merchant.

Merchant Category Code (MCC)

Four-digit code identifying merchant business type.

Example

5411

Grocery Stores

O

OTP

One-Time Password.

Used for customer authentication.

P

PAN

Primary Account Number.

The complete payment card number.

Sensitive information.

Payment Gateway

Secure communication layer between merchant and payment processor.

Payment Processor

Organization responsible for routing payment transactions.

PCI DSS

Payment Card Industry Data Security Standard.

Global security standard protecting payment card data.

POS

Point of Sale.

Location where customers make payments.

Examples

Grocery checkout
Restaurant terminal
Retail counter

R

Reconciliation

Matching payment records among:

Merchant
Gateway
Processor
Bank

Refund

Returning money to the customer.

S

Settlement

Actual movement of funds between financial institutions.

Settlement Report

Report listing completed merchant settlements.

Stored Credential

Customer payment information securely stored for future transactions.

Used in subscriptions.

T

Tokenization

Replacing sensitive payment data with randomly generated tokens.

Example

Card Number

4111111111111111

↓

Token

TK_9AFD61H73

Transaction

A payment event initiated by a customer.

U

UPI

Unified Payments Interface.

Real-time payment system developed in India.

V

Velocity Check

Fraud detection rule monitoring rapid transaction activity.

Example

5 Payments

Within

2 Minutes

↓

Review Transaction

W

Wallet Token

Secure identifier replacing the original card number in digital wallet transactions.

End-to-End Payment Flow

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 --> MerchantBank

Payment Ecosystem Overview

flowchart TD

Customer

Merchant

Gateway

Processor

Acquirer

Network

Issuer

Customer --> Merchant

Merchant --> Gateway

Gateway --> Processor

Processor --> Acquirer

Acquirer --> Network

Network --> Issuer

Issuer --> Network

Network --> Acquirer

Acquirer --> Merchant

Payment Lifecycle Summary

Stage	Purpose	Money Moves?
Checkout	Customer initiates payment	❌
Authentication	Verify identity	❌
Authorization	Verify funds or credit	❌
Capture	Merchant requests funds	✅ Begins
Clearing	Exchange transaction information	❌
Settlement	Transfer funds	✅
Reconciliation	Match accounting records	❌
Refund	Return payment	✅
Chargeback	Reverse disputed payment	✅

Payment Participants Summary

Participant	Responsibility
Customer	Makes payment
Merchant	Sells products
Payment Gateway	Secure communication
Payment Processor	Routes transactions
Acquiring Bank	Merchant banking
Card Network	Routes payment messages
Issuing Bank	Approves or declines payments
Regulator	Ensures compliance

Common Payment Methods

Method	Example
Cash	Physical Currency
Debit Card	Bank Account
Credit Card	Visa, Mastercard
ACH	Bank Transfer
Wire Transfer	SWIFT
Digital Wallet	Apple Pay
Contactless	NFC Card
QR Payment	Merchant QR
UPI	Instant Bank Transfer
BNPL	Affirm, Klarna

Practice Exercises

Exercise 1

Trace an online purchase from checkout through:

Authorization
Capture
Clearing
Settlement
Reconciliation

Identify every participant involved.

Exercise 2

Compare the payment lifecycle for:

Credit Card
Debit Card
UPI
Digital Wallet

Highlight similarities and differences.

Exercise 3

List all fees involved in a $500 card payment.

Identify which organization receives each fee.

Exercise 4

Investigate a failed payment and determine whether it failed during:

Authentication
Authorization
Capture
Settlement

Explain the likely business reason.

Exercise 5

Design a fraud prevention checklist for an online merchant.

Include:

Velocity checks
Device fingerprinting
Geolocation analysis
Transaction limits
Risk scoring

Learning Checklist

After completing this article, you should be able to answer:

✅ What is a payment ecosystem?
✅ Who participates in payment processing?
✅ What is the difference between authorization and capture?
✅ What happens during clearing and settlement?
✅ What is merchant onboarding?
✅ How are merchants charged processing fees?
✅ Why are PCI DSS, KYC, and AML important?
✅ How do payment providers detect fraud?
✅ What is the difference between a refund and a chargeback?
✅ How does money move from a customer to a merchant?

Series Summary

Congratulations!

You have completed Payment Domain Fundamentals, the foundation of the Payment Domain Knowledge series.

In this article, you learned:

Payment industry overview
Payment ecosystem
Key participants
Payment methods
Payment lifecycle
Merchant onboarding
Payment fees
Security and compliance
Fraud prevention
Real-world payment scenarios
Business KPIs
Industry glossary

These concepts provide the business foundation required before diving into payment gateways, card networks, settlement systems, fraud engines, and enterprise payment architectures.