Summary
Key takeaways
- A green confirmation page does not prove that checkout works. Check separately that the correct payment was authorized, that Magento created exactly one order and that fulfillment received it once.
- Hyvä’s November 17 release notes list version 3.0.2 on the current Checkout 3.x line and 1.3.16 on the previous 1.x line. Each line has its own patches.
- Checkout 3.x runs on Magewire 3 and requires PHP 8.2 or newer. A Magewire 1 compatibility module helps well-behaved 1.x components and extensions keep working during the transition.
- Some checkout methods and cart totals behavior changed between versions. An extension can render correctly in the browser and still change a quote total that an external API consumer relies on.
- Elogic Commerce recommends approving the upgrade with evidence from four places: the browser, the payment provider, Magento and the system that fulfills the order.
- A stable correlation key should connect the checkout attempt, payment reference, Magento order ID and export acknowledgment in the staging report.
- Test both completion and recovery paths, including 3D Secure, declines and retries, separate wallet runs, address and delivery changes, delayed payment notifications, and refunds.
- Wallet eligibility belongs in the evidence. A missing Apple Pay or Google Pay button in a supported market is a different problem from a hidden button on an ineligible browser.
- Behavior that customers take for granted can take a lot of effort. At Ormoda, module customization took about 200 of roughly 500 development hours, or about 40% of the Hyvä redesign and checkout rebuild.
- Pause the release on hard failures such as a charge with no order, a duplicate charge or ERP export, the wrong currency, or a missing payment method in a supported market.
When this applies
This guidance is for Magento Open Source and Adobe Commerce stores that already use Hyvä Checkout 1.x and plan to move to the 3.x line, and for teams starting a new Hyvä Checkout project. It is most relevant when checkout depends on several payment gateways, wallets, 3D Secure, local shipping or pickup options, fraud tools, address lookup, custom form steps or an ERP or OMS export, especially when some of those integrations are custom or maintained by third parties. Adobe Commerce stores using Hyvä Enterprise compatibility and B2B checkout add-ons can use the same approach to test trade accounts, approvals and payment terms. QA, payments, operations and integration owners can use the version manifest, the scenario matrix and the hard failure criteria to make a clear release decision.
When this does not apply
This test plan matters less for stores that do not use Hyvä Checkout, for example those keeping Luma checkout through theme fallback or using a supported third-party checkout. A new store with a single standard payment method and no custom delivery logic or downstream export will need a much smaller test set. The upgrade should also wait if the platform, PHP runtime or key integrations do not yet meet Checkout 3.x requirements, or if a payment, shipping or tax module has no supported version. In that case, give each unresolved dependency an owner and a test date instead of releasing early. Project figures such as the Ormoda hours describe one engagement and are not an estimate for other stores.
Checklist
- Record the Magento, PHP, theme module, Tailwind, checkout build, Magewire and compatibility module versions, plus any Enterprise or B2B checkout add-ons.
- List every gateway, tax, shipping, pickup, fraud, address lookup, custom form and order export integration with its version and maintainer.
- Match each payment integration to the exact module and configuration your store uses, not just the gateway brand.
- Pull a representative period of checkout attempts and successful orders by device, method, market and shopper type, including low-volume methods the business must keep.
- Read the 3.x upgrade guide with the owners of payments, shipping, fraud and tax.
- Define a correlation key that links each test attempt to its payment reference, Magento order and export acknowledgment.
- Prepare fixed test fixtures with a known product, address and expected amount for a guest order, a signed-in order and a trade order where B2B applies.
- Complete a 3D Secure challenge and confirm one authorized amount, one Magento order and one export.
- Trigger a decline, retry on the same quote and confirm only one successful charge and one accepted order remain.
- Test Apple Pay and Google Pay separately on eligible devices, including cancelling and returning to checkout, and record the eligibility conditions.
- Change the country or postal code and switch between delivery and pickup, then verify the available methods and final totals.
- Test the billing step after an address edit as well as on first render.
- Simulate delayed or repeated payment notifications and confirm payment, order and export end up as one correct result.
- Run a cancellation or refund through the normal operations path and confirm Magento and the provider agree on amount and reference.
- Agree on hard stop criteria and a plan for in-flight orders, then release to one store view first and prove the same transaction in a neighboring view.
Common pitfalls
- Treating a successful confirmation page as proof that payment, order creation and export all worked.
- Upgrading without a full version manifest, which makes it hard to trace what changed when something breaks.
- Assuming the Magewire 1 compatibility module will cover every custom component or extension.
- Checking only what the shopper sees and missing changes to quote totals used by external systems.
- Matching a payment integration by gateway name only, when the brand may have several modules or flows.
- Testing only happy paths and skipping declines, retries, wallet cancellations and delayed notifications.
- Running wallet tests only on unsupported browsers or devices and not recording eligibility conditions.
- Testing the billing step only on first load and missing failures after an address change.
- Underestimating the effort for shipping estimators and other custom modules customers rely on.
- Rolling back the storefront without reconciling payments and orders created during the release window.
A wallet button is the easy part of a checkout test. The commercially important question comes a few seconds later. Did the right payment authorize, did Magento create one order, and did fulfillment receive it once? For stores moving to Hyvä Checkout 3.x, those are separate checks. A green confirmation page can coexist with a failed export or a payment the shopper is asked to retry.
Hyvä’s November 17 release notes list 3.0.2 on its current Checkout 3.x line and 1.3.16 on its previous 1.x line. Checkout 3.x runs on Magewire 3. The release is a good moment to inventory the payment and delivery paths that depend on code your store owns. Elogic Commerce recommends approving the upgrade with transaction evidence from the browser, payment provider, Magento and the system that fulfills the order. Hyvä Checkout changelog · Hyvä release lines
At Ormoda, the Belgian watch and jewelry retailer, Elogic Commerce rebuilt checkout as part of an earlier move from Luma to Hyvä. The scope included Stripe, Apple Pay and Google Pay, plus location-based shipping. That experience is a practical starting point for choosing what to exercise on staging. Each method needs a completed order and a recovery path appropriate to that provider. Ormoda case study
Establish which code the upgrade will move
Hyvä Checkout 3.x uses Magewire 3 and requires PHP 8.2 or newer. The 1.x line uses Magewire 1. Hyvä includes a Magewire 1 compatibility module with Checkout 3.x so well-behaved 1.x components and extensions can work during the transition. Record the exact version of the theme module, Tailwind CSS, Commerce platform and PHP runtime. For an Adobe Commerce store using Hyvä Enterprise compatibility, check the installed Enterprise Checkout module and the B2B Checkout add-on where applicable. Hyvä requirements · Hyvä compatibility module
Read the release guide with the people who own your shipping, fraud, payments and tax integrations. Some checkout methods and cart totals behavior changed between versions. An extension can appear to render in the browser and still affect a quote total that an external API consumer uses. Capture an export or API response alongside the expected customer experience. On Tap’s upgrade analysis notes that custom components and external totals consumers deserve their own staging checks. Upgrading to Hyvä Checkout 3.0 · On Tap upgrade analysis
| Record | What to capture before changing checkout |
|---|---|
| Version manifest | Magento and PHP versions, theme module, Tailwind generation, checkout build, Magewire, the backward compatibility module and Enterprise extras. |
| Integration versions | Gateway, tax, shipped and pickup methods, fraud tools, address lookup, custom form steps and the order export. Record the module maintainer where the integration is externally maintained. |
| Traffic and revenue | A representative period of attempts and successful orders by device, method, market and shopper type. Include each low-volume method the business must keep. |
| Acceptance evidence | Checkout test ID, test environment, market, amount and currency, payment reference, Magento order ID, export acknowledgment and result. |
In its payment directory, Hyvä identifies tracked integrations and shows who maintains them. A gateway brand can have multiple integration versions or flows. Match the entry to the actual module and configuration, and run the provider’s test environment through a successful payment, a decline and a return from any required authentication. Hyvä payment integrations · Stripe testing documentation
Test completion and recovery with the same order
For each row, start with a known product, address and expected amount. Keep one guest order and one signed-in order as a baseline. Add a trade account when B2B approval or payment terms are part of the installed setup. Record the outcome in each system. Use the same fixture on both versions where the merchant is comparing an upgrade with the current checkout.
| Scenario | Exercise in the provider sandbox | Evidence that clears the test |
|---|---|---|
| Card authentication | Complete a required 3D Secure challenge and return to checkout. | Authorized or captured amount fits the store’s policy and matches one Magento order plus one export. |
| Decline and retry | Trigger a test decline, then pay on the same quote using a supported test method. | The shopper can recover. Exactly one successful charge and one accepted order remain. |
| Apple Pay and Google Pay | Use eligible devices and browsers. Run each wallet separately and try a cancel and return. | Returning from the wallet keeps the expected currency, shipping, tax and order state. |
| Address and delivery changes | Change country or postal code, and switch from delivery to pickup where offered. | The available methods and final totals reflect the new address and the chosen service. |
| Delayed payment response | Use the provider’s test tooling or your staging harness to exercise a delayed or repeated notification. | Payment, order and export converge to a single correct result. |
| After the purchase | Confirm cancellation or refund in the provider sandbox using the normal operations path. | Magento and the provider agree on the amount and reference that operations should reconcile. |
Eligibility belongs in the evidence. Wallet buttons appear only under the conditions supported by the payment integration, provider and device. Write down those conditions for each scenario. A hidden button on an ineligible browser and a hidden button in the supported market have different implications.
Public developer reports can help QA choose which layer to watch. In one LinkedIn post, Adam Varga described a billing component that failed to load after a theme-related routing interaction. The report concerns his implementation. It is a practical reason to test the billing step after an address edit as well as on the first render. Adam Varga’s implementation note
Give the slow paths the same attention as the happy path
Elogic Commerce put roughly 200 of 500 development hours at Ormoda into module customization across its Hyvä rebuild. The work included adapting a shipping estimator and a product brand module. That is about 40% of the total project development hours. It shows how much effort can sit in behaviors customers take for granted. Treat it as an example of project scope when planning your own checkout and shipping audit. Ormoda project delivery
Use the test log to make a release decision. Hard failures include a successful charge with an absent order, a duplicate charge or ERP export, the wrong currency, and a missing method that customers in a supported market rely on. These merit a pause while the team reconciles open transactions. Agree on what to do with in-flight orders before changing checkout configuration. A restored storefront still needs operations to account for payments and orders created during the release window.
Hyvä Checkout can be scoped to specific store views, which gives eligible installations a way to start with one storefront. The interested merchant can use staging to prove the same transaction in both the test view and a neighboring view. The Elogic Commerce approach makes one completed payment and one downstream acknowledgment the unit of acceptance. Hyvä Checkout documentation · Elogic Commerce Hyvä Themes development
When should a Magento store move to Hyvä Checkout 3
Use 3.x for a new Hyvä Checkout project whose platform, runtime and integrations meet the current requirements. For an existing store, move when the modules and merchant-specific buying routes have passed the agreed staging matrix. Give an unresolved dependency an owner and a test date. Hyvä documents both release lines so the team can select the current patch for the line it runs. Store owners planning linked platform work can review their Magento maintenance scope.