Stitch Payments with Elementor
Stitch does not ship Elementor widgets. It works when Elementor provides layout around standard WooCommerce checkout, because payment fields still render through WooCommerce gateways.
Supported setups
| Setup | Support |
|---|---|
| Elementor layout on the WooCommerce checkout page | Yes |
Page with [woocommerce_checkout] shortcode | Yes — detected automatically |
| Elementor Pro WooCommerce checkout widget | Yes — detected automatically |
| WooCommerce Cart/Checkout blocks | Yes — separate Blocks integration |
| Custom Elementor forms replacing WC payment fields | No |
Automatic detection
Checkout_Context::is_checkout_context() returns true when:
is_checkout()is true- Add-payment-method account screens
- Singular pages with
[woocommerce_checkout]in post content - Elementor documents containing
woocommerce-checkout-page,wc-checkout-page, or a shortcode widget with[woocommerce_checkout]
When detected, Stitch enqueues stitch-payments-gateway CSS and JS on that page.
Recommended setup
- Use the official WooCommerce checkout page as the checkout endpoint, even if designed in Elementor.
- Keep WooCommerce payment methods in the layout — do not replace them with custom form widgets.
- Test guest checkout (new card) and logged-in checkout (saved cards, if enabled).
- Test both classic shortcode checkout and Blocks if your store uses both.
Custom page slug
If checkout lives on a page that is not auto-detected:
add_filter( 'stitch_payments_is_checkout_context', function ( $is_context, $gateway ) {
return $is_context || is_page( 'elementor-checkout' );
}, 10, 2 );
Styling
Elementor global styles may affect checkout spacing. Target Stitch selectors such as #wc-stitch-form and .stitch-payment-header. See Styling.