1. Set Up Express Checkout

Express Checkout is currently only available for US-based merchants enrolled in Adobe’s Early Adopter Program (EAP) and is not yet available to all merchants.

Before You Start

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

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

Install

Use Adobe’s official installation steps to add the Express 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 Express 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:

Adyen



Authorize.net



Braintree



CyberSource



NMI



Stripe


  1. Obtain the following API keys by navigating to Developers > 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.
  2. In the Adobe Commerce browser tab, scroll to Account Credentials

  3. Insert the unique API key and Publishable Key.

  4. 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 Express Checkout experience.
  5. Set Environment dropdown to match Sandbox or Production, depending on which onboarding flow you used.

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

  7. Select the Save Config button.

Limitations

Review the following limitations of the Express 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 Amazon Pay is not compatible with Adobe Commerce versions >=2.4.1-p1
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 Secure 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 Vantiv 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.

Refund After Partial Void

Adobe Commerce does not allow partial void.

📖On This Page