Payment processing software is the transaction engine that takes an online card payment from checkout through authorization, capture, clearing, settlement and disputes, and keeps the records that reconcile each step. This guide is for PSPs, acquiring banks and electronic money institutions (EMIs) that run this engine for their merchants.
What Is Payment Processing Software?
Payment processing software is the engine behind your payment service. It accepts the payment request from the merchant, applies your fraud and authentication rules, sends the authorization to an acquirer and tracks every later operation on the same payment. It then records the result for settlement, reconciliation and reporting.
The engine is several components that hand a payment from one to the next. Each has a different owner. The split below is for a licensed or rented platform; on your own servers you also run the hosting and its PCI DSS scope, and in an own build you own every vendor row.
Components of payment processing software and who owns them
Component
What it does
Who owns it
Acceptance
Hosted payment page, widget, application programming interface (API) and software development kits (SDKs) that receive the payment from the merchant
Software vendor builds it; you decide which methods each merchant may use
Card vault
Stores card numbers and replaces them with tokens
Vendor runs it inside its PCI DSS scope
Risk and authentication
Fraud rules, limits and the 3-D Secure (3DS) decision
You set the rules; the issuer authenticates the cardholder
Routing
Chooses the acquirer connection for each payment
You set the rules
Connectors
Translate each request into the format of one acquirer or payment method
Vendor builds and maintains them; the acquirer certifies them
Transaction ledger
Holds the state of each payment and links captures, refunds and chargebacks to it
Vendor builds it; your team reads it
Settlement and reporting
Matches acquirer reports to transactions and calculates what each merchant is owed
Processing software is not the full business system you run as a PSP. Merchant contracts, onboarding, fee plans and invoicing sit in a separate layer that uses the engine’s records.
How Does Payment Processing Software Handle a Transaction?
The software takes each payment through eight stages, from the merchant’s request to the last refund or dispute. Your engine acts at every stage, but it decides at only a few of them. The issuer, the card scheme and the acquirer own the rest, and the engine records what they return.
Request: the merchant sends, your software receives
The checkout passes the card data or a token, the amount, the currency and the shop identifier. The request names one of the card transaction types: a one-step payment or an authorization.
Screening: your software runs your rules
The engine checks the shop’s limits and runs your anti-fraud tools. Card numbers are replaced by payment tokenization before anything is stored.
Authentication: the issuer authenticates through your 3DS Server
Where your rules or the law call for it, the cardholder completes 3DS with the issuer before the authorization is sent.
Authorization: the issuer decides
Routing picks an acquirer. The acquirer sends the request through the card scheme to the issuer, which approves or declines and returns a response code.
Capture: the merchant or your software captures
For a two-step payment, the merchant captures the approved amount later, in full or in part. A one-step payment is captured at once.
Clearing: the acquirer submits
The acquirer sends the captured transactions to the card scheme, which passes them to the issuers.
Settlement: the issuer pays through the scheme, the acquirer pays out
The scheme moves funds from issuers to the acquirer, net of interchange. The acquirer pays the merchant, or pays you if you collect funds for your merchants.
After settlement: the merchant refunds, the issuer disputes, your team reconciles
Refunds and chargebacks arrive as new operations on the same payment. Your team matches settlement reports to the ledger.
The ledger holds this together. Each payment gets a unique identifier, and every capture, refund or chargeback is stored as a child of the first authorization. Without that link, a partial refund on a partly captured payment cannot be checked against the amount still available.
What Happens During Authorization and 3-D Secure?
During authorization, your software sends the request to the chosen acquirer, waits for the issuer’s response and stores its code. During 3DS, which comes first, your 3DS Server passes transaction and device data to the issuer, which lets the payment through or challenges the cardholder. Your rules decide when to ask.
The merchant chooses one of two flows for each payment, and your software must support both:
One-step payment
One request authorizes and captures the payment.
It fits digital goods and services delivered at once.
A cancellation after approval needs a refund or a reversal.
Two-step authorization and capture
The authorization holds funds; a later capture charges them.
It fits goods shipped later or amounts that change.
An unused hold is released with a void.
A hold does not last forever. Under section 5.7.3.5 of the Visa Product and Service Rules, an approval for a cardholder-initiated card-absent payment is valid for 10 calendar days, or 30 with an extended authorization indicator, a flag the merchant sets in the authorization request when it expects a longer hold. Your software should warn the merchant before that window closes.
Rule
Visa reversal deadlines
Section 5.7.3.6 of the Visa Product and Service Rules requires an authorization reversal within 24 hours. It applies to the unused difference when the final amount is smaller than the approved one. It also applies to the full amount when the payment is cancelled or the approval expires unused. The acquirer must accept a reversal its merchant sends (section 7.3.7.1).
Timeouts need the same care. If the acquirer does not answer, the issuer may still have approved. Send a reversal to the first acquirer before you try a second route, or the cardholder can be charged twice.
Declines are a separate case: card schemes limit how often a declined card may be sent again. Our guide to cascading logic covers those reattempt rules.
In the European Economic Area, 3DS is also a legal matter. Article 97 of PSD2, the second Payment Services Directive, requires strong customer authentication when the payer initiates an electronic payment. For remote payments, the authentication must be linked to the amount and the payee.
How Do Capture, Clearing and Settlement Work?
Capture turns an approved hold into a charge. The acquirer then clears captured transactions with the card scheme, and the scheme settles net amounts between issuers and the acquirer. Your software captures in time, records the amount that moved and reports what each merchant is owed. The money itself moves through the scheme and the acquirer.
Who acts at each post-authorization stage
Stage
What your software does
Who moves the money
Capture
Sends the full or partial amount against the authorization, and reverses the rest
No money moves yet; the issuer keeps the hold
Clearing
Passes captured transactions to the acquirer in real time or in a batch
The acquirer submits to the scheme, which forwards to the issuer
Settlement
Imports the acquirer’s settlement report and marks each transaction settled
The issuer pays through the scheme; the acquirer receives the net amount
Payout
Calculates each merchant’s amount after fees and any reserve
The acquirer pays the merchant, or pays you and you pay the merchant
A late capture is a scheme problem, not only a lost sale. If an approved payment is not processed within the Visa validity window, the issuer may dispute it under condition 11.3, No Authorization/Late Presentment (Visa Product and Service Rules, section 11.9.3.1). Capture jobs that run by rule should stop before the window ends.
Who receives settlement depends on your model. As a technical PSP, the acquirer pays your merchants directly and your software only reports. As a payment facilitator or aggregator, funds reach your account and the engine calculates each payout, including split payments for marketplaces.
How Does the Software Handle Refunds, Voids and Chargebacks?
Refunds, voids and chargebacks all reverse money on a payment, but different parties start them at different stages. A void releases a hold before capture. A refund returns captured money at the merchant’s request. A chargeback is started by the issuer for the cardholder. Your software must keep the three apart in the ledger.
Operations that reverse a payment
Operation
When it applies
Who starts it
What your software checks
Void
Authorized, not yet captured
Merchant or your software by rule
The hold still exists and has not been captured
Refund
Captured or settled
Merchant, through the API or back office
The total refunded stays within the captured amount
Chargeback
Settled, disputed by the cardholder
Issuer, through the scheme and acquirer
Links the dispute to the payment and freezes further refunds on it
Pre-arbitration
The merchant contests the chargeback
Acquirer, with the merchant’s evidence
The deadline and the evidence file for each case
The refund check prevents a common loss: a merchant refunds a payment that the cardholder has already charged back, and pays twice. The engine should block a refund once a chargeback is open.
24 hours
to reverse an unused or partly used authorization
120 days
for the issuer to raise a card-absent fraud dispute (condition 10.4)
30 days
for the acquirer’s pre-arbitration attempt after a fraud or authorization dispute
Source: Visa Core Rules and Visa Product and Service Rules, 24 October 2026 edition, sections 5.7.3.6, 11.8.5.4 and 11.3.2
Deadlines run from the processing date, so your software should show each open case with its days left.
Who pays when a merchant cannot cover a chargeback is a contract matter, explained in our guide on chargeback liability.
What Do Reconciliation and Reporting Cover?
Reconciliation matches three records: the transactions in your ledger, the settlement report from each acquirer and the credit on your bank statement. Reporting turns the same records into approval rates, volumes and amounts owed. Your finance team owns both. The software has to make every mismatch visible and traceable to one transaction.
Mismatches have a small set of causes: a capture the acquirer did not settle, a fee that differs from the contract, a chargeback debited before your system recorded it, or a payment approved after a timeout. Each one starts with the transaction identifier the acquirer reports.
Illustrative example
One day of settlement against the ledger
Assumptions: one acquirer, one currency, made-up figures, fees ignored. Your ledger shows 4,000 captured payments for 200,000.00, and 40 refunds for 2,000.00.
Item
Your ledger
Acquirer report
Action
Captures
4,000 / 200,000.00
3,998 / 199,900.00
Find the 2 missing captures and resubmit while the approval is valid
Refunds
40 / 2,000.00
40 / 2,000.00
Matched
Chargebacks
0
3 / 240.00
Record the 3 disputes and block refunds on those payments
Net to receive
198,000.00
197,660.00
The difference of 340.00 is explained by the rows above
The day closes only when every line of difference points to a transaction.
On our platform a daily close builds financial statements for each shop, and FinStatHub reconciliation matches transactions against bank statements. If you work as an aggregator, the same statements feed each merchant’s balance.
When a single payment fails or hangs, the reason sits in the messages exchanged with the acquirer. The back office should show these transaction logs to your support team without a ticket to the vendor.
Which Interfaces Does Payment Processing Software Need?
Payment processing software needs interfaces on two sides. Merchants reach it through a hosted payment page, a widget, an API, mobile SDKs and plugins. On the other side, connectors link it to acquirers and payment methods. The merchant interface you allow decides who collects card data, and with it the merchant’s PCI DSS scope.
Merchant interfaces and their effect on card data
Interface
Who collects the card data
Merchant’s PCI DSS scope
Fits
Hosted payment page
Your software, on its own page
Smallest: card data does not reach the merchant’s servers
Merchants on common shop platforms, or with no website
Prebuilt payment modules for shop platforms cut integration work for small merchants.
On the acquirer side, ask how many connectors exist, how fast a new one is built and who maintains it when the acquirer changes its specification.
Good to know
Control direct API access
Allow host-to-host integration only for merchants that have shown their own PCI DSS compliance. Keep it switched off by default and enable it for each shop, so an unregistered website cannot send card data straight to your API.
What Uptime, Latency and Security Requirements Apply?
Payment processing software must stay available when one acquirer fails, answer the checkout within seconds, process each request only once and protect card data under PCI DSS. Availability and speed are set by your contracts with merchants. Security rules come from the card schemes and the PCI Security Standards Council.
Availability
Monitor each acquirer connection and move its traffic when it slows down. In one of our cases an acquirer slowed to 30-second responses: see acquirer failure contained.
Latency and throughput
Set a timeout for each connector and test peak load before a large merchant goes live. Our post on transaction throughput explains what happens when a gateway hits its limit.
Idempotency
A repeated request with the same order identifier returns the first result instead of a second charge. This matters most after a network error on the merchant’s side.
Audit trail
Every request, response and manual change is logged with time and user. You need it for disputes, scheme audits and your own investigations.
PCI DSS responsibilities
PCI DSS is shared. The vendor validates the platform that stores, processes and transmits card data. Under Visa’s service provider rules, Level 1 covers 300,000 or more Visa transactions a year and needs an Attestation of Compliance from a Qualified Security Assessor every 12 months. You answer for your own systems and staff access. If you run a bank and are weighing your own audit against a vendor’s, read our post on outsourcing PCI DSS.
Payment pages need extra checks. PCI DSS v4.0.1 requirements 6.4.3 and 11.6.1 took effect on 31 March 2025. According to the PCI Security Standards Council, they require that payment page scripts are authorized, checked for integrity and monitored for tampering.
Which Deployment Model Fits Your Payment Processing Software?
Pick software as a service (SaaS) when you want the fastest start and no infrastructure team. Pick your own servers when data residency or bank IT policy requires it, or a lifetime licence when you want full control of the system. The model decides who runs uptime, who carries PCI DSS scope for hosting and who pays for capacity.
Deployment models compared
Model
Who hosts and runs uptime
PCI DSS scope for hosting
Launch on eComCharge
SaaS
Vendor, in its certified environment
Mostly the vendor’s
From 1 week
On-premises
You, on your own servers, with vendor support
Yours for the servers and network
From 3 months
Lifetime licence
You, with full control of the system
Yours for the servers and network
From 3 months
Own build
You, including every connector and scheme change
Fully yours
Not applicable
Shared SaaS does not have to mean shared capacity. In one of our cases a single high-volume merchant slowed a PSP’s whole pool until it moved to dedicated servers for one merchant inside the SaaS setup.
What Are the Risks of Payment Processing Software, and Who Does Not Need It?
The main risks sit at the hand-offs between stages: a timeout that turns into a double charge, a capture that comes too late, settlement nobody reconciles and stored cards that work with one acquirer only. Each has a known control. You may not need your own engine at all.
Risk
What goes wrong
How to reduce it
Double charge after a timeout
The issuer approved, the response was lost, and a second route charged again
Reverse on the first route before any retry, and match late responses
Late presentment
A capture after the approval window opens a dispute under Visa condition 11.3
Track approval age and stop capture jobs before the window ends
Unreconciled settlement
Missing captures and unexpected fees stay unnoticed for weeks
Reconcile daily and treat every unmatched line as an open case
One acquirer only
An acquirer that stops service stops all your merchants
Stored cards cannot be charged through a new route
Keep the vault in the gateway and request network tokens, which the card scheme issues and any acquirer can charge
Wider PCI DSS scope
Merchants on direct API integrations handle card data badly
Default to the hosted page and approve direct access shop by shop
Good to know
Who does not need payment processing software
A single merchant does not run an engine; it connects to a PSP. If you have one acquirer and a few merchants, you can resell that acquirer’s gateway first. If you are still choosing a licence and an acquirer, read how to start a payment processing company. Building from scratch only pays off at a scale our build vs buy calculator helps you test.
How Do You Test Payment Processing Software Before You Sign?
Test the engine in the vendor’s sandbox with the cases that break real systems, not with a single approved payment. Run each test yourself, through the API and the back office, and keep the results. The vendor answers questions; your team decides whether each test passed.
Tests to run in the sandbox
A two-step payment captured in part, with the rest reversed.
A void before capture and a refund after settlement.
Two partial refunds that together exceed the captured amount: the second must fail.
A refund attempt on a payment with an open chargeback.
An acquirer timeout, followed by a late approval.
The same request sent twice with one order identifier.
A 3DS flow that passes without a challenge, and a challenged one.
A settlement report imported and matched to the ledger.
A chargeback, shown with its deadline and evidence file.
The log of one failed payment, opened by your support team.
eComCharge is a white-label payment gateway that runs the processing engine for PSPs, acquiring banks and EMIs. It carries each payment from the merchant’s checkout through authorization, capture, refunds and chargebacks, and keeps the records for settlement and reconciliation. You run it under your own brand.
12 transaction types, including payment, authorization, capture, void, refund, reversal, chargeback, payout and person-to-person (P2P) transfer.
A hosted payment page and a payment widget, mobile SDKs, payment links and 40+ e-commerce plugins.
170+ active connectors with banks and payment methods, and 45+ currencies.
A 3DS Server certified by Visa, Mastercard and UnionPay, with 3DS applied by rule: no challenge, challenge or forced.
Payment processing software is the transaction engine of a payment service. It accepts the merchant's payment request, applies fraud and 3-D Secure rules, sends the authorization to an acquirer and records every later capture, refund and chargeback on the same payment. As a PSP, acquiring bank or EMI, you use it to settle and reconcile what your merchants process.
Payment processing software runs the transaction itself: authorization, capture, clearing, settlement and disputes. PSP software is the wider business system around it, with merchant onboarding, fee plans, invoicing and the back office. As a PSP you need both, and many platforms ship them together.
It depends on the scheme and the transaction. Under section 5.7.3.5 of the Visa Product and Service Rules, an approval for a cardholder-initiated card-absent payment is valid for 10 calendar days, or 30 with an extended authorization indicator, a flag the merchant sets when it expects a longer hold. An approval that will not be used must be reversed within 24 hours.
A void cancels an authorization before it is captured, so the hold is released and no money moves. A refund returns money that was already captured, at the merchant's request. A chargeback is started by the issuer on the cardholder's behalf, passes through the card scheme and the acquirer, and is debited from the merchant.
Responsibility is shared. The vendor validates the platform that stores, processes and transmits card data, for a Level 1 service provider with an annual assessment by a Qualified Security Assessor. You answer for your own systems and staff access. Each merchant's scope depends on its integration: a hosted payment page keeps card data off its servers.
SaaS gives the fastest start and leaves hosting, uptime and most of the hosting PCI DSS scope with the vendor. Your own servers suit you if you are a bank with data residency rules or strict IT policies, and move that work back to you. On eComCharge, SaaS takes from 1 week and your own servers from 3 months.
Not quite. A payment gateway is the part that accepts the payment from the merchant and passes it to an acquirer. Payment processing software covers the whole lifecycle, including capture, settlement, refunds, chargebacks and reconciliation. A white label payment gateway usually includes the full engine.
The cost depends on the deployment model, your transaction volume, the acquirer connectors you need and any custom work. A SaaS setup and a licence on your own servers carry different upfront costs. eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.
Respectfully, the eComCharge Team
eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.
How vertical SaaS platforms and the PSPs that serve them run embedded payments: the four models and their liability, recurring billing and SCA, failed renewals, cross-border acquiring, PCI DSS scope and the revenue maths.
How intelligent payment routing picks an acquirer for each payment in real time, joins routing with antifraud and 3DS, and recovers soft declines within Visa and Mastercard retry rules.
What payment service provider software includes, who uses each module, what a multi-merchant setup needs, how fees and payouts work, build vs white label, and which compliance duties stay with you.
A guide for PSPs, banks and EMIs adding peer-to-peer transfers through an API: how the funding and credit legs work, scheme push-payment rules, EU licensing and AML obligations, KYC limits, fraud controls and integration options.
An overview of payment routing for PSPs and banks: how a gateway chooses the acquirer for each online payment, the main rule types, static vs dynamic routing, least-cost routing, failover and cascading, KPIs and risks.
A chargeback explained for PSPs and acquirers: who is involved, how the dispute cycle runs, Visa's four reason categories, time limits, who carries the loss and when a merchant can respond.