To get started using the Quick Checkout for Adobe Commerce extension you must complete a few onboarding steps to connect your instance with our checkout functionality.
If Gainsight is enabled, it triggers the Take the tour button in your Quick Checkout Admin panel about Quick Checkout for Adobe Commerce:
On the Admin sidebar, go to Stores > Configuration > Advanced:
If Gainsight is not enabled, continue with the onboarding steps.
See the Quick Checkout Admin panel topic for more information.
If you do not configure your Bolt accounts you cannot set up your sandbox or production environments.
In order to use the Quick Checkout, you must have the following available for Bolt:
Refer to the prerequisites topic for more information.
See API credentials to learn how to create or access your API keys for your instance.
See the install topic for detailed information about obtaining the extension.
Before configuring the Quick Checkout in your Adobe Commerce Admin it is required to create a sandbox and production merchant accounts in Bolt. Provide all of the required details to create an account in Bolt.
Refer to the test and validate topic for more information.
To use the Quick Checkout you require Bolt unique keys and signing secret. Obtain the following API keys by navigating to Developers > API > Keys in the Bolt Merchant Dashboard.
API key: A private key used by your back end to interact with Bolt APIs.
Publishable key: A key used by your front end to interact with Bolt APIs.
Signing secret: Used for signature verification on requests received from Bolt.
See the Bolt environment details page to learn about keys and signing secret from Bolt for the Quick Checkout extension.
You must create API keys for both sandbox and production environments.
To connect your payment services provider follow the steps described in the processor setup developer Bolt page.
Yes
.Quick checkout fields are only visible when Enable is set to Yes
.
Select method (Sandbox or Production) to use.
Validate credentials after providing your unique API and Publishable keys.
Refer to the Settings topic for more information on the configuration options for the Quick Checkout for Adobe Commerce extension.
You must provide unique API and Publishable keys before enabling the extension otherwise customers will see a payment form and will not be able to place an order.
On the Admin sidebar, navigate to Stores > Configuration > Checkout to access the general Checkout Admin config page.
In the Service Settings section, provide all details required to enable the extension.
Set Payment Action to either option:
Authorize
: Do not capture transaction automatically upon authorization.Authorize and Capture
: Capture transaction automatically upon authorization.For more information on the Adobe Commerce standard checkout options, refer to the checkout topic.
To enable the Quick Checkout for Adobe Commerce extension:
To check if the shopper has a Bolt account:
Switch the scope to Main Website.
Click the Configure Callback URL button. This enables Bolt to determine if the shopper has an account. If they do, the OTP pop-up appears.
Switching the scope to the Main Website ensures that the proper URL is set. Each website could have multiple domains.
See the Site, Store, and View Scope topic for more information about scopes in Adobe Commerce.
Set Enable Checkout Tracking to Yes
.
Disabling this option will affect reporting because Adobe Commerce is not allowed to share checkout tracking information with Bolt.
Select the Next Stage After Login option to change the navigation flow after the customer has logged in. By default it is set to the Payments page.
Define if Quick Checkout allows for the automatic login during checkout. By default it is enabled to automatically login to the Bolt network.
See Bolt’s Enable Automatic Login documentation for more information.
The onboarding process is designed to guide you through the required steps for setting up and enabling the Express Checkout functionality.
Contact Adobe Commerce Support through the Adobe Commerce Help Center for any assistance.
See the test and validate topic for more information.