A payment processor is the company or technical system that carries transaction messages between a merchant, the card networks and the banks, obtains authorizations, submits completed transactions for clearing and arranges the movement of funds into the merchant account. In checkout and payments within e-commerce, the processor is the part of the chain that turns an approved checkout into money actually received.
The term is used at two levels. In the strict industry sense it means the transaction-processing infrastructure behind an acquiring bank. In everyday merchant language it often means the whole payment provider that a store contracts with, which may bundle the processor, the acquirer relationship and the payment gateway into one service.
How a payment processor handles a card transaction
Card payments follow the four-party model: the cardholder, the issuer that gave the card, the merchant, and the acquirer that holds the merchant relationship, connected by a card network such as Visa or Mastercard. The processor works on the acquiring side and translates each payment into network messages, traditionally based on the ISO 8583 message standard.
A transaction passes through several distinct stages, and each one has its own timing and failure modes. The table below shows the life cycle from the moment a customer confirms an order.
| Stage | What happens | Typical timing |
|---|---|---|
| Authorization | Issuer approves or declines and reserves the amount | One to three seconds |
| Capture | Merchant confirms the final amount to be charged | At shipment or immediately |
| Clearing | Captured transactions are submitted in batches to networks | Usually the same or next day |
| Settlement | Funds move from issuer to acquirer to merchant | Commonly one to three business days |
| Reconciliation | Merchant matches payouts with orders and fees | After each payout |
The gap between authorization and capture matters in e-commerce. Many stores authorize at checkout and capture only when the goods ship. An authorization hold does not last forever: depending on the network, card type and merchant category, it typically expires after roughly seven days, and capturing after expiry can fail or trigger a chargeback.
Payment processor compared with related roles
Several roles in the payment chain are often merged under one brand, which makes the vocabulary confusing. The essential distinction is that the gateway collects and transmits, the processor routes and settles, and the acquirer carries the financial risk.
| Role | Main responsibility | Faces the customer |
|---|---|---|
| Payment gateway | Securely captures payment data and passes it on | Yes, through checkout forms or APIs |
| Payment processor | Routes authorizations, clearing and settlement messages | Rarely, it works in the background |
| Acquiring bank | Holds the merchant account and underwrites risk | No |
| Card network | Sets rules and connects acquirers with issuers | No, except through card branding |
| Payment facilitator | Onboards many small merchants under one master account | Yes, as the merchant’s provider |
Modern full-stack providers combine all acquiring-side roles. This simplifies onboarding, because a merchant can accept payments within days, but it also means one provider controls availability, pricing and payout timing. Neighboring security steps such as 3D Secure authentication and tokenization of card numbers sit around the processor rather than replacing it.
Fees and pricing models
The total cost of a card payment, called the merchant service charge, has three components. Interchange goes to the issuer, scheme fees go to the card network, and the processor or acquirer markup pays for the service itself. In the European Economic Area, interchange for consumer cards is capped at 0.2% for debit and 0.3% for credit, while other regions have different or no caps.
| Pricing model | How it works | Main advantage | Main drawback |
|---|---|---|---|
| Blended or flat rate | One percentage plus a fixed fee per transaction | Simple and predictable | Often expensive for low-cost debit cards |
| Interchange plus | Actual interchange passed through plus a fixed markup | Transparent cost structure | Monthly statements are harder to read |
| Interchange plus plus | Interchange and scheme fees passed through separately | Most transparent model | Requires volume and analysis to benefit |
| Tiered pricing | Transactions grouped into qualified and other rates | Looks simple at first | Opaque reclassification raises costs |
Beyond per-transaction fees, contracts often include chargeback fees, currency conversion margins, payout fees and rolling reserves, where a share of revenue is held back for a period to cover future refunds and disputes. These terms frequently matter more than the headline rate.
Choosing a payment processor for an online store
The right processor depends on sales volume, geography, payment methods and risk profile. A small domestic shop and a cross-border subscription business have very different needs, as the following decision table shows.
| Merchant situation | Suitable setup | Reason |
|---|---|---|
| New store with low volume | All-in-one provider with flat pricing | Fast onboarding and minimal integration |
| Growing store with high card volume | Interchange plus plus contract | Lower and more transparent costs |
| Sales in many countries | Processor with local acquiring | Higher approval rates and fewer cross-border fees |
| Subscriptions and recurring billing | Processor with network tokens and account updater | Fewer failed renewals from expired cards |
| Very high volume or critical uptime | Two processors with payment orchestration | Failover and routing to the cheapest route |
Risks and common mistakes
The most expensive mistakes concern approval rates and account stability, not the visible fee. A difference of a few percentage points in authorization success can outweigh any price negotiation.
- Ignoring decline codes: soft declines can often be retried, while hard declines should not be retried repeatedly.
- Capturing after the authorization expires, which increases failures and disputes.
- Exceeding chargeback thresholds set by card networks, which can lead to monitoring programs and account termination.
- Relying on a single provider without a fallback plan for outages or sudden account reviews.
- Comparing only headline rates while overlooking currency conversion margins and reserves.
In simple terms
When someone pays by card in an online shop, the money does not jump straight from their bank to the shop. A payment processor acts like a courier and an accountant at once. It asks the customer’s bank whether the payment is allowed. It records the answer. Later, it makes sure the money actually arrives in the shop’s account.
The customer rarely sees the processor. Yet without it, a card payment would stop at the checkout page.
A practical example
An online furniture store sells items worth between 300 and 3,000 euros and ships made-to-order sofas about three weeks after purchase. At first it captured payments only at shipment, but many authorizations had expired by then, and captures began failing.
Working with its processor, the store changed its flow. It now captures the payment immediately at checkout for made-to-order items and refunds if the order is canceled, while stock items are still captured at shipment within a few days.
The store also moved from a flat rate to an interchange plus plus contract, because most customers pay with domestic debit cards. Failed captures dropped to almost zero, and the monthly processing cost fell noticeably once low-cost debit transactions were no longer charged at the blended rate.