The upgrade to Orbital 7.0.1 gives you the ability to process credit cards, ACH, SEPA, UK Direct Debit and credit card reference transactions.
This feature is in Limited Availability. If you want 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 Orbital Gateway.
Set up Safetech
If you want to use the Safetech Fraud Security tool and Zuora’s Billing system, Chase Orbital and Zuora recommend that you reach out to your JP Morgan account manager before configuring in Zuora. You might have to sign a fee schedule specifically for Safetech, then you can obtain your Safetech ID.
When you have secured your Safetech ID, request your JP Morgan account manager to put you in contact with a Safetech analyst who will assist you with training and setting up the Safetech tool. Once you are ready to implement, refer to Chase’s developer portal for Safetech specifications.
After Safetech is integrated into your payment pages, see the sections below to understand the Zuora fields that can pass onto Chase Orbital for fraud check.
Additional Orbital 7.0.1 Configuration Fields
In addition to common configuration fields, you also have to configure the 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 Orbital 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 Pay Orbital 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
SFTP username for Reconciliation.
- Reconciliation Password
SFTP password for 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.
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:
AVS Fields Field Length Limitation AVSname 30 characters AVSaddress1 30 characters AVSaddress2 30 characters AVScity 20 characters AVSphoneNum 14 characters AVSzip 10 characters
This option is only available in Orbital 6.4.4 and Orbital 7.0.1, and it is not selected by default.
Orbital Gateway Reconciliation Prerequisites
Gateway reconciliation for Orbital version 7.0.1 is enabled through the Chase Orbital portal.
- Contact Orbital to get access to the Orbital Virtual Terminal Scheduled Reporting.
- Enable Closed Batch Detail Report and Rejected Batch Detail Report.
- Set Report type to File/CSV.
- Set Delivery method 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.
Supported Safetech Fields
Chase Orbital 7.0.1 Integration supports the following Safetech fields:
If you are using the Verify payment method REST API or Payment Pages 2.0 to verify a payment method, you must leverage the
param_gwOptions_[option] parameter to pass in the values to these fields. See Client Parameters for Payment Pages 2.0 for more information. Note that the
field_deviceSessionId client parameter for Payment Pages 2.0 is not applicable.
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.
Currently, only existing Chase Orbital Payment Gateway tokens are supported as a Credit Card Reference Transaction payment method type. Creating tokens in Zuora is not supported.
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.
<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> <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>