Getting Started » Introduction
Welcome to Checkout.com's documentation site! On this page you'll find everything you need to begin integrating with one of our flexible payment solutions.
Our Getting Started guide will walk you through all our major features, starting with our simplest payment solution, Checkout.js, all the way through to how to complete and manage charges through our Merchant API.
If you're integrating with Checkout.com for the first time, we recommend reading through the entire Getting Started section to familiarise yourself with our solutions and features. For those already comfortable with our payment platform, feel free to jump ahead to:
Checkout.com offers three browser-based payment solutions that are suitable for non-PCI compliant merchants, Checkout.js v2, Checkout.js, and CheckoutKit.js.
Both Checkout.js and CheckoutKit.js can be used in conjunction with our Merchant API to support:
Not a developer? You can still benefit from Checkout.com's full suite of payment solutions with our range of plugins for popular shopping carts.
Please contact us to set up a test merchant account. After we create your account, we will send you two emails:
- Confirmation email from our Integration Team containing your secret key and public key.
- Account creation email from The Hub, our reporting dashboard, along with login credentials.
Once you have both emails, you’re ready to start integrating in our Sandbox Environment.
A different set of keys is required for each business channel.
If you have any questions during the integration process, do not hesitate to contact our Integration Team.
You can safely test your integration within our Sandbox environment, which allows you to easily apply your Sandbox configuration to your live environment by toggling the Sandbox/Live switch - just remember to swap your test key for your live key!
Please refer to our Testing and Simulating Charges page for information on how to simulate charges with test cards and trigger different types of responses from Checkout.com's payment gateway.
Sandbox accounts are archived after three months of inactivity and all transactional test data is deleted, though the account remains accessible. If your account is idle for six months, it will be deleted. Once deleted, a new account will be required to simulate charges.