Align Ecommerce Learning Center
Payment Technology & Operations
Understand the systems that move payments through your business—from checkout and authorization to settlement, reconciliation, and merchant funding.
Explore practical guides, visual explanations, comparisons, and tools covering payment gateways, processors, merchant accounts, APIs, recurring billing, POS systems, digital wallets, payment routing, and emerging technology.
Built for business owners Practical explanations Reviewed by payment professionals
Already evaluating your payment infrastructure? Get a free payment review →Important: A payment being approved is not the same as the merchant receiving the money.
The Payment Ecosystem
See How a Payment Moves Through Your Business
A card payment may appear to happen instantly, but several systems must exchange information before the transaction is approved, captured, settled, and deposited. Select any part of the payment stack to learn what it does, why it matters, and how it can affect your business.
Payment approval confirms that the transaction can proceed. It does not mean the merchant has received the funds.
2. Settlement and funding: Funds move after the transaction is captured
Timing varies by batch schedule, processor, bank, weekends, holidays, risk controls, and payment method.
Customer & Payment Method
The transaction begins when a customer selects a card, bank account, digital wallet, or another payment method.
What it is
The customer initiates the purchase using a credit card, debit card, digital wallet, bank account, or another payment method accepted by the merchant.
What it does
The payment method provides the account credentials or token needed to request authorization for the transaction.
Why it matters
The methods a business accepts can influence checkout completion, customer convenience, transaction expense, fraud exposure, and operational complexity.
Merchant example
A mobile shopper chooses Apple Pay instead of manually entering a card number into an ecommerce checkout.
Merchant impact
Offering the right payment methods can reduce friction and improve conversion, but every method can carry different integration, pricing, settlement, return, and risk requirements.
Checkout, App or POS System
This is the customer-facing environment where payment information and purchase details enter the merchant’s payment stack.
What it is
The interface through which a customer submits payment, including a website checkout, mobile app, payment link, virtual terminal, or point-of-sale system.
What it does
It collects the order and payment information and sends the transaction into the merchant’s payment infrastructure.
Why it matters
Checkout architecture affects conversion, customer confidence, data collection, integrations, reporting, security, and PCI responsibilities.
Merchant example
An ecommerce brand uses an embedded checkout, while its retail location accepts the same customer through an integrated countertop POS system.
Merchant impact
A poorly designed or incompatible checkout can create abandoned purchases, duplicate data entry, incomplete reporting, failed transactions, and unnecessary compliance exposure.
Payment Gateway
The gateway is the technology layer that securely connects the merchant’s checkout environment to the transaction-processing infrastructure.
What it is
A payment gateway securely transmits transaction information from a website, app, payment page, or POS environment into the processing network.
What it does
It can provide transaction messaging, tokenization, hosted fields, recurring billing, fraud controls, reporting, APIs, webhooks, and integration tools.
Why it matters
Gateway capabilities influence checkout flexibility, subscription support, data portability, reporting, security, integrations, and the ability to change processing relationships.
Merchant example
An online merchant uses a gateway API to send tokenized payment information from its website to its processor without storing raw card data in its own systems.
Merchant impact
The wrong gateway can restrict integrations, complicate migrations, weaken reporting, limit recurring billing functionality, or make the merchant overly dependent on one provider.
Payment Processor & Acquiring Connection
The processor and acquiring side move transaction messages between the merchant’s payment environment and the financial institutions involved.
What it is
The processor manages transaction communication and connects the merchant’s gateway or POS environment to acquiring and card-network infrastructure.
What it does
It routes authorization messages, receives responses, supports transaction capture, and participates in clearing, settlement, reporting, and merchant funding.
Why it matters
Processor capabilities can affect reliability, transaction routing, supported payment methods, integration compatibility, reporting, risk controls, and support quality.
Merchant example
The processor receives a transaction from the merchant’s gateway and routes the authorization request toward the appropriate card network and issuing bank.
Merchant impact
Processor limitations can produce integration restrictions, outages, poor support, weak reporting, or instability for complex business models. Multi-processor routing can improve redundancy when implemented correctly.
Card Network
The card network provides the rules and communication rails that connect acquiring institutions with card-issuing banks.
What it is
A card network—such as Visa, Mastercard, American Express, or Discover—operates transaction-routing systems and establishes network rules.
What it does
It routes transaction messages between the acquiring and issuing sides and supports network authorization, clearing, settlement, disputes, and compliance programs.
Why it matters
Network rules influence interchange qualification, stored credentials, recurring billing, fraud monitoring, disputes, data requirements, and merchant acceptance practices.
Merchant example
A Visa transaction travels through Visa’s network from the merchant’s acquiring connection to the institution that issued the customer’s card.
Merchant impact
How transactions are submitted can influence approval outcomes, costs, compliance treatment, fraud signals, and the evidence available if a customer later disputes the charge.
Issuing Bank
The issuing bank evaluates the transaction request on the customer’s side and normally makes the final authorization decision.
What it is
The financial institution that issued the customer’s card or payment account and maintains the customer-side account relationship.
What it does
It evaluates available funds or credit, account status, authentication data, fraud signals, transaction context, and internal risk rules before responding.
Why it matters
The issuer typically determines whether a card transaction is approved or declined, even when the merchant’s gateway and processor are functioning correctly.
Merchant example
A customer’s bank declines an unusually large online purchase because the transaction conflicts with the bank’s fraud-detection model.
Merchant impact
A merchant cannot directly control an issuer’s decision, but complete transaction data, authentication, routing, retry logic, billing descriptors, and checkout practices can influence authorization performance.
Authorization Response
The response tells the checkout whether the issuing bank approved or declined the request—but approval is not the end of the payment lifecycle.
What it is
A message returned through the payment network indicating whether the authorization request was approved or declined.
What it does
It gives the merchant an approval code or a decline response and determines whether the checkout can proceed with the transaction.
Why it matters
An approval confirms that the transaction may proceed, but the merchant still needs to capture the transaction and complete settlement before receiving funds.
Merchant example
A purchase is approved at checkout, but the merchant’s system fails to capture it before the authorization expires.
Merchant impact
Confusing authorization with funding can create incomplete transactions, fulfillment errors, expired authorizations, or false assumptions about cash already available to the business.
Capture & Merchant Batch
Capture confirms the amount the merchant intends to collect and moves an authorized transaction toward clearing and settlement.
What it is
Capture converts an approved authorization into a transaction the merchant intends to complete. Captured transactions are often grouped into a merchant batch.
What it does
It finalizes the transaction amount and submits the completed transaction record into the clearing and settlement process.
Why it matters
Uncaptured transactions can expire, and late or incorrectly configured batches can delay deposits and complicate reporting.
Merchant example
A restaurant authorizes a card before the tip is known, then captures the completed total after the customer signs the receipt.
Merchant impact
Capture settings and batch timing can affect cash flow, fulfillment, recurring billing, tips, partial shipments, delayed delivery, accounting, and customer experience.
Clearing & Settlement
Clearing calculates financial obligations, while settlement completes the movement of funds between participating institutions.
What it is
Clearing is the exchange and reconciliation of transaction records. Settlement is the resulting movement of money between the issuing and acquiring sides.
What it does
It determines what each participant owes and resolves the financial obligations created by the merchant’s captured transactions.
Why it matters
This stage turns completed transaction data into actual financial movement, subject to network schedules, processor policies, adjustments, and risk controls.
Merchant example
At the end of the processing cycle, captured transactions are cleared and the corresponding funds move through the card and banking system.
Merchant impact
Settlement timing, reversals, refunds, fees, reserves, bank holidays, processor cutoffs, and funding policies can change both when the merchant receives money and how much is deposited.
Merchant Funding & Reconciliation
The payment cycle becomes operationally useful only when deposits can be matched to sales, refunds, fees, reserves, and adjustments.
What it is
Merchant funding is the deposit of transaction proceeds into the business bank account. Reconciliation matches that deposit to the underlying activity.
What it does
It completes the operational payment cycle and gives the business the records needed to verify deposits and maintain accurate accounting.
Why it matters
Deposits may not equal gross sales because of fees, refunds, chargebacks, reserves, adjustments, different batch dates, or multiple sales channels.
Merchant example
A merchant compares gateway transactions, processor batch reports, fee records, and the bank deposit to explain why net funding differs from daily gross sales.
Merchant impact
Weak reconciliation can conceal missing funds, duplicate refunds, unexpected fees, chargebacks, reserve deductions, incorrect batches, or reporting failures across systems.
Authorization is not funding
An approved transaction still needs to be captured, cleared, settled, and deposited.
Gateway and processor are different
The gateway connects the checkout to payment infrastructure; the processor manages transaction communication and processing.
Deposits may not equal gross sales
Fees, refunds, disputes, reserves, adjustments, and batch timing can change the final deposit.