The Chase Paymentech Orbital® Payment Gateway enables online payment processing for the most basic storefronts or for highly integrated e-commerce systems. Merchants can establish secure online transaction processing in a true one-stop-shop environment.

Features

✅ Refund A creditcard payment processed with can be / according to its status. ✅ Payment Authorization Payments can be authorized by customers using Credit Card. ✅ Payment Capture Payment authorizations made using Credit Card payment methods can be captured. This step happens automatically with CHARGE transactions.

Resources

Configuration

To set up your Orbital gateway account, you'll need a Merchant ID. Depending on the platform you are boarded on at Chase, the BIN could be 000001 or 000002. For setup assistance and to ensure proper configuration, you might need to use Chase’s 12-digit PNS number in the MID field if boarded on the Tandem platform. For any setup needs or assistance with new credentials, contact Chase's customer support directly.

This table describes the required or possible attributes needed to configure a merchant product for this type.

Name	Type	Description	Rules
host		Base URL used for API requests to the Orbital gateway.
username		Username for API authentication with Orbital. Examples: api_user.
password		Password for API authentication with Orbital. Examples: securepassword.
industryType		Type of industry for the transaction, as required by Orbital. Examples: EC.
bin		Bank Identification Number used for the transaction. Examples: 000001.
merchantId		The merchant identifier for processing transactions with Orbital. Examples: merchant_123456.
terminalId		Terminal identifier for processing transactions with Orbital. Examples: 001.

Enabling this Product

Using create-merchant-product API you can add a new product to your merchant record. Below is an example configuration for the payload of that request.

{
  "line": "payments",
  "product": "creditcard",
  "provider": "orbital",
  "config": {
    "username": "api_user",
    "password": "securepassword",
    "industryType": "EC",
    "bin": "000001",
    "merchantId": "merchant_123456",
    "terminalId": "001"
},
  
}

Data Mapping

The following bullet points outline the mapping of data fields between the Authvia platform and the system, detailing the correspondence of specific attributes for seamless data integration.

Authvia transaction.reference.external maps to orderID
Authvia transaction.id maps to comments
Authvia transaction.description maps to UNMAPPED
Authvia transaction.references.customer maps to UNMAPPED
Authvia merchant.id maps to UNMAPPED