Setup
Speak to your Chase Orbital account manager to obtain sandbox credentials for your region. To sign-up for a Chase Orbital test account, visit developer center account and select Get Access.Connector configuration
After setting up your Chase Orbital connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:- Using Flow - Configure Chase Orbital as the target connector in Flow to automatically route card transactions to this connector
- Using the API - Explicitly set the
payment_service_idparameter to the Chase Orbital connector ID when creating transactions. This overrides any Flow routing rules.
Credentials
When setting up Chase Orbital in the dashboard, configure the following credentials.- Merchant ID - The Chase Orbital assigned Merchant ID for your account. You can see this in the Chase Orbital Development Center Dashboard -> Overview -> Project -> Acquirer ID.
- Username - The Chase Orbital username shared by your account manager.
- Password - The Chase Orbital password shared by your account manager.
Reporting credentials
If you use settlement reporting, configure the following reporting credentials from Chase Orbital.- SFTP username - Your SFTP username for reporting exports.
- SFTP password - Your SFTP password for reporting exports.
- SFTP address - The SFTP host address for reporting exports.
- Merchant ID - The Merchant ID for the reporting account.
Features
Chase Orbital supports the following features:- Delayed capture - Authorize a payment and capture it at a later time
- Partial capture - Capture a portion of the authorized amount
- Partial refunds - Refund a portion of the captured amount
- Refunds - Refund a captured payment
- Void - Cancel an authorized transaction before capture
- Zero auth - Verify a card without charging it
- Digital wallets - Support for Apple Pay, Google Pay, and other wallet integrations
- Network tokens - Network tokenization is enabled by default
- Settlement reporting - Access settlement reporting via SFTP
Supported countries
Chase Orbital supports transactions from buyers in the following countries:| Country code | Country code | Country code | Country code | Country code | Country code | Country code | Country code |
|---|---|---|---|---|---|---|---|
AD | AE | AF | AG | AI | AL | AM | AO |
AQ | AR | AS | AT | AU | AW | AX | AZ |
BA | BB | BD | BE | BF | BG | BH | BI |
BJ | BL | BM | BN | BO | BQ | BR | BS |
BT | BV | BW | BY | BZ | CA | CC | CD |
CF | CG | CH | CI | CK | CL | CM | CN |
CO | CR | CU | CV | CW | CX | CY | CZ |
DE | DJ | DK | DM | DO | DZ | EC | EE |
EG | EH | ER | ES | ET | FI | FJ | FK |
FM | FO | FR | GA | GB | GD | GE | GF |
GG | GH | GI | GL | GM | GN | GP | GQ |
GR | GS | GT | GU | GW | GY | HK | HM |
HN | HR | HT | HU | ID | IE | IL | IM |
IN | IO | IQ | IR | IS | IT | JE | JM |
JO | JP | KE | KG | KH | KI | KM | KN |
KP | KR | KW | KY | KZ | LA | LB | LC |
LI | LK | LR | LS | LT | LU | LV | LY |
MA | MC | MD | ME | MF | MG | MH | MK |
ML | MM | MN | MO | MP | MQ | MR | MS |
MT | MU | MV | MW | MX | MY | MZ | NA |
NC | NE | NF | NG | NI | NL | NO | NP |
NR | NU | NZ | OM | PA | PE | PF | PG |
PH | PK | PL | PM | PN | PR | PS | PT |
PW | PY | QA | RE | RO | RS | RU | RW |
SA | SB | SC | SD | SE | SG | SH | SI |
SJ | SK | SL | SM | SN | SO | SR | SS |
ST | SV | SX | SY | SZ | TC | TD | TF |
TG | TH | TJ | TK | TL | TM | TN | TO |
TR | TT | TV | TW | TZ | UA | UG | UM |
US | UY | UZ | VA | VC | VE | VG | VI |
VN | VU | WF | WS | YE | YT | ZA | ZM |
ZW |
Supported currencies
Chase Orbital supports processing payments in the following currencies:| Currency code | Currency code | Currency code | Currency code |
|---|---|---|---|
CAD | EUR | GBP | USD |
Limitations
The following features are not supported by this connector:- Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
- Partial authorization - Partial authorization is not supported
- Transaction sync - Transaction synchronization is not supported
Integration
To accept card payments with Chase Orbital, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:- Embed - A pre-built, customizable payment form that handles the complete payment flow
- Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
- Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
payment_service_id parameter.
Connection options
You can sendcomments as part of the connection_options. Gr4vy passes the
value as the order comments in Chase Orbital.