Knowledge Center

Knowledge Center > Billing and Payments > Payment Gateways > Supported Payment Gateways > Chase Paymentech (Orbital) Gateway

Chase Paymentech (Orbital) Gateway

Chase Paymentech is a leading credit card processor and payment gateway provider. Zuora is pre-integrated with Chase Paymentech's Orbital.

Prerequisites

Obtain a Chase Paymentech Orbital Gateway Account on the Salem Platform

Chase Paymentech provides two host platforms for the Orbital Gateway: Salem and Tampa. However, Zuora's only supports the Orbital Gateway (Salem Platform).

If you have not yet signed up for a gateway account, get in touch with your account representative or our sales team through zuora.com. We can refer you to the right contacts to ensure that you are set up with a gateway account that is compatible with Zuora.

If you have an existing Chase Paymentech Orbital gateway account, make sure it is using the Salem Platform. 

Zuora does not support the Orbital Gateway (Tampa Platform) so please make sure your gateway account is configured using the right host platform. If you are not sure which hosting platform your Orbital Gateway is using, the Orbital Gateway (Tampa Platform) uses BIN 000002) and has a 12 digit PNS Merchant ID number.

Link Your Merchant ID to Zuora's Submitter ID

In order for Zuora to submit payment transactions to Chase Paymentech's Orbital gateway on your company's behalf, your Chase Paymentech Merchant ID(s), also known as the Presenter ID, will need to be linked to Zuora's Submitter ID (SID). If you are planning to configure more than one merchant ID number in Zuora, make sure all merchant IDs are linked to Zuora's SID. Alternatively, you can ask for your IDs to be linked to Zuora's SID at the chain level, which ensures the link is done at the company level and any merchant IDs associated with the company will be linked automatically to Zuora's SID. Please ensure both your Orbital Production and Test accounts are linked. 

You can work with your Chase Paymentech relationship/account manager, or contact the Chase Paymentech support team to request the accounts be linked. Chase Paymentech Support can be reached at 1-866-645-1314 or GatewaySupport@ChasePaymentech.com. If it is an urgent matter, please contact their support team by phone. Support is provided 24x7.

Zuora's Submitter ID: 056839.

Processing Error if Account is Not Linked

If you attempt to process test or production transactions in Zuora or create a new payment method, the following error may occur if your merchant IDs have not been linked to Zuora's SID: "ProcStatus:20412 - Precondition Failed: Security Information is missing. Error processing transaction."  If this error occurs, please contact Chase Paymentech to ensure your accounts are properly linked. 

Enable the Orbital Gateway for Your Tenant

Once you have linked your merchant IDs to Zuora's SID, you can contact Zuora Global Support with your merchant ID number(s) so that our support team can enable the gateway in your tenant. 

Zuora recommends that merchants use Orbital 7.0.1 to pass additional Level 2 and Level 3 data potentially reducing transaction costs and to take advantage of additional reconciliation and security features.

Configure the Orbital Gateway

To set up Orbital as your gateway, enter your Orbital credentials in the Z-Payments Settings > Setup Payment Gateway page. When selecting a Gateway Type, choose Chase Paymentech (Orbital Gateway).

Chase Paymentech Orbital Gateway Config.jpg

Common Fields for Configuration

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
  • Verify new credit card (optional)
  • Verify updated credit card (optional)
  • 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. Default is disabled.

  • Enable CVV Filtering

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

Credentials

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. 

Industry Type

Industry type defines the industry type for the transaction and identifies how transactions are obtained.  This information is passed in the transaction request submitted to Chase Paymentech. Please select the appropriate industry type, choosing from one of the following:

  • Mail Order Transaction
  • Recurring Payment
  • eCommerce Transaction

CP Orbital Salem Credentials.jpg

Select the Correct Industry Type

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 Paymentech Account Executive or Orbital support 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 gateay 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 Paymentech 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 Paymentech Account Executive or Orbital support to determine what industry type to use when configuring this gateway in Zuora. 

BIN

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

Merchant ID

The merchant ID (MID) is the merchant account number assigned to you by Chase Paymentech. 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.

Merchant ID Format

The Orbital Gateway (Salem 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 and Tampa. The Orbital Gateway (Salem Platform) uses a 6 digit numeric MID while the Orbital Gateway (Tampa Platform) uses a 12 digit numeric MID.

Zuora does not support the Orbital Gateway (Tampa Platform) so please make sure your gateway account is configured using the right host platform. If you are not sure which hosting platform your Orbital Gateway is using, the Orbital Gateway (Tampa Platform) uses BIN 000002) and has a 12 digit PNS Merchant ID number.

Enable AVS Filtering

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

Code Description
2 Bill-to address did not pass Auth Host edit checks
5 Edit-error - AVS data is invalid
E Zip No Match / Zip 4 Match / Locale no match
G No match at all
JC International street address and postal code not verified
N5 Address not verified (International only)

Enable CVV Filtering

The CVV response code N = CVV No Match will be rejected by Zuora when this setting is enabled.

Setting Up Multiple Gateway Profiles for the Same MID

If you obtain payments using different methods, you may need to create multiple payment gateway profiles in Zuora using the same MID but with a different Industry Type selected in each profile.

If you accept all credit cards, it is recommended that you configure two gateway instances. One gateway for Visa and Mastercard with the default authorization amount set to $0. This will result in reduced transaction fees when payments are processed.

Configure a second gateway instance for all other credit cards with the default authorization amount set to $1 or higher. Default amounts set to $0 only applied to Visa and Mastercard. Processing other credit cards with this value will produce an error when the payment is processed.

Testing Your Configuration

Zuora recommends testing your selected payment gateway using both your payment gateway's test and production (live) environments. Once you have completed testing in the gateway's test environment, it is recommended that you perform a test in your live production environment with a real credit card. If there are any differences in the configuration of your testing and production accounts, testing in production ensures your production merchant account is set up properly and can successfully connect to the production environment.

Accessing Your Gateway's Test Environment

Some payment gateways provide separate credentials for merchants to access their testing environment, some gateways use the same credentials for testing as for the production (live) environment but direct test transactions to a different URL, and other gateways do a little of both. To access the Orbital Gateway test environment, you simply have to select the Use Test Gateway Environment option in Zuora when configuring your payment gateway profile. 

Accessing Test or Production (Live) Mode from Zuora

When configuring the Orbital payment gateway in Zuora, you can indicate whether you would like to use the Orbital test environment or the Orbital production environment. 

  • If Use Gateway Test Environment is selected, Zuora will direct payment transactions to the Orbital test environment. The address for this system is orbitalvar1.paymentech.net, port 443.

You will be accessing a test environment linked to Zuora's submitter ID. This environment is a testing simulator.

  • If Use Gateway Test Environment is not selected (disabled), Zuora will direct payment transactions to the Orbital production (live) environment. The address for this system is orbital1.paymentech.net, port 443.

Chase Paymentech Orbital Test.jpg

Test Credit Cards and Testing Scenarios

Please contact the Chase Paymentech Orbital Support team for test credit card numbers and testing scenarios. Their Merchant Certification Department can provide you the appropriate documentation for testing. Chase Paymentech Support can be reached at 1-866-645-1314 or GatewaySupport@ChasePaymentech.com.

General Testing Information

Integration Testing

Zuora has been certified with Chase Paymentech as an integration partner and maintains the integration on an ongoing basis, thoroughly testing the integration with every new release. The Chase Paymentech (Orbital Gateway) integration documentation is helpful if you are integrating the Orbital gateway directly with your website, however, you do not need to perform any integration or certification testing to submit transactions to the Orbital gateway via the Zuora application. The intended audience for the integration guides are technical integrators, however, these documents can be helpful to non-technical integrators who can refer to it for information on testing and troubleshooting gateway errors (as described below).

Performance and Volume Testing

In general, gateway testing environments are intended to give merchants the opportunity to test their gateway and integrations to their gateway, in order to work out any bugs before going to the production environment. Some gateway test environments are shared amongst multiple merchants, and other gateways provide unique testing environments for each merchant. Additionally, gateway test environments (also referred to as certification or sandbox environments) do not have the same high availability or performance capability as production environments. As such, they are not intended for load testing. Merchants performing high volumes of load testing that puts a stress on a shared test environment may receive a warning from the gateway or have their access to the testing environment suspended.

Troubleshooting Gateway Errors

There are several ways to obtain information on gateway errors:

  1. Refer to the Chase Paymentech's Orbital Gateway Java Documentation* for information on response codes, values, and descriptions. This SDK and other Chase Paymentech documentation can be downloaded from Chase Paymentech's Orbital Integration Library.
  2. Look up the transaction by the transaction ID number (in the Zuora payment detail page, this is the Reference ID and Secondary Reference ID numbers) in virtual terminal to see if more information is provided; often you will see more than just the response (reasons) code and response message in Zuora.
  3. If you require additional information, you can contact Chase Paymentech Support can be reached at 1-866-645-1314 or GatewaySupport@ChasePaymentech.com.

ProcStatus Errors

ProcStatus errors are errors sent by the Chase Paymentech Orbital gateway to Zuora, these transactions did not pass the gateway validation and thus were rejected by Chase Paymnetech. Such transactions do not get sent to the payment processor nor card issuing banks. Chase Paymentech will return an error to Zuora with a definition of the error so that action can be taken by the customer (for example, fix the data provided for the payment method or use a different payment method).

ProcStatus:20412 - Precondition Failed: Security Information is missing. Error processing transaction.

If you attempt to process test or production transactions in Zuora or create a new payment method, the following error may occur if your merchant IDs have not been linked to Zuora's SID: "ProcStatus:20412 - Precondition Failed: Security Information is missing. Error processing transaction."  If this error occurs, contact Chase Paymentech to ensure both your test and production accounts are properly linked.

ProcStatus Errors #839, 840, and 841 have to do with an invalid credit card account number.

These errors refer to "PAN" which stands for Primary Account Number (the credit card number). When the end customer encounters these errors, it is recommended that the user re-enter their credit card account information. Here are some specific PAN errors: 

  • 839 PWS_ERR_VALIDATION_PAN_LUHN Fix = Typically associated with a transaction where an account that does not pass our BIN/MOD10 check.

This error is typically associated with a transaction where an account does not pass Chase Paymentech's BIN/MOD10 validation of the credit card number. BIN stands for Bank Identification Number and MOD10 refers to the checksum formula used to validate the credit card number.

Chase Paymentech will validate the BIN by checking the first six digits of the credit card number, which are also known as the Issuer Identification Number (IIN). The BIN identifies the card issuing financial institution (for example Visa or MasterCard), and is used to route transactions to the appropriate card issuing banks for approval and settlement. 

The MOD 10 check-digit routine distinguishes whether a credit card number is valid by using an algorithm to compute the last digit of a credit card number based on a calculation of all the digits preceding the last number on a credit card. Refer to (search for MOD 10 check-digit routine) for an example of how the MOD 10 check-digit routine is performed on a credit card number.

  • 841 PWS_ERR_VALIDATION_PAN_RANGE Fix

This error is typically associated with a transaction where no credit card number is submitted to the gateway or the credit card number is invalid (for example, contains invalid characters or does not fall within a valid BIN Range). As mentioned above, the BIN is the first six numbers of a credit card that identifies the credit card type (for example: Visa or Mastercard), and the bin range is the range of numbers applicable to the credit card as designed by the card issuing bank. 

Make Sure You Are Not Re-Trying an Invalid Card Too Many Times

We recommend that you check the payment in Zuora to see how many times the same payment method has been retried for payment and failed. If there have been several retries, check the error messages from the beginning with the first failure and the more recent failures to determine if the error message is the same. If a merchant tries to process a payment against the same credit card too many times despite receiving errors, this could trigger warnings to the card issuing bank. The card issuing bank may place an alert on the account and not allow any further transactions from the merchant using that payment method. When a merchant has been flagged, the error received on the payment may be not state the reason why, instead it might be a generic error decline error. In this case, the merchant (Zuora customer) should work with Chase Paymentech Support to see if they can identify the problem with the payment method. If the processor does not know, then the merchant and/or the card holder can try calling their card issuing bank to look into the issue.

</h>

Last modified
02:55, 16 May 2017

Tags

This page has no custom tags.

Classifications

(not set)