Hyvä Checkout in 2026: is it worth it?

Checkout is where Magento stores lose the most revenue for the least visible reason. Hyvä Checkout is the most common replacement for the default Luma checkout on Hyvä stores, and since the Hyvä Theme became free in late 2025, it is now the main paid piece of a Hyvä build. This article covers what Hyvä Checkout costs in 2026, how it compares with Luma and other one-step checkouts, and when it pays for itself.

What is Hyvä Checkout?

Hyvä Checkout is a checkout module for Magento 2, developed and supported by Hyvä Themes. It replaces Magento’s Knockout.js-based checkout with a server-rendered checkout built on:

• Magewire, a port of Laravel Livewire for Magento. Components are written in PHP using the classes, dependency injection and layout XML that Magento developers already know.
• Alpine.js for small interactive behavior in the browser.
• Tailwind CSS for styling, shared with the Hyvä Theme.

Do not confuse it with the React Checkout. Hyvä’s docs explain that the open-source React Checkout was originally called “Hyvä Checkout” but is a separate, community-maintained project with no shared code. If a module or blog post mentions React components, it refers to the React Checkout.

Hyvä Checkout pricing and licensing in 2026

According to hyva.io, Hyvä Checkout is sold as follows:

Key license terms:

• One license covers one Magento installation with unlimited store views and domains, as long as they belong to the same business entity.
• Code is delivered through Private Packagist, with support via the Hyvä Slack community and customer portal.
• There is no free trial. Hyvä offers a 30-day money-back policy, and agencies can buy a license for testing and transfer it to a client.
• Hyvä Checkout is also included in the Hyvä Commerce bundle.

For context, the Hyvä Theme itself was relicensed under OSL3 and AFL3 and became free from November 10, 2025. Checkout, Enterprise and Commerce remain commercial products.

Key features

• One-page or multi-step layouts. You choose the layout, and you can build your own checkout variants that appear in the admin selector.
• Separate mobile checkout. An optional mobile setting serves a different checkout when the user agent matches a mobile device, for example multi-step on phones and one-page on desktop.
• Store-view scoping. Hyvä Checkout is opt-in per store view. The default setting is “Magento Luma (original)”, so you can roll it out gradually.
• PHP-first customization. Most changes happen in PHP and layout XML (hyva-checkout.xml), with little custom JavaScript.
• A/B testing. Hyvä’s docs point to an open-source module by Elgentos (elgentos/magento2-hyva-checkout-ab-test) for comparing Hyvä Checkout against your Luma checkout.

On performance, Hyvä claims “13 times faster load time on mobile devices compared to standard Magento checkout.” That is a vendor figure. Measure it on your own store before and after.

Hyvä Checkout vs Luma checkout vs other one-step checkouts

Two points stand out. First, Luma-based one-step checkout extensions still carry Luma’s JavaScript weight, so they change the layout more than the performance. Second, if your storefront runs on Hyvä, using a Luma checkout requires the hyva-themes/magento2-luma-checkout fallback module, which loads a Luma theme just for checkout. Hyvä supports this for migrations and compatibility, but recommends Hyvä Checkout for the best experience.

Can you use Hyvä Checkout on a Luma store?

Yes. Hyvä’s docs state that Hyvä Checkout depends on the Hyvä Theme, but the rest of your store does not have to run on it. Using the theme fallback module, you configure the store to load the Hyvä default theme only for requests containing hyva_checkout/index, while every other page stays on Luma. This is a practical first step for Luma stores that want a faster checkout before committing to a full Hyvä frontend.

Payment provider compatibility

Because Hyvä Checkout is built from scratch, standard Magento payment and shipping modules usually do not work out of the box. Each one needs a Hyvä Checkout integration.

Hyvä lists support for popular providers including PayPal, Mollie, Stripe, Adyen, Braintree and Payplug, and tracks third-party integrations on a public Checkout Integration Tracker. Before you buy:

1. List every payment method, shipping carrier, address validation service and checkout-related extension you use.
2. Check each one against the Hyvä integration tracker and the vendor’s own documentation.
3. Budget development time for anything missing. Magewire integrations are usually simpler to write than Knockout components, but they still need building and testing.

Also read the compatibility note on hyva.io: Hyvä Checkout “does not support 100% of B2B and Adobe Commerce specific features yet.” If you rely on B2B quotes, company accounts or other Adobe Commerce checkout features, check the Hyvä Checkout feature matrix first.

When is Hyvä Checkout worth it?

It is usually a good investment when:

• You already run the Hyvä Theme, or plan to. The checkout shares its stack and avoids loading Luma assets just for checkout.
• Mobile traffic is a large share of your sessions and your current checkout feels slow on phones.
• Your payment and shipping providers have integrations, or you have developers to build them.
• Your team finds Knockout.js checkout customizations slow and fragile, and prefers working in PHP.

It is harder to justify when:

• You depend on Adobe Commerce B2B checkout features that are not covered yet.
• A key payment method has no integration and building one is not in the budget.
• Order volume is so low that a checkout conversion improvement would not cover the license and integration cost.

A simple way to estimate: take your monthly checkout sessions, your current checkout completion rate and your average order value, and calculate how much one extra completed checkout per 100 sessions would be worth. Compare that with the €1,000 license plus your integration and testing time. Then confirm the result with an A/B test instead of relying on vendor numbers.

For Magento checkout optimization, also fix the basics, whatever checkout you use: guest checkout, fewer form fields, address autocomplete, clear shipping costs early, and fast payment methods such as wallets.

Our Hyvä theme development team builds and integrates Hyvä Checkout, including custom payment and shipping integrations.

Frequently asked questions

Is Hyvä Checkout free now that the Hyvä Theme is free?

No. Only the Hyvä Theme became open source in November 2025. Hyvä Checkout is a commercial product at €1,000 per installation, plus support and updates after the first year.

Does Hyvä Checkout require the Hyvä Theme?

The checkout depends on the Hyvä Theme, but your storefront can stay on Luma. The theme fallback module loads the Hyvä default theme only for the checkout pages.

Which payment providers work with Hyvä Checkout?

Hyvä lists PayPal, Mollie, Stripe, Adyen, Braintree and Payplug among supported providers. Check the integration tracker for your exact module and version.

Can I test Hyvä Checkout before switching fully?

Yes. It is enabled per store view, and Hyvä’s docs reference an open-source A/B testing module that splits traffic between Hyvä Checkout and your existing checkout. Note that you need enough traffic for statistically meaningful results.

Sources

• Hyvä: Hyvä Checkout product and pricing page
• Hyvä Docs: Hyvä Checkout
• Hyvä Docs: Does Hyvä Checkout require a Hyvä Theme?
• Hyvä Docs: Luma Checkout with Hyvä Themes
• Hyvä Docs: Hyvä Checkout vs React Checkout
• Hyvä: Hyvä Theme is open source and free
• Adobe: Customize checkout