Skip to main content
Fiserv IPG (Internet Payment Gateway) is a payment processing platform from Fiserv, a global financial services technology company. It provides card payment processing for businesses worldwide.

​
Setup

Fiserv IPG provides self-service sign-up for a sandbox account. To sign up for an account, visit the Fiserv registration page.

​
Connector configuration

After setting up your Fiserv IPG connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:
  • Using Flow - Configure Fiserv IPG as the target connector in Flow to automatically route card transactions to this connector
  • Using the API - Explicitly set the payment_service_id parameter to the Fiserv IPG connector ID when creating transactions. This overrides any Flow routing rules.
The connector ID can be found in the dashboard under Connections -> Configured connections.

​
Credentials

When setting up Fiserv IPG in the dashboard, configure the following credentials from the Fiserv portal.
  • API key - The API key from the Fiserv dashboard under API Keys.
  • Secret key - The secret key found under the API key in the Fiserv dashboard under API Keys.
  • Store ID - Your Fiserv store identifier.
Fiserv

​
Features

Fiserv supports the following features:
  • Delayed capture - Authorize a payment and capture it at a later time
  • Partial capture - Capture a portion of the authorized amount
  • Partial refunds - Refund a portion of the captured amount
  • Refunds - Refund a captured payment
  • Void - Cancel an authorized transaction before capture
  • Zero auth - Verify a card without charging it
  • Digital wallets - Support for Apple Pay, Google Pay, and other wallet integrations
  • Network tokens - Enable network tokenization when configured
  • Issuer-based installments - Support for installment payment plans
  • Transaction sync - Synchronize transaction status with Fiserv
  • 3-D Secure - Pass-through 3DS authentication

​
Supported countries

Fiserv supports transactions from buyers in the following countries:
Country codeCountry codeCountry codeCountry codeCountry codeCountry codeCountry codeCountry code
ADAEAFAGAIALAMAO
AQARASATAUAWAXAZ
BABBBDBEBFBGBHBI
BJBLBMBNBOBQBRBS
BTBVBWBYBZCACCCD
CFCGCHCICKCLCMCN
COCRCUCVCWCXCYCZ
DEDJDKDMDODZECEE
EGEHERESETFIFJFK
FMFOFRGAGBGDGEGF
GGGHGIGLGMGNGPGQ
GRGSGTGUGWGYHKHM
HNHRHTHUIDIEILIM
INIOIQIRISITJEJM
JOJPKEKGKHKIKMKN
KPKRKWKYKZLALBLC
LILKLRLSLTLULVLY
MAMCMDMEMFMGMHMK
MLMMMNMOMPMQMRMS
MTMUMVMWMXMYMZNA
NCNENFNGNINLNONP
NRNUNZOMPAPEPFPG
PHPKPLPMPNPRPSPT
PWPYQARERORSRURW
SASBSCSDSESGSHSI
SJSKSLSMSNSOSRSS
STSVSXSYSZTCTDTF
TGTHTJTKTLTMTNTO
TRTTTVTWTZUAUGUM
USUYUZVAVCVEVGVI
VNVUWFWSYEYTZAZM
ZW

​
Supported currencies

Fiserv supports processing payments in the following currencies:
Currency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency code
AEDAUDAWGBBDBHDBIFBRLBSD
BYNBZDCADCHFCNYCZKDKKDOP
EURGBPGYDHKDHUFILSINRJMD
JPYKRWKWDKYDMXNMYRNOKNZD
OMRPLNRONRSDRUBSARSEKSGD
SRDTRYTTDTWDUSDVESXCDXCG
ZAR

​
Limitations

The following features are not supported by this connector:
  • Over capture - Capturing more than the authorized amount is not supported
  • Partial authorization - Partial authorization is not supported
  • Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
Additional limitations include:
  • Google Pay CVV - To accept Google Pay transactions, your Fiserv merchant account or store ID must have the CVV field set as non-mandatory.

​
Integration

To accept card payments with Fiserv, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which routes the payment to your configured Fiserv connection based on your Flow rules or explicit payment_service_id parameter.