IPG — Internet Payment Gateway
Fiserv’s gateway — hosted checkout and a direct API, with an Australian integration path that is its own thing.
- Provided by
- Fiserv
- Category
- Acquirer-tied
Recorded as tied because that is what the Australian package is in practice. Gateway-only access with an external acquirer is not something Fiserv publishes for Australia, and it should be confirmed rather than assumed.
- Status
- Current
- Integrations
- Hosted checkout (Connect), Direct API, XML/SOAP (Australian integration), REST API (regional)
- Features
- Tokenisation, Recurring payments
- Payment methods
- Apple Pay, Google Pay
- Also acquires
- Yes — Fiserv is an acquirer too
Fiserv’s Internet Payment Gateway is sold across several markets and the Australian deployment is not identical to the others. The documented Australian integration path is XML over SOAP, while REST endpoints appear in other regional IPG offerings — so a developer working from the global docs can get a long way down the wrong road.
Hosted checkout, branded Connect, covers merchants who want the card fields off their own servers. Tokenisation, recurring payments, Apple Pay and Google Pay are supported, with the fraud package depending on what has been bought.
The thing to settle before committing is whether the Australian arrangement is gateway-only or full-stack. Fiserv is an acquirer as well as a gateway provider, and its Australian merchant package should not be assumed to permit an external acquirer behind it.
Developer resources
Fiserv's own documentation, for whoever has to build against IPG — Internet Payment Gateway.
What it costs
Fiserv does not publish gateway fees for IPG — Internet Payment Gateway. The merchant service fee is negotiated on your volume and card mix. Find out what yours should be.
On IPG — Internet Payment Gateway?
No callbacks, no waiting. Your quote on screen in minutes, from Australia’s major providers.