Find the module configuration options
To configure the Stripe Connector for Adobe Commerce navigate to the configuration section for it (Stores > Configuration > Sales > Payment Methods):
Stripe appears on your checkout page only after you configure your API keys. If you don’t have a Stripe account yet, register online.
- Mode: We recommend that you start by testing the integration in test mode. Switch to live mode when you’re ready to accept live transactions. You can learn more about testing payments on Stripe.
- API keys: Fill in the test and live keys that Stripe provides to you in the Developers section of your Dashboard.
- Hold Elevated Risk Orders: If Stripe Radar marks a payment with an
Elevated Riskstatus, the module places the order
On Holduntil you review the payment. See the section Enabling fraud prevention features with Stripe Radar for additional details.
- Receipt Emails: When enabled, Stripe sends a payment receipt email to the customer after the payment succeeds. You can customize the styles and brand of emails from your Stripe account settings.
- Enabled: Enable or disable Stripe as an available payment method for the standard checkout page, for the multi-shipping checkout page, and for the admin area.
- Payment flow: Select your preferred payment flow for the standard checkout page. With the embedded payment flow, we embed an iframe-based Payment Element directly in the checkout page. With the redirect payment flow, we redirect customers to Stripe Checkout to complete their payment.
- Title: The label you want to display to the customer on the checkout page.
- Payment methods: This link opens the payment methods settings in your Stripe Dashboard. From there, you can individually enable or disable the payment methods you want to offer to your customers. These settings impact both the Stripe Checkout and Payment Element payment flows.
- Payment Action: Select Authorize and Capture if you want to charge customer cards immediately after a purchase. This is the default option and doesn’t require you to do anything after the customer has placed the order. If you prefer to finalize the payment later, you can choose Authorize Only, which authorizes and holds the order amount on the customer’s card so you can capture the amount later by issuing an invoice. You can read more about capturing payments using invoices with this module.
- Expired authorizations: For card payments that you don’t capture immediately, you must do so within seven days. Any attempt to capture the amount after that returns an error. By enabling this option, the module attempts to recreate the original payment with the original card used for that order. The module saves cards automatically in Authorize Only mode and the customer can’t delete them from their account section until you either invoice or cancel the order.
- Automatic Invoicing: The Authorize Only option creates a new invoice with a Pending status on checkout. After capturing the charge, the invoice status transitions to Paid. This option is useful when Payment Action is set to Authorize Only: no invoice results from completing the checkout flow. If enabled, the module automatically generates an invoice on checkout completion so you can email it to a customer before charging them.
- Save customer payment method Enable this option to allow customers to save their last used payment method in the Stripe vault and reuse it later for quicker checkout.
- Card Icons: Display card icons based on the card brands your Stripe account supports.
- Optional Statement Descriptor: This is an optional short description for the source of the payment, shown in the customer’s bank statements. If left empty, the default descriptor configured from your Stripe Dashboard applies. This option isn’t available for Multibanco, SEPA Direct Debit, or Sofort.
- Sort Order: If you’ve enabled multiple payment methods, this setting determines the order of payment methods presented on the checkout page.
If your customer is using a compatible device, they can use Apple Pay or Google Pay during the checkout process. Use the dedicated configuration section in the Adobe Commerce admin panel to set your preferences:
- Enabled: Enable or disable the wallet button as an available payment method for the locations selected. You can enable the wallet button even if you disable regular payments.
- Locations: Choose where to display the wallet button. If you’re using the embedded payment flow, we recommend against selecting the checkout page, because the Payment Element already displays its own version of the wallet button. If you still choose to enable it on the checkout page, the module hides the wallet button in the Payment Element to avoid displaying it twice.
- Wallet buttons: This link opens the payment methods settings in your Stripe Dashboard. From there, you can individually enable or disable Google Pay or Apple Pay on your store.
- Button Type: Choose between three types of payment buttons to display (Default, Buy, and Donate).
- Button Theme: Choose between three types of button themes (Dark, Light, and Light-Outline).
- Button Height: Adjust the button height to match your theme’s Add to Cart and Proceed to Checkout buttons.
- Seller Name: The name of your business that appears in the modal at the time of the payment.
See the troubleshooting section if the button doesn’t appear after enabling it.
Stripe uses webhooks to notify your application when an event happens in your account. Webhooks are particularly useful for updating Magento orders when a customer’s bank confirms or declines a payment, or when collecting subscription payments. These events allow the module to mark Magento orders as ready for fulfilment, record refunds against them, or add comments about payment failure reasons.
Starting from version 3 of the module, you no longer need to manually configure webhooks. The module checks and potentially configures webhooks automatically in the following cases:
- When you install or upgrade the module and trigger the
- Every time you update the API keys in the Magento admin.
- Every time you change the URL of a store in the Magento admin.
- When the module detects a change in the database during one of the hourly automated checks. This prevents webhooks from being broken due to a manual change to the database, a migration from a different server, or a backup restoration.
When updating webhooks, the module creates a single webhook endpoint per Stripe account. For example, if you have five store views, four are using a Stripe account and the last one is using a different Stripe account, the module creates two webhook endpoints.
This also applies if you use different domain names for your store views. In this case, the module uses one of the store view domains and not your base URL. This is to prevent issues with base URLs often being behind a firewall for security reasons.
The module uses webhook signatures to verify that the events were sent by Stripe, not by a third party. You can disable this protection only when your Magento instance is using developer mode.