IPG

Merchants can configure transactions on Carat Portal to be routed by many acquirers and payment methods. One of these is IPG (Internet Payment Gateway) by First Data/fiserv.

Thus, the store can configure Carat Portal so that transactions made with VISA cards, for example, are routed through IPG while those made with MASTERCARD are routed through BIN.

Supported Carat Portal interfaces

The following interfaces for integration with IPG are available:

• REST Payment
  • REST Card query
• REST Pre-Authorization
• REST Cancellation

Permitted Authorizers

The following authorizers / issuers are available for integration with IPG:

• VISA
• MASTERCARD
• ELO
• AMERICAN EXPRESS
• HIPER
• SOROCRED
• CABAL

Required credentials

The merchant must obtain with IPG the credentials listed below, and pass them to Software Express or make the registration as explained later in this document.

Parameter	Description	Format
ipgMerhantApiKey	Merchant identification on IPG.	< 32 AN
ipgMerchantApiSecret	Merchant key generated by IPG.	< 16 AN
ipgEndPointURL	URL for IPG API REST.	< 200 AN

Registration of information through the merchant's portal

The merchant can register the information obtained with IPG on the Merchant's Portal on Carat Portal. For this purpose, the merchant must select the authorizer and enter the editing screen as in the example shown below:

In the editing environment of the Authorizer, you can change the configurations registered on the Carat Portal environment. In this case, the change will only occur for this authorizer. Note that if merchant uses the same IPG account, it will be necessary to manually change passwords for all the other authorizers.

Transaction flow

In this section, we will present the particularities of the IPG transactional flow.

Card query

For card query request with "routing-id" field set to IPG, will be returned card details provided by IPG. For more details, click here

Payment with recurring indication

In the IPG routing it is possible to make payment with recurrence indicator (Learn more). To sign recurring payments, send the following payment parameters:

• acquirer.recurrency with the value true;
• acquirer.is_first_recurring with the value true to indicate that the transaction is the first in a series of recurring transactions, or false in opposite case.