How does a payment gateway work?
The customer enters card details or chooses a method at checkout. The gateway encrypts the data, formats it as an authorization request and sends it to the processor or acquirer, which forwards it through the card network to the issuing bank. The issuer approves or declines, and the answer travels back the same way, usually within a few seconds. Many gateways also run 3-D Secure, store tokens for repeat payments and apply basic fraud screening before the request leaves.
Why does a payment gateway matter for approval rate?
The gateway decides what data the issuer receives. Missing fields, such as cardholder name, billing address or 3-D Secure results, give issuers less to work with and can turn a borderline payment into a decline. Timeouts matter too. As an illustrative example: if 1% of 50,000 monthly attempts time out at the gateway, 500 payments never reach the issuer at all, regardless of how creditworthy the customers are.
How is a gateway different from a PSP or an orchestration layer?
A gateway is the connection. A PSP is a commercial package that usually bundles a gateway, an acquiring relationship, payment methods, settlement and risk tools under one contract. An orchestration layer sits above several gateways and PSPs and decides which one handles each payment. A merchant can have one gateway and no orchestration, or one orchestration layer connected to many gateways.
Where does Omno use it?
Omno connects to the gateway APIs of its PSPs. The merchant integrates with Omno’s single API, Omno translates each request into the selected provider’s format, and responses and webhooks come back in one consistent structure.