As of 4 September 2026, Hyvä’s public integration tracker showed its Amazon Pay integration for Hyvä Checkout as a work in progress, with a usable version available from the development branch. Hyvä noted that the integration might require fine-tuning for individual site requirements.
Separately, Amazon released version 5.18.5 of its official Magento 2 Amazon Pay extension on 6 August 2026. The release added PHP 8.5 compatibility and addressed a checkout JavaScript error and compatibility with newer Symfony versions.
For Magento and Adobe Commerce merchants considering Hyvä Checkout, the practical point is not that Amazon Pay support had become universally production-ready. Instead, the integration had progressed far enough to be evaluated, while merchants still needed to check its documented feature coverage against their own requirements.
Why Amazon Pay matters for checkout migration decisions
For merchants with meaningful Amazon Pay usage, payment-method compatibility can be an important part of a checkout migration decision.
Amazon Pay allows customers to use payment and, where applicable, address information associated with their Amazon account. That can reduce the amount of information they need to enter manually during checkout.
The relevant question for merchants evaluating Hyvä Checkout is therefore whether the Amazon Pay functionality they rely on is supported in their specific implementation. This should be assessed alongside other checkout requirements rather than assuming that the existence of an integration means every Amazon Pay feature is covered.
What the Hyvä Checkout integration covered
As recorded in Hyvä’s Amazon Pay checkout integration tracker around the time of publication, a substantial part of the integration had already been implemented.
Checked items included:
-
Amazon Pay credentials and configuration
-
Multi-currency functionality
-
Amazon Sign-in during checkout, listed as partial support
-
Payment functionality
-
Authorisation mode
-
Button language and colour configuration
-
The Amazon Pay button in the mini-cart
-
Logging and a range of checkout and return URL options
However, the tracker still described the integration as a work in progress and stated that the usable version was available from the development branch.
Several listed capabilities remained incomplete, including the Amazon Pay button on product pages, Amazon Pay as a payment option in the final checkout stage, some sales options and shipping restrictions.
That distinction matters. Merchants should not interpret the availability of the integration as confirmation that every storefront and checkout use case is covered.
There is also a separate Hyvä Theme Amazon Pay compatibility module, with the package name hyva-themes/magento2-amazon-pay. Its tracker covers storefront compatibility requirements including Amazon Pay buttons in areas such as the cart, mini-cart and product pages, as well as optional Amazon Sign-in functionality.
This is separate from the Hyvä Checkout integration and should be assessed according to the storefront and checkout setup a merchant is using.
Amazon Pay 5.18.5 and extension compatibility
Amazon Pay 5.18.5 was released on 6 August 2026 as a stable build of Amazon’s official Magento extension.
According to its Adobe Commerce Marketplace release notes, the release:
-
added compatibility with PHP 8.5
-
fixed the "
$elem.uniqueId is not a function" JavaScript error on checkout -
fixed compatibility with newer Symfony versions
The extension’s declared compatibility and dependencies should still be checked against the merchant’s Magento or Adobe Commerce environment before upgrading.
For merchants using a Hyvä compatibility layer, the underlying Amazon extension and the Hyvä integration should also be tested together rather than treating compatibility of either component in isolation as sufficient.
The broader pattern: payment method coverage matters
Amazon Pay is one of many payment integrations merchants need to consider when evaluating Hyvä Checkout.
Hyvä maintains a payment integrations directory covering integrations maintained by the Hyvä team, payment service providers and community contributors.
Hyvä also uses its integration tracker to identify who is responsible for implementation and first-line support for individual integrations.
This makes payment compatibility a requirements exercise rather than a simple platform-level yes-or-no question.
Before migrating, merchants should map the payment methods and related features they currently depend on, then confirm the status, maintainer and supported functionality of each relevant Hyvä Checkout integration.
Timing matters ahead of peak season
For merchants considering checkout changes ahead of the Golden Quarter, the October-to-December peak trading period, implementation timing matters.
A checkout migration involves more than installing a payment compatibility module. Payment flows, customer states, shipping rules, refunds, authorisation and capture behaviour, localisation and third-party extensions can all affect the final implementation.
On Tap recommends allowing enough time for integration testing, regression testing and monitoring before releasing checkout changes close to peak trading periods.
For merchants that require Amazon Pay, the progress of the Hyvä integration was useful, but its work-in-progress status meant it still needed to be validated against the merchant’s actual checkout requirements before deployment.
What merchants should do
-
If you are already on Hyvä Checkout: On Tap recommends reviewing the current Amazon Pay integration tracker before adopting or updating the integration. Test the Amazon Pay flows your store depends on in a staging environment rather than assuming every feature of Amazon’s standard Magento extension is supported.
-
If you are evaluating Hyvä Checkout: Include Amazon Pay in your payment-method compatibility assessment. Check not only whether an integration exists, but also its status, documented feature coverage, maintainer and any site-specific work required.
-
If you use Hyvä Themes without Hyvä Checkout: Review the separate Hyvä Theme Amazon Pay compatibility module and confirm the storefront functionality your implementation requires.
-
If you are updating Amazon’s Magento extension: Review the Amazon Pay 5.18.5 release information, check its declared Magento and PHP dependencies against your environment, and test the update alongside any Hyvä compatibility modules you use.
The bigger picture
The status of Amazon Pay illustrates why payment integrations need to be assessed individually when planning a Hyvä Checkout migration.
An available integration can represent meaningful progress without necessarily meaning that every merchant requirement is covered or that the module can be deployed unchanged in every production environment.
The relevant question is whether Hyvä Checkout supports the payment methods, functionality and customisations required by your store at the point you plan to migrate.
For Amazon Pay, merchants should use Hyvä’s integration tracker to check the latest documented status and validate that functionality against their own checkout requirements before making a deployment decision.
About On Tap
On Tap is a growth-focused eCommerce consultancy and Hyvä partner, specialising in Magento and Adobe Commerce implementations for mid-market and enterprise merchants.
From Hyvä Checkout migration planning and payment-method compatibility audits to peak-season readiness and ongoing technical maintenance, On Tap helps merchants make informed checkout decisions based on their technical and commercial requirements.
If you want help evaluating your Hyvä Checkout migration path, get in touch.


