Setup
Checkout.com provides a self-service sign-up for a sandbox account. To sign-up for an account visit the sign-up page and fill in the details.Connector configuration
After setting up your Checkout.com connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:- Using Flow - Configure Checkout.com 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 Checkout.com connector ID when creating transactions. This overrides any Flow routing rules.
Credentials
When setting up Checkout.com in the dashboard, configure the following credentials, which are obtained from Checkout.com:Public key
The Checkout.com Public key is obtained from the Checkout.com Developer Dashboard under the Developers -> Overview heading. Then click ”+ Create a new key”

Secret key
As with the public key, navigate to the same section and select ”+ Create a new key” Once in, select “Secret API key”
Webhook secret key
Use this value to verify webhook signatures from Checkout.com. Webhooks are required for this connector.Payout funding account
Use this value to enable payouts and original credit transactions.Features
To use Checkout.com your account needs to be enabled for theirfull API
feature. To enable it, please contact the Checkout.com Integration team at
integration@checkout.com.
Checkout.com 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
- Partial authorization - Support partial approval responses
- Void - Cancel an authorized transaction before capture
- Zero auth - Verify a card without charging it
- Refunds - Refund a captured payment
- Digital wallets - Support for Apple Pay, Google Pay, and other wallet integrations
- Network tokens - Enable network tokenization when supported by Checkout.com
- 3-D Secure - 3DS authentication
Supported countries
Checkout.com supports transactions from buyers in the following countries:| Country code | Country code | Country code | Country code | Country code | Country code | Country code | Country code |
|---|---|---|---|---|---|---|---|
AT | AU | BE | BG | BR | CA | CH | CY |
CZ | DE | DK | EE | ES | FI | FR | GB |
GR | HK | HU | IE | IN | IT | JP | LT |
LU | LV | MT | MX | MY | NL | NO | NZ |
PL | PT | RO | SE | SG | SI | SK | US |
Supported currencies
Checkout.com supports processing payments in the following currencies:| Currency code | Currency code | Currency code | Currency code | Currency code | Currency code | Currency code | Currency code | Currency code | Currency code |
|---|---|---|---|---|---|---|---|---|---|
AED | AFN | ALL | AMD | AOA | ARS | AUD | AWG | AZN | BAM |
BBD | BDT | BGN | BIF | BMD | BND | BOB | BRL | BSD | BWP |
BZD | CAD | CDF | CHF | CLP | CNY | COP | CRC | CVE | CZK |
DJF | DKK | DOP | DZD | EGP | ETB | EUR | FJD | FKP | GBP |
GEL | GIP | GMD | GNF | GTQ | GYD | HKD | HNL | HTG | HUF |
IDR | ILS | INR | ISK | JMD | JPY | KES | KGS | KHR | KMF |
KRW | KYD | KZT | LAK | LBP | LKR | LRD | LSL | MAD | MDL |
MGA | MKD | MMK | MNT | MOP | MUR | MVR | MWK | MXN | MYR |
MZN | NAD | NGN | NIO | NOK | NPR | NZD | PAB | PEN | PGK |
PHP | PKR | PLN | PYG | QAR | RON | RSD | RUB | RWF | SAR |
SBD | SCR | SEK | SGD | SHP | SLE | SOS | SRD | SZL | THB |
TJS | TOP | TRY | TTD | TWD | TZS | UAH | UGX | USD | UYU |
UZS | VND | VUV | WST | XAF | XCD | XCG | XOF | XPF | YER |
ZAR | ZMW |
Limitations
The following features are not supported by this connector:- Over capture - Capturing more than the authorized amount is not supported
- Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
- Transaction sync - Transaction synchronization is not supported
Integration
To accept card payments with Checkout.com, 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.