This is the web client half of a custom cart integration. The server half, which is identical for web, iOS, and Android, is covered in the overview.
Server libraries are available for TypeScript, Python, Go, C#, and PHP, or call the API directly. See SDKs.

Pre-requisites

You must have a Bolt Merchant account to begin. If you do not yet have an account, contact sales to begin onboarding. A merchant account and API keys are not sufficient on their own. A payment processor, Trusted Domains, and a division set up as a custom cart are all required, and each one fails in a way that is hard to diagnose from the browser. See prerequisites and readiness for the full checklist and the checks you can run before wiring up a storefront.

API Keys

You must have access to your merchant account’s production and sandbox keys to set up this integration. Both admin and developer-level roles have access to keys; if you are a developer and you do not have access, reach out to your Bolt Admin.
  1. Login to the Merchant Dashboard.
  2. Navigate to Administration > API.
  3. Scroll to API Keys and click the eye icon to reveal your keys.
The Publishable Key supports the multi-step checkout use case by default. To build other checkout flows such as Payment-Only, switch divisions using the Division dropdown. The publishable key is a long string of lower and upper case letters and numbers that consists of three sections.

Environments

You must have all of the following merchant accounts set up to build, test, and deploy your integration:
Never share your API Keys or Signing Secrets externally.

Configure your integration

Set your API keys and environment URLs as configuration for whichever language or library you’re integrating with.
.env
Initialize a client from that config using the official library for your language:
TypeScript

The four pieces

  1. Generate an order token by sending a POST request to /v1/merchant/orders.
  2. Install the Checkout Button on your storefront using /v1/checkout_button.
  3. Build out your Merchant Callback API to interact with the Bolt API and handle various operations for the order, such as:
  4. Listen for transaction webhooks related to the order’s changing transaction status. These are configured separately from your Merchant Callbacks.