Bolt has launched a new Merchant Dashboard experience. See this page for help documentation that reflects the Legacy Dashboard.

---

# Before You Start

Review the following requirements before installing Quick Checkout on your Adobe Commerce store:

Requirements	Constraints
PHP version	Depending on the Adobe Commerce instance version >=2.4.4
Composer	Depending on the Adobe Commerce instance version >=2.4.4
Magento Open Source or Adobe Commerce >=2.4.4	none

Install

Use Adobe’s official installation steps to add the Quick Checkout extension to your store.

Configure

1. Log into Adobe Commerce admin. This is typically located at yourstoreurl.com/admin.
2. Navigate to Stores > Configuration > Sales > Checkout.
3. Scroll to Quick Checkout.
4. In a separate browser tab, create a Production or Sandbox merchant account with Bolt. Provide all of the following required information:
   • First Name
   • Last Name
   • Email Address
   • Store Name
   • Website URL
   • Payment Processor
5. Set up your chosen payment processor from the Bolt Merchant Dashboard:
   • Sandbox URL
   • Production URL

6. Obtain the following API keys by navigating to Administration > API > API Keys in the Bolt Merchant Dashboard.

   • API Key: A private key used by your backend to interact with Bolt’s APIs.
   • Publishable Key: A key used by your front-end to interact with Bolt’s APIs. The publishable key is a long string of lower and upper case letters and numbers that consists of three sections.
   • Signing Secret: Used for signature verification on requests received from Bolt.

7. In the Adobe Commerce browser tab, scroll to Account Credentials

8. Insert the unique API Key, Publishable Key, and Signing Secret.

9. Define your Service Settings.

   • Title: Used to identify Bolt payment options displayed in your storefront (e.g., Credit Card powered by Bolt).
   • Payment Action: Determines whether transaction capture is automatic upon authorization (Authorize and Capture) or delayed (Authorize).
   • Debug Mode: Used to test and troubleshoot the Quick Checkout experience.

10. Set Environment dropdown to match Sandbox or Production, depending on which onboarding flow you used.

11. Set Enable dropdown to Yes to activate the extension.

12. Select the Save Config button.

Limitations

Review the following limitations of the Quick Checkout beta:

General Limitations

Limitations	Constraints
US only	This feature is only available for US merchants
USD only	USD is the only compatible currency
Amazon Pay	Quick Checkout is not compatible with Amazon Pay
PWA Studio and headless deployments	Merchants MUST use the Luma-based coupled storefront. PWA Studio and headless deployments are not supported
3D Secure	3D Secure is not supported
B2B	B2B is not supported
ISPU	In-Store Pickup (ISPU) functionality is not supported
Multishipping	Multishipping is not supported

Transaction Limitations

Review which advanced transaction actions are supported for your processor.

Advanced Transaction Actions	Bolt Payments	Stripe	Adyen	Braintree	CyberSource	NMI	Auth.net
Multi-Capture	✅	❌	✅	❌	✅	❌	✅
Multi Partial Refund	✅	✅	✅	✅	✅	✅	✅ Post Capture
Refund After Capture	✅	✅	✅	❌	✅	✅	✅
Void After Partial Capture	✅	❌	✅		✅	✅	✅
Refund After Partial Void	✅	❌	✅		❌	❌
Void After Full Capture	❌	❌	❌	❌	❌	❌	❌
L2/L3 Data Support	✅	✅	✅	✅	✅	❌	❌
Webhooks	❌	✅ Capture/Void/Refund	❌	✅ Polling for Capture/Void; delayed 1 hour

Transaction Processing Considerations

In the event a given transaction action is not supported for your processor on the previous table, you may consider these alternative solutions:

Multi-Capture

If multi-capture is not supported for your processor, it is important to understand that after the initial capture, the authorization can no longer be used for additional captures. The most straightforward solution is using the Authorize and Capture Payment Action setting, which will ensure that only one capture is being made against the order. In case this is not an acceptable solution and you must set your Payment Action to Authorize, we recommend one of the following:

• Shipping the whole order together and then capturing the full amount
• Creating a full invoice before the first shipment happens to avoid un-invoiced shipped items

Void After Partial Capture

• If multi-capture is not supported for your processor, you can void the transaction before the order is invoiced
• If multi-capture is supported, you can cancel an order and Adobe will void the rest of the authorization as well

Refund After Capture

If you need access to initiating refunds during the majority of a transactions lifecycle, we recommend using the Payment Action setting of Authorize and Capture. In the event a refund fails due to a capture still being unconfirmed, the platform notifies the user that it’s not possible to perform the refund yet. Make sure to inform your customer service representatives that they may encounter this and to wait until the transaction’s status updates before re-initiating the refund.

Orders processed via Authorize.net can be voided when in the captured-but-not-settled state.

Refund After Partial Void

Adobe Commerce does not allow partial void.