Knowledge Center

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

Chase Orbital Version 7.0.1 Integration

The upgrade to Orbital 7.0.1 gives you the ability to process credit cards, ACH and credit card reference transactions. 

This feature is in Limited Availability. If you wish to have access to the feature, submit a request at Zuora Global Support

For complete information about enabling, configuring, and testing an Orbital gateway, see Chase Paymentech (Orbital) Gateway.

Orbital 6.3.0, Orbital 6.4.4, and Orbital 7.0.1 Selected Feature Comparison

The following table compares a subset of features where there are changes in support between Orbital 6.3.0, Orbital 6.4.4, and Orbital 7.0.1. 

Function Feature Orbital 6.3.0 Orbital 6.4.4  Orbital 7.0.1 
Verification AVS (Orbital) Supported Supported Supported
CVV (Orbital) Supported Supported Supported
AVS Filtering (Zuora) Supported Not Supported,
Deprecated
Not Supported,
Deprecated
CVV Filtering (Zuora)  Supported Not Supported,
Deprecated
Not Supported,
Deprecated
Payment Methods Credit Card Supported Supported Supported
Debit Card (Using Debit Card Networks) Supported

Not Supported

Not Supported

Apple Pay Not Supported Not Supported Supported
Bank Transfer (ACH) Supported Supported Supported
SEPA Direct Debit Not Supported Supported Supported
UK Direct Debit Not Supported Supported Supported
Safetech Fraud and Security Not Supported Supported Supported
Tokenization (using CC Ref Transactions) Not Supported Supported Supported
Payment Processing Gateway Options Supported

Supported

Supported

Soft Descriptor Supported Not Supported Not Supported
Level 2 Data Not Supported Supported Supported
Level 3 Data Not Supported

Supported

 

Supported

 

Delayed Capture: Single Capture Supported

Supported

Supported

Payment Void/Cancel Void Supported Supported Supported
Refund Processing Referenced Refunds Supported Supported Supported
Non Referenced Refunds Supported Supported Supported

Additional Orbital 7.0.1 Configuration Fields

The following sections show how to configure additional fields that are available in Orbital 7.0.1.

  • 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. 
  • 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 Paymentech account.

Contact Zuora Global Support to enable Level 3 Card Data for your tenant. To use this feature Level 3 Card Data must also be enabled for your Chase merchant account.

  • 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. This field is required if you have enabled Level 3 Card Data
  • Enable Safetech Fraud Service

Safetech Fraud Service is enabled through the Chase Paymentech portal. When enabled, additional order information and customer parameters are passed to the Safetech Fraud Management tool for evaluation using Zuora's API or Hosted Payment Page. 

  • Safetech Merchant ID
  • Safetech Fraud Score Indicator
  • Enable gateway reconciliation
    See Gateway Reconciliation for more information.
  • Reconciliation Username
  • Reconciliation Password

Orbital Gateway Reconciliation Prerequisites

Gateway reconciliation for Orbital version 7.0.1 is enabled through the Chase Paymentech portal.

  1. Contact Orbital to get access to the Orbital Virtual Terminal Scheduled Reporting.
  2. Enable Closed Batch Detail Report and Rejected Batch Detail Report.
  3. Report type set to “File/CSV”.
  4. Delivery method set to “SFTP”.

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.

Credit Card Reference Transactions

Complete the following prerequisites for credit card reference transactions:

  • Enable the credit card reference transaction method of payment. To complete this action, click your username at the top right, navigate to Settings > Payments > Payment Method, click Edit, and select CC Reference Transaction.
  • Contact Zuora Global Support to enable the Payment Tokenization feature for your tenant.

Zuora supports Orbital tokens. Tokens are used for credit card reference transactions in Zuora. A reference transaction is simply a representation of a credit card payment method without having sensitive payment method information like the credit card number stored in Zuora. Please note that the token cannot be used with another gateway, which is why we recommend storing credit card information in Zuora whenever possible.

See the following topics for more information about setting up credit card reference transactions in Zuora.

The following SOAP API call can be used to create a payment method that represents an Orbital-stored credit card.

Request example:

<ns1:create>
  <ns1:zObjects xsi:type="ns2:PaymentMethod">
    <ns2:AccountId></ns2:AccountId>
    <ns2:SecondTokenId></ns2:SecondTokenId>
    <ns2:TokenId></ns2:TokenId>
    <ns2:Type>CreditCardReferenceTransaction</ns2:Type>
  </ns1:zObjects>
</ns1:create>

Response example:

<Response>
   <NewOrderResp>
       <IndustryType></IndustryType>
       <MessageType>A</MessageType>
       <MerchantID>041756</MerchantID>
       <TerminalID>001</TerminalID>
       <CardBrand>VI</CardBrand>
       <AccountNum>XXX</AccountNum>
       <OrderID>2umnRgb7ceOiRksqhZdik3</OrderID>
       <TxRefNum>57B1E2338499034E722099B6575E1C9B0B9E54D5</TxRefNum>
       <TxRefIdx>0</TxRefIdx>
       <ProcStatus>0</ProcStatus>
       <ApprovalStatus>1</ApprovalStatus>
       <RespCode>00</RespCode>
       <AVSRespCode>JB</AVSRespCode>
       <CVV2RespCode>N</CVV2RespCode>
       <AuthCode>tst940</AuthCode>
       <RecurringAdviceCd></RecurringAdviceCd>
       <CAVVRespCode></CAVVRespCode>
       <StatusMsg>Approved</StatusMsg>
       <RespMsg></RespMsg>
       <HostRespCode>100</HostRespCode>
       <HostAVSRespCode>IB</HostAVSRespCode>
       <HostCVV2RespCode>N</HostCVV2RespCode>
       <CustomerRefNum></CustomerRefNum>
       <CustomerName></CustomerName>
       <ProfileProcStatus></ProfileProcStatus>
       <CustomerProfileMessage></CustomerProfileMessage>
       <RespTime>113931</RespTime>
       <PartialAuthOccurred></PartialAuthOccurred>
       <RequestedAmount></RequestedAmount>
       <RedeemedAmount></RedeemedAmount>
       <RemainingBalance></RemainingBalance>
       <CountryFraudFilterStatus></CountryFraudFilterStatus>
       <IsoCountryCode></IsoCountryCode>
       <CTIAffluentCard>N</CTIAffluentCard>
       <CTICommercialCard>Y</CTICommercialCard>
       <CTIDurbinExemption>N</CTIDurbinExemption>
       <CTIHealthcareCard>N</CTIHealthcareCard>
       <CTILevel3Eligible>Y</CTILevel3Eligible>
       <CTIPayrollCard>X</CTIPayrollCard>
       <CTIPrepaidCard>N</CTIPrepaidCard>
       <CTIPINlessDebitCard>N</CTIPINlessDebitCard>
       <CTISignatureDebitCard>N</CTISignatureDebitCard>
       <CTIIssuingCountry>USA</CTIIssuingCountry>
   </NewOrderResp>
</Response>
Last modified
18:44, 10 May 2017

Tags

Classifications

(not set)