Common configuration fields

There are some common fields you must complete for every gateway configuration. We recommend reviewing our Setting Up payment gateways documentation for information on these common fields:

• Name

• Use Gateway Test Environment

• Cards Accepted

• Default Authorization Amount Except for Discover, all other card networks support $0 authorization. For Discover, use $1 or higher for authorization.

• Verify new payment method (optional)

• Verify updated payment method (optional)

Specific configuration field

In addition to the common fields, every gateway has unique requirements and information (such as credentials and certain rules) that you must provide to configure the gateway in Zuora.

The Industry Type for your merchant account can be found by logging into your Orbital Virtual Terminal and viewing the setup for your merchant ID (MID). Alternatively, you can also contact your Chase Orbital Account Executive or technical.priority.support@chase.com to determine which default Industry Type is set up for your MID(s).

It is possible for your transactions to be obtained using an Industry Type that is different than the Industry Type set up for your MID. In this case, when configuring the payment gateway in Zuora, you should select the Industry Type for how the transaction is actually obtained. For example, you could have an MID whose default setup in Chase Orbital is eCommerce transaction, but the transactions are Recurring Payment. In this case, you would configure the Orbital payment gateway profile in Zuora using the Industry Type of Recurring Payment.

Generally, if you are accepting orders through your website, you will use the eCommerce transaction Industry Type, and if these transactions are accepted on a recurring basis, you will use the Recurring Payment Industry Type. However, please discuss with your Chase Orbital Account Executive or technical.priority.support@chase.com to determine what industry type to use when configuring this gateway in Zuora.

For authorization and payment transactions using Credit Card or Google Pay payment methods, the Industry Type field is populated by using the following prioritized sources:

1. Gateway Options: The Industry Type value in the gatewayOptions field takes precedence.
2. Gateway configuration setting: If no value is available in the gatewayOptions field, the Industry Type value specified on the gateway instance configuration page is used.
3. The RC value: If neither of the preceding sources provides the Industry Type value, RC is used.

BIN

The BIN number is the Transaction Routing Definition and this is assigned by Chase Orbital. The Orbital Gateway (Salem/Stratus Platform) uses only BIN 000001. Therefore, when configuring your Orbital Gateway (Salem/Stratus Platform) in Zuora, you will see only one option to select from, that is Salem - 000001 or Stratus - 000001.

Merchant ID

The merchant ID (MID) is the merchant account number assigned to you by Chase Orbital. This Orbital MID is your Salem Division (TD) number. This MID number should be the same one you provided to Zuora Global Support to enable in your tenant, and the ID(s) will appear as a picklist in the gateway configuration page. If you have more than one Merchant ID number, you can set up multiple gateway configurations for each Merchant ID number.

The MID may also be referred to as the Transaction Division (TD) number or Presenter ID.

The Orbital Gateway (Salem/Stratus Platform) MID is a 6 digit numeric value such as: 041756. This account number matches your host platform number. There are two host platforms available for the Orbital Gateway: Salem (or Stratus) and Tampa. The Orbital Gateway (Salem/Stratus Platform) uses a 6 digit numeric MID while the Orbital Gateway (Tampa Platform) uses a 12 digit numeric MID.

JPMPP Merchant ID

This is the ID of your merchant account used for strong customer authentication (SCA). Contact Chase Merchant Services to get your merchant account set up for SCA.

JPMPP Merchant Password

This is the password of your merchant account used for strong customer authentication (SCA). Contact Chase Merchant Services to get your merchant account set up for SCA.

Enable Level 2 Card Data

Level 2 Card Data provide customers and merchants with additional information on their credit card statements about their purchases such as the amount of sales tax they pay and to reconcile transactions with a unique customer code.

Select this check box if you want to enable Level 2 card data processing. Note that if the tax amount is 0, the Level 2 data will not be sent to the Chase Orbital gateway.

For details about the required data, see Level 2 and Level 3 data mapping for Chase Orbital gateway . For more information about Zuora's support for Level 3 and Level 2 data, see Level 2 and Level 3 Card Data .

Enable Level 3 Card Data

Enabling 3 Card Data means additional order and line item is passed to Orbital when processing a credit card transaction. This information may result in lower interchange rates on eligible commercial, corporate and purchasing cards. This functionality must also be enabled for your Chase Orbital account.

Select this check box if you want to enable Level 3 card data processing. If Enable Level 3 Card Data is enabled, you must configure the following fields. Otherwise, the Level 3 and Level 2 data will not be sent to the Chase Orbital gateway.

• Commodity Code : Commodity codes are used in Level 3 data by accounts payable and procurement software to classify the goods purchased. There is no universally accepted commodity code standard, but the United Nations Standard Products and Services Code (UNSPSC) is widely deployed. An example of the UNSPSC Commodity Code for Software is 43230000. Orbital accepts a maximum of 12 characters.

• Unit of Measure

For details about the required data, see Level 2 and Level 3 data mapping for Chase Orbital gateway . For more information about Zuora's support for Level 3 and Level 2 data, see Level 2 and Level 3 Card Data .

Enable Safetech Fraud Service

To enable the Safetech Fraud service in Zuora, select the following checkboxes for your needs. Before enabling this service in Zuora, ensure that you have enabled it through the Chase Pay Orbital portal. See Set up Safetech for more information.

• Enable Safetech Fraud Service for Payment Method Verification Additional order information and customer parameters are passed to the Safetech Fraud Management tool for evaluation in the request of the following API operations or Payment Pages 2.0:

  • Payment method creation API operations, such as Create a payment method

  • Verify a payment method API operation

  • The Gateway Options client parameters in Payment Pages 2.

• Enable Safetech Fraud Service for Delay Capture Authorization Additional order information and customer parameters are passed to the Safetech Fraud Management tool for evaluation in the request of the Create authorization API operation. Note that this setting is only available for the Chase Paymentech Orbital Gateway integration.

The following table lists the fields that Zuora sends to Chase Orbital for Safetech integration:

For the fields starting with "gwOptions_", you must leverage the Gateway Options fields ( gatewayOptions field for API operations and param _gwOptions_[option] parameter for Payment Pages 2.0) to pass in values.

Enable gateway reconciliation

In Zuora, select Enable gateway reconciliation and configure the following credentials:

• Reconciliation Username : SFTP username for the reconciliation.

• Reconciliation Password : SFTP password for the reconciliation. This password expires every three months. Therefore, you need to reset the password every three months on the Orbital side and in Zuora configuration.

• Unzip File Password : Password to unzip files for the reconciliation.

Reconciliation reports are scheduled to run daily at 23:00:00 PDT. Zuora automatically retrieves the reports and they can be viewed by accessing Payment Operations > Gateway Reconciliation .

Zuora recommends you to enable the Gateway Reconciliation Job Completion | Reconciliation Completed Notification. With this notification turned on, you will get notified if the Gateway Reconciliation job fails because you forgot to reset the password or for any other reason. See Notifications for more information.

Enable AVS field length validation

If you select this check box, Zuora will truncate the value of the following AVS request fields based on the field length limitations of the Orbital gateway:

Note that the acceptable characters are alphanumeric characters, including 0~9, a~z, and A~Z. Special characters like ä will be considered as 2 characters. Hence, if special characters are used in the AVS validation fields, you might get a length validation error.

Soft Descriptor

Soft Descriptor is used to define the merchant name or product description that will appear on the customer's statement. This field is required if you want to use Soft Descriptor.

Merchant Phone Number

The merchant phone number or the phone number that is associated with your Orbital merchant account.

Additional configuration fields for Chase Orbital v6.3.0

The following fields are supported only in Chase Orbital version 6.3.0 and previous versions.

Enable AVS Filtering

If enabled, Zuora will decline Credit Card transactions for certain AVS response codes returned by the gateway, even if the gateway has approved the transaction. This setting is disabled by default.

The following table is a list of AVS response codes that Zuora will reject when this setting is enabled.

Enable CVV Filtering

If enabled, Zuora will decline Credit Card transactions for the following response code returned by the gateway, even if the gateway has approved the transaction. This setting is disabled by default.

CVV response code N = CVV No Match