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.
  • Payment facilitator fields - When operating as a payment facilitator, provide the sub-merchant details described in Payment facilitator (Omnipay).
Fiserv

Payment facilitator (Omnipay)

Payment facilitator support uses Fiserv’s Omnipay platform and is enabled per connection, by request only. It is not available by default. Contact Gr4vy to have it configured, and note that your Fiserv account must also be enabled for payment facilitator (sub-merchant) processing on Fiserv’s side.
Fiserv’s Omnipay platform supports the payment facilitator (PayFac) processing model, also referred to as the aggregator model. This differs from the merchant of record model. When enabled, the Fiserv connector sends sub-merchant details with each transaction so funds and reporting are attributed to the correct sub-merchant. The following sub-merchant fields are configured as connector credentials on the enabled connection:
  • MCC - The merchant category code for the sub-merchant.
  • Legal name - The sub-merchant’s registered legal name.
  • Email - The sub-merchant’s contact email.
  • Merchant ID - The sub-merchant identifier.
  • Address - The sub-merchant’s address, including address lines, city, region, postal code, and country.
The sub-merchant object is only accepted if your Fiserv account is enabled to operate as a payment facilitator. If it is not, Fiserv rejects the transaction with Sub merchant data not supported. Ask Fiserv to enable payment facilitator processing on your account before going live. You can test against a Fiserv sandbox account in the meantime.
See Payment facilitators for how PayFac support works across connectors.

Zero-dollar authorizations

On the Fiserv connector, zero-dollar (account verification) authorizations are sent to Fiserv as a standard authorization for a zero amount. This applies to all Fiserv card connections, not only payment facilitator connections.

Capabilities

This connector supports the Mastercard Transaction Link Identifier (TLID). Gr4vy stores the TLID from the first customer-initiated payment and sends it on later merchant-initiated payments, with nothing to enable.

Installments

Fiserv supports issuer installments, such as interest-free installments in Mexico (MSI). When a transaction includes installment_count, Gr4vy sends it to Fiserv in order.installmentOptions as the number of installments, without interest. For MSI, set the transaction’s country to MX. Gr4vy then leaves out recurringType, because Fiserv rejects it on MSI payments. For any other country, or none, Gr4vy sends recurringType as FIRST, or as REPEAT when is_subsequent_payment is true. Gr4vy doesn’t send stored credential fields on installment payments, even when store is true.

Capture, void, and refund

Fiserv only accepts installments on a sale. Gr4vy sends these payments as a sale, and Fiserv captures them straight away, whatever the intent. Set intent to capture, so the transaction shows as capture_succeeded and you can refund it as usual. With intent set to authorize, the transaction shows as authorization_succeeded in Gr4vy, although Fiserv has already captured the funds. You can only refund it through Gr4vy after you capture it in Gr4vy.
  • Capture - Capture the full amount, before Fiserv settles the payment. While Fiserv reports the payment as captured, Gr4vy records the capture without capturing the payment again. After Fiserv settles the payment, Gr4vy sends the capture to Fiserv as a new request. A partial capture records less in Gr4vy than Fiserv took.
  • Void - Don’t void a payment made with installment_count alone. Gr4vy sends Fiserv a pre-authorization void, which doesn’t release a sale, so the funds stay captured. A payment that also has the connection option is voided differently.
  • Refund - Refund the transaction once it’s captured in Gr4vy.

Installment connection option

Before installment_count existed, Fiserv installments were set with the installmentOptions connection option. It still works, and it lets you set more of Fiserv’s installment fields. Gr4vy passes each field unchanged in order.installmentOptions:
  • numberOfInstallments
  • installmentsInterest
  • installmentDelayMonths
  • merchantAdviceCodeSupported
A payment made with the connection option is also captured straight away. When a transaction sets both, Gr4vy creates the payment with installment_count instead of the option’s fields. Voiding a transaction that has the connection option sends Fiserv a refund for the full amount. The transaction then shows as authorization_voided in Gr4vy, although Fiserv refunded the payment. Voids follow the connection option even when the transaction also sets installment_count.

Supported countries

Supported currencies

Limitations

  • Google Pay CVV - To accept Google Pay transactions, your Fiserv merchant account or store ID must have the CVV field set as non-mandatory.
  • Settlement split - Omnipay’s settlementSplit (dividing funds across multiple accounts) is not currently supported. Payment facilitator connections receive the full settlement amount.

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 - Embed SDKs for iOS, Android, and React Native
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.