Set up and configure a FiservCommerceHub payment gateway instance

Basic Information

• Name: Specify a name for the gateway instance.
• Use Gateway Test Environment: When setting up the payment gateway integration, if you want Zuora to use the payment gateway's test service URL, select this checkbox.

Credentials

The following credentials provided by Fiserv must be configured. When a merchant account is set up with the Fiserv gateway, the following information is assigned by the gateway. The information is used to identify the account through which the transaction will be processed.

• Merchant Id
• Terminal Id
• API Key
• API Secret

Rules

• Cards Accepted: Select the cards you want to accept. Make sure your gateway's merchant account is also configured to support the same cards you have configured in Zuora. If you submit a transaction for a card type that is not enabled in your merchant account, it will result in an error stating the CardType is not supported or that you are not signed up for that tender type.
• Default Authorization Amount: Specify the minimum default amount used to authorize or validate a payment. The default value of this field is 1. 
• Verify new payment method: Select this checkbox to verify the payment methods when creating them. By default, this checkbox is selected. For tokenized payment methods, you must validate them in Zuora so that payments made with these payment methods are successful.
• Verify updated payment method: Select this checkbox to verify the payment methods when updating them. By default, this checkbox is selected. For tokenized payment methods, you must validate them in Zuora so that payments made with these payment methods are successful.
• Enable Network Tokens: Select this checkbox to include the following field in payment creation or authorization requests sent to the gateway. The gateway uses this indicator field to retrieve and store network tokens, which are used for subsequent transactions linked to the gateway token. The gateway does not return the network tokens to Zuora or notify Zuora of any failures related to creating network tokens. 

  • "transactionInteraction": {
    "posEntryMode": "CREDENTIAL_ON_FILE"
    }

• Custom field mapped to Association Response Code: Use this field to store the association response code. This code indicates the outcome of a transaction from the card issuer's perspective and is crucial for understanding why a transaction was approved or declined. Note that the association response code is not sent if the payment fails before reaching the card issuer.
• Custom field mapped to Merchant Advice Code: Use this field to store the merchant advice code from the gateway. The payment network returns this code to indicate the reason for a transaction's approval or decline, providing more specific information and guidance on how to handle it.

  Note: Merchant Advice Code is only sent on transaction decline for Visa and Mastercard.

• Custom field mapped to Host Response Code: Use this field to store the host response code. This code provides the specific, detailed status of a transaction from the payment processor, offering more granular information than a general response code. The Host Response Code will always be sent by the processor, even if the Association Response Code is not sent.