New Dashboard Notice
Bolt has launched a new Merchant Dashboard experience. See this corresponding page for help documentation that reflects the Legacy Dashboard.
Please note that Legacy Dashboard documentation may no longer have up to date information on our newest features and releases.
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.
- Log into Adobe Commerce admin. This is typically located at
yourstoreurl.com/admin
.
- Navigate to Stores > Configuration > Sales > Checkout.
- Scroll to Quick Checkout.
- In a separate browser tab, create a Production or Sandbox merchant account with Bolt. Provide all of the following required information:
- Set up your chosen payment processor from the Bolt Merchant Dashboard:
To connect Adyen, retrieve these credentials from your existing Adyen account.
Credential |
Description |
Example |
Where to Find It |
Adyen Merchant Account Code |
A unique identifier for your Adyen account. |
129413 |
From your Adyen account: - Go to Settings.
- Find Merchant accounts.
- Find your account code, then copy the string for use in a later step.
|
Adyen Webservice API Key |
A string created specifically for use with Bolt that allows connection between the Bolt and Adyen APIs. |
324f...3ni9 |
From your Adyen account:
- Go to Developers, then API credentials, and select the web service credential that has a description of
Bolt . If you don’t already have an API credential for Bolt, you should create a Web Service User credential and add Bolt in the description. - When you click the credential, you’ll see the Configure API Credential Page.
- Go to the Authentication section, under Server Settings, and select Generate New API Key.
- Select Save changes at the bottom of the page, then copy the string for use in a later step.
|
Adyen HMAC Key |
The hash-based message authentication code (HMAC) is a unique secret key that generated in your Adyen account. |
44782DEF547...6BA056 |
You can generate and retrieve an HMAC signature by following the instructions listed in Adyen’s Verify HMAC Signatures article. |
Adyen Username |
The username for the Adyen API credential you use for reporting. |
Report@Company.BoltFinancial |
From your Adyen account:
- Go to Developers, then API credentials, and select the reporting credential. If you don’t already have one, you should create a Reporting credential.
- When you click the credential, you’ll see General Settings.
- Copy the value in Username for use in a later step.
|
Adyen Password |
The password for the Adyen API credential you use for reporting. |
56f3...99h6 |
From your Adyen account:
- Go to Developers, then API credentials, and select the reporting credential. If you don’t already have one, you should create a Reporting credential.
- When you click the credential, you’ll see General Settings.
- Go to the Authentication section and click Basic Auth.
- Click Generate password.
- Click Save changes at the bottom of the page, then copy the password for use in a later step.
|
Live URL Prefix |
A unique snippet of an endpoint URL that allows Bolt to identify your Adyen account. Note: This value is only available in your live environment. |
- Example endpoint:
https://e73e0f17d7bd00d7-BoltFinancial-checkout-live.adyenpayments.com/checkout/v1/payments - Example Live URL Prefix:
e73e0f17d7bd00d7-BoltFinancial
|
From your Adyen account: - Go to Developers.
- Go to API URLs and copy the Live URL prefix from one of the endpoints.
|
To connect Authorize.net, enter the following information from your existing account:
Credential |
Description |
Example |
Where to Find It |
Authorize.net API Login ID |
A complex value that identifies your account to the payment gateway when submitting transaction requests from the website. |
Ab&1R7ghT |
- Log into the Merchant Interface.
- Navigate to Account > Settings > API Credentials & Keys.
- Find your API Login ID and paste it into the required Bolt Set Up field.
|
Authorize.net Transaction Key |
A randomly generated value that adds an additional layer of authentication when submitting transaction requests from your website. |
Ao73tGh6ryB358nI |
- Log into the Merchant Interface.
- Navigate to Account > Settings > API Credentials & Keys.
- Click New Transaction Key.
- Select the option that allows both keys to remain in use for up to 24 hours.
After you’ve generated a new key, you have 24 hours to update your keys across all integrations.
- Obtain the PIN from your email and enter it on the verification page.
- Copy the Transaction Key and paste it into the required Bolt Set Up field.
|
If you are using Authorize.net as an emulator for another payment processing tool and receive an authorization error for the credentials you use, please open a ticket with our Support Team.
To connect Braintree, enter the following information from your existing account:
Credential |
Description |
Example |
Where to Find It |
Braintree Merchant ID |
A 16-character string that is the unique identifier for your entire Braintree gateway account. |
7289hdsj2479herj |
In your Braintree admin dashboard: - Go to the Settings gear icon in the top-right corner, then select Business from the drop down.
- Find your Merchant ID, then copy and paste the string into the required Bolt Set Up field.
|
Braintree Public Key |
A 16-character user-specific string that acts as a public identifier. |
32y47e4h8fej38fj |
In your Braintree admin dashboard: - Go to the Settings gear icon in the top-right corner, then select API from the drop down.
- Select Keys.
- Find your Public ID under API Keys, then copy and paste the string into the required Bolt Set Up field.
|
Braintree Private Key |
A 32-character user-specific string that acts as a private identifier to operate API calls. |
83jd74bs03nf73bskf83hf8j8hskd3ff |
- In the same location in your Braintree account that you found your Public Key, find the Private Key column.
- Click View.
- Copy and paste it into the required Bolt Set Up field.
|
To connect CyberSource, enter the following information from your existing account:
Credential |
Description |
Example |
Where to Find It |
CyberSource Merchant ID |
The unique identifier for your merchant account with CyberSource. Usually the same as your CyberSource User Name. |
api_integration_tests |
Find your initial CyberSource confirmation of registration email. The Merchant ID is listed here. |
CyberSource Shared Secret Key |
Base-64 encoded secret key used as the authentication ID for REST API requests. |
0524a22e-e46a-4872-
59a79a264f03 |
Important: This page shows both the shared secret key and the shared secret. Make sure to save both values before you navigate away from this page. The shared secret is not retrievable in the future.
- Log into the Business Center and navigate to Payment Configuration > Key Management.
- Click Generate Key.
- Click Rest - Shared Secret > Generate Key.
- Copy and paste the key into the required Bolt Set Up Field.
- Optionally, click Download to save the keys information in a text file on your machine.
|
CyberSource Shared Secret |
Base-64 encoded secret used as an authentication signature for REST API requests. |
vz2Ir2ivCuOEd43YThb47
QhcfP7bqgjYSycu49lAwYW= |
You can find more information about these keys in
CyberSource's documentation.
To connect NMI, you must first generate Bolt-specific NMI API and Webhook Signing keys.
Then, enter the following credentials from your existing account into the Bolt Set Up fields:
Credential |
Description |
Example |
Where to Find It |
NMI API Key |
A 32-character api key, generated by you, specifically for use in this set up process. |
jlsdfLS3FDd3skfas2hdfZ4ds3274k8f |
Generate in your NMI account: - Go to My Settings > Security Keys > Add a New Private Key.
- Click generate a new API key.
- Copy and paste the key into the required Bolt Set Up Field.
|
Webhook Signing Key |
A webhook URL that combines the base Bolt webhook with your Bolt Merchant Public ID. This allows Bolt to coordinate chargeback handling with your payment processor. |
https://api.bolt.com/v1/webhooks/nmi/{public-id} |
Replace {public-id} with your “Merchant Public ID” (a 12-character string), found in the Developers tab in your Bolt Merchant Dashboard. If you find that you cannot access this key, please reach out to our Support team. |
To connect Stripe:
- Click Connect Stripe.
- Then, log into and verify your account credentials for your existing Stripe Account.
- Click Log In.
Do not click "Create New Account" - this may create an additional Stripe account and freeze transactions for 14 business days.
-
Obtain the following API keys by navigating to Administration > API > API Keys in the Bolt Merchant Dashboard.
-
In the Adobe Commerce browser tab, scroll to Account Credentials
-
Insert the unique API Key, Publishable Key, and Signing Secret.
-
Define your Service Settings.
-
Set Environment dropdown to match Sandbox
or Production
, depending on which onboarding flow you used.
-
Set Enable dropdown to Yes
to activate the extension.
-
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
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.