Payment Gateway
Payment Gateway is the technology layer that securely transmits payment data between the customer's card (or digital wallet), the merchant's POS or checkout system, and the acquiring bank, authorizing, encrypting, and routing each transaction for settlement. The gateway transmits card details for authorisation. The processor moves the money and the merchant account holds it, which is why the three are priced separately.
When a customer clicks 'Pay Now,' a chain of real-time decisions runs in milliseconds, and the payment gateway sits at the start of it. A payment gateway is a technology layer that authenticates, encrypts, and routes electronic payment transactions between a buyer's bank and a merchant's acquiring bank. For finance teams it matters beyond the technical setup: gateway fees, settlement timing, and reconciliation behavior feed straight into cash flow reporting and AR close accuracy.
How a payment gateway moves money through the stack
When a payment is submitted, the gateway tokenizes the card data, passes an authorization request through the card network (Visa, Mastercard, etc.) to the issuing bank, and returns an approval or decline in near real time. Approved transactions are batched and settled through the acquiring bank, usually within one to three business days. Finance teams need to map gateway settlement cycles to their AR aging logic. A transaction authorized on Monday may not clear the bank until Wednesday, and that timing gap affects daily cash positioning.
Where it gets complicated
A common misread is treating 'payment gateway' and 'payment processor' as the same thing. They are separate layers with separate fee lines. The gateway charges for the authorization service, often a per-transaction fee plus a monthly platform fee. The processor moves the actual funds and charges interchange-plus or flat-rate fees. When you build a reconciliation feed into your ERP or AR automation tool, account for the two fee streams separately so that net revenue and payment processing cost are reported accurately on the P&L.
Integrating a gateway into ERP and AR automation
Take a SaaS company processing 800 subscription renewals per day through Stripe. The gateway produces a settlement report listing gross charges, refunds, disputes, and net payout per batch. The company's AR automation software pulls this report via API, matches each transaction to an open invoice by customer ID, and posts the receipt in the ERP. Any transaction that can't be matched (a currency mismatch, a duplicate charge, a failed webhook) lands in an exceptions queue for manual review. That makes settlement timing and API reliability finance criteria for choosing a gateway, as well as IT criteria.
Questions to ask
- What are the per-transaction and monthly platform fees, and how do they change at volume thresholds?
- What is the settlement cycle (same day, next day, or T+2), and does it match our cash flow reporting cadence?
- Does the gateway provide a machine-readable settlement report (CSV, API) that our ERP or AR tool can ingest automatically?
- How does the gateway handle disputes and chargebacks, and what is the expected timeline for funds returned?
- What tokenisation and PCI-DSS compliance standard does the gateway use, and what liability does that shift to us?
- Can the gateway support multi-currency settlement, and how are foreign exchange conversions applied and reported?
- What is the gateway's documented uptime SLA, and what is our contingency if the gateway is unavailable at month-end close?
Where finance teams get payment gateway accounting wrong
The most common error is booking the gross charge as revenue and treating the gateway net payout as cash, which understates revenue and misclassifies processing fees. Teams also fail to reconcile in-transit amounts: funds authorized but not yet settled sit in neither the bank ledger nor the AR subledger, creating a float that distorts daily cash reports. A clean gateway reconciliation maps the gross charge to revenue, processing fees to expense, and the payout to cash, posted on the settlement date rather than the authorization date.
Gateway, processor, merchant account
Three components often sold as one product. The gateway captures and transmits the transaction for authorisation. The processor routes it through the card networks and settles it. The merchant account is where settled funds land before transfer to the business bank account. Bundled providers hide the split, which simplifies setup and makes it harder to change one component later without changing all three.
Comparing POS systems
POS systems separate on what the payment processing costs and whether you can change processor without replacing the terminals. Once payment gateway is settled as a requirement, read the Point of Sale Software category guide for how the market splits, then weigh the Square profile against the Toast profile on that requirement rather than on the feature list. No head-to-head comparison is published in this category yet, so the profiles listed in the Point of Sale Software guide are the place to compare. Before you book demos, put your own numbers through the point of sale ROI calculator so the business case is written down before a vendor writes it for you.
Frequently asked questions
Is a payment gateway the same as a merchant account?
No. A merchant account is a bank account that holds funds after a transaction settles. A payment gateway is the software layer that authorises and routes the transaction. You need both, though many modern providers like Stripe bundle them into one service, which simplifies setup but can complicate fee transparency for finance teams.
How often should finance teams reconcile gateway settlements?
Daily reconciliation is best practice for high-volume businesses. Each batch settlement should be matched to open invoices and posted to the GL on the settlement date. Monthly-only reconciliation creates a backlog of unmatched exceptions that is difficult to resolve once transaction context is stale.
What happens to gateway fees in a refund scenario?
Most gateways do not return the original authorization fee on a refund; at most, the interchange component may be credited. Track refunded amounts gross and record non-refundable gateway fees as a separate expense line, so processing costs aren't understated in the period the refund is issued.
Related terms
Inventory Sync and POS Transaction come up in the same workflow as payment gateway, and the rest of the POS systems cluster is indexed in the finance operations glossary.