How a payment gateway works
Think of a payment gateway as a secure message relay for payment data. When a customer enters their card details at checkout and hits "Pay", here is what happens:
- The gateway encrypts the payment information and sends it to the acquiring bank (the merchant's bank).
- The acquiring bank routes the request through the relevant card network — Visa, Mastercard, or another network.
- The card network forwards it to the cardholder's issuing bank for approval.
- The issuing bank returns an approval or decline.
- The gateway relays that result back to the checkout — usually within a second or two.
The customer sees "Payment successful" or a decline message. Behind that simple result is a chain of authorisations moving across multiple systems, all orchestrated by the gateway.
Gateways also handle important security work: encrypting card data, running tokenisation (replacing card numbers with safe tokens), and supporting 3D Secure authentication. A gateway handles the authorisation step only — it does not hold your money. Funds settlement (the transfer into your merchant account) is handled by the acquiring bank, usually within a few business days. Many businesses use a payment service provider that bundles the gateway, acquiring, and other services into one product, so you interact with a single platform rather than managing them separately.
Hosted checkout vs API gateway
Gateways come in different integration styles depending on how much control you want over the checkout experience.
A hosted checkout redirects customers to a payment page managed by the provider. It is fast to deploy and the provider handles PCI compliance for that page — ideal if your team wants to launch quickly without building a form from scratch.
An API gateway lets you build the checkout UI yourself and pass payment data directly via code. This gives you full control over the experience, at the cost of more development work and stricter PCI scope.
If you are evaluating options in Singapore, ONE's payment gateway in Singapore covers supported methods, pricing, and how to get started.
What to look for in a payment gateway
When comparing gateways, the key factors to weigh are:
- Supported payment methods — cards alone are rarely enough. Local rails (like PayNow in Singapore) and digital wallets (Apple Pay, Google Pay) matter for conversion.
- Pricing transparency — watch for per-transaction fees, monthly fees, and international card surcharges. Understanding the full cost up front avoids surprises.
- Integration options — hosted checkout, payment links, and direct API access let you launch fast and add sophistication later.
- Settlement speed — how quickly approved funds reach your account matters for cash flow.
- Developer documentation — clear API references and sandbox environments make integrations faster.