The term "payment gateway" gets used loosely - sometimes to mean the whole payments stack, sometimes to mean just the checkout widget. Understanding precisely what a gateway does, and how it sits alongside an acquirer and a processor, makes it much easier to evaluate your options and avoid buying a solution to a problem you do not actually have.
Gateway, acquirer, processor - the plain-English version
When a customer enters their card details at checkout, three things need to happen: the data needs to be transmitted securely, the transaction needs to be authorised by the card network and the cardholder bank, and the funds need to move into your account. Different parties handle different parts of this.
The gateway is the first leg. It encrypts the card data and passes it on. The processor sits in the middle - it routes the transaction between the gateway, the card networks (Visa, Mastercard, eftpos), and the issuing bank. The acquirer is the bank or financial institution that holds your merchant account and ultimately settles the funds into your account. In practice, many providers bundle two or three of these roles together, which is why the language gets muddy. When someone says "payment gateway" they often mean the whole hosted layer that handles all three.
What to look for when choosing
Reliability is first. Card acceptance is a core revenue function - gateway downtime means lost sales. Look at published uptime records and whether the provider has transparent status pages. Fees matter too, and transparency matters more than the headline rate. Understand whether you are paying per-transaction fees, monthly minimums, and what the surcharging rules mean for passing costs to customers - the card surcharging rules in Australia have specific requirements about what you can and cannot pass on.
Payout timing is often overlooked. Some gateways settle daily, others take two or three business days. For a hospitality or retail business managing cash flow tightly, the difference between same-day and two-day settlement is real money. Also check which payment methods are supported. Buy-now-pay-later, digital wallets, and eftpos routing all behave differently and not every gateway handles all of them.
Integration quality and PCI compliance
The gateway you choose will touch your website, your app, your POS, and potentially your accounting software. Poor integration quality - outdated SDKs, missing webhooks, no sandbox environment for testing - creates ongoing development cost. Good gateways have clear documentation, stable APIs with versioning, and support for the tools you are already using. If you are thinking through how payments fit into your broader POS integration, the gateway is a foundational choice, not an afterthought.
On security: look for a gateway that handles cardholder data on its own infrastructure so your systems are out of scope for PCI DSS. Hosted payment pages, tokenisation, and 3D Secure support are the markers to look for. A gateway that keeps your application out of the card data flow dramatically reduces your compliance burden.
How it fits your stack
For most hospitality and retail businesses, the gateway decision is intertwined with the acquiring relationship. It is worth separating the questions: "which gateway has the best integration for our stack" and "which acquirer gives us the best rates" are different decisions, and in some setups you have flexibility to mix them. In others - particularly bundled terminal and gateway products - you are making one decision that covers both.
The right answer depends heavily on your transaction volume, whether you are taking payments in-person, online, or both, and what you are already running. If you are building or re-evaluating your payments stack and want a second opinion, tell us about your project - we have been on both sides of this decision.
Frequently asked questions
- What is a payment gateway and how does it work?
- A payment gateway is the technology layer that securely captures and transmits card data from a checkout - online or in-person - to the payment processor and card networks. It encrypts the transaction data, routes the authorisation request, and returns an approval or decline to the merchant in real time.
- What is the difference between a payment gateway and a payment processor?
- The gateway is the secure transmission layer - it captures and encrypts card data and sends it on. The processor handles the routing of the authorisation request between the gateway, the card network, and the cardholder bank. Many providers bundle both roles, which is why the terms are often used interchangeably, but they are technically distinct functions.
- How do I choose a payment gateway for my business in Australia?
- Start with reliability, then look at total fee structure including monthly minimums and surcharging rules, payout timing, supported payment methods, and integration quality with your existing tools. For Australian businesses, also check eftpos routing support and whether the gateway handles PCI compliance on your behalf through hosted payment pages or tokenisation.