Adding Buy Now Pay Later to a Magento or Adobe Commerce store on Hyva means wiring two separate layers: the payment method inside checkout and the on-site messaging that promotes financing on product and cart pages. Both install as Composer modules, and the messaging layer is where most Hyva stores quietly give back their Core Web Vitals gains.
Why BNPL earns its place on a Magento storefront
Buy Now Pay Later has moved from a novelty to a checkout expectation, especially for higher ticket carts. When a shopper can split a $600 order into four payments or finance a $2,000 purchase over 12 months, the price objection at the moment of decision softens. Merchants who add BNPL typically report higher average order value and improved conversion on considered purchases, because the payment barrier shrinks even when the shopper pays in full anyway.
The cost is real and worth stating plainly. BNPL settles like a payment method, and the provider takes a merchant fee that is higher than card processing. Standard card rates sit around 2 to 3 percent per transaction. BNPL fees run higher, and they vary by provider and risk profile. You are paying for conversion lift and guaranteed settlement (the provider pays you up front and carries the repayment risk), so the decision is a margin calculation, not a technical one. Run the math on your real AOV before you commit.
BNPL is available across every major platform, which is why it rarely decides a replatform on its own. It runs on Shopify, Shopware, and BigCommerce through their own app ecosystems, and on Magento and Adobe Commerce through Composer modules. The mechanics below are specific to Magento on a Hyva frontend, where the frontend framework changes how the promotional scripts behave.
The two integration layers most guides collapse into one
Almost every BNPL walkthrough treats the integration as a single task. It is two, and confusing them is the root of most botched rollouts.
Layer one is the checkout payment method. This is the provider appearing as a selectable option at the payment step, capturing the order, redirecting or opening a hosted flow for approval, and returning an authorization. It is transactional, it lives in checkout, and it is governed by the same payment integration API as any other method.
Layer two is on-site messaging. This is the “4 payments of $150” or “as low as $52/mo with Affirm” text that appears on product detail pages, in the cart, and sometimes on category and landing pages. Klarna calls its version on-site messaging, and it supports payment messaging, banners, top strips, and footer placements. It is a marketing widget rendered by a third-party JavaScript library that reads the price on the page and calls the provider to render an accurate installment estimate. It has nothing to do with checkout capture.
You can ship layer one without layer two, but you lose most of the conversion benefit, because shoppers decide whether a purchase is affordable long before they reach checkout. You should never ship layer two without layer one, because promising financing you cannot process is a fast way to lose trust at the payment step.
Affirm, Klarna, and Afterpay compared for a US merchant
The three providers overlap but serve different cart profiles. Affirm leans into longer-term, higher-ticket financing. Klarna and Afterpay lean into the shorter “pay in four” model that suits mid-priced DTC carts. The table below summarizes what actually differs for a US store.
| Factor | Affirm | Klarna | Afterpay |
|---|---|---|---|
| Primary model | Pay in 4 plus longer monthly financing (3 to 60 months) | Pay in 4 plus financing and pay-later | Pay in 4, plus longer monthly on eligible carts |
| Best fit cart | Higher ticket, considered purchases | Mid to high AOV DTC | Lower to mid AOV DTC and fashion |
| On-site messaging | Promotional messaging with prequalification enabled on product pages by default | On-site messaging: payment messaging, banners, top strips, footer | Placement widgets on product and cart |
| Settlement to merchant | Up front, provider carries risk | Up front, provider carries risk | Up front, provider carries risk |
| Magento module | Composer module, Hyva Checkout compatibility available | Composer module, CSP compatible in Hyva Checkout | Available via Scalapay path and provider modules |
Two practical notes. First, Affirm promotional messaging on product pages ships with prequalification on by default, which lets a shopper see their real estimated rate; you can adjust that behavior with your Affirm account contact. Second, many merchants run two providers, one for pay-in-four and one for longer financing, to cover both a $120 cart and a $1,800 cart. That is a supported pattern, but every additional provider adds another messaging script to the page, which brings us to performance.
Installing BNPL on Magento and Hyva
On a Hyva storefront the checkout layer depends on whether you run the legacy Luma checkout or Hyva Checkout. Hyva Checkout supports 40-plus payment providers through compatibility modules maintained by Hyva, the payment service providers, and the community, all installed with Composer. Klarna, PayPal, Stripe, Adyen, and Afterpay through Scalapay are among the tracked integrations, and several are marked CSP compatible in the Hyva integration tracker.
The install pattern is consistent. You pull the module with composer require, run bin/magento setup:upgrade, add your merchant credentials in the admin payment configuration, and enable the method for the right store views. If you are on Hyva Checkout, confirm the provider has a Hyva Checkout compatibility module rather than only a Luma module, because a Luma-only payment component will not render in the React-based Hyva Checkout. If you are still on the Luma checkout under a Hyva theme, the standard provider module usually works, since the payment step is not Hyva-rendered.
For the messaging layer, the provider gives you a script snippet and a small placement component. On Luma you would drop it into a template or a widget. On Hyva, you place it in your theme templates or a CMS block, and this is where the framework matters. Hyva replaced Knockout and RequireJS with inline Alpine.js and native JavaScript, so there is no RequireJS loader to hang the provider script off. You add the script directly, and you control exactly when and how it loads. That control is an advantage only if you use it.
Loading on-site messaging without wrecking Core Web Vitals
A BNPL messaging script is third-party JavaScript that you do not control, and it runs on your most important pages. Dropped in naively, it becomes a render-blocking or main-thread-hogging liability that eats the interaction responsiveness a Hyva build was meant to protect. The fix is disciplined loading, not avoidance.
Load the messaging library with defer (or async where order does not matter) so it downloads in parallel and never blocks HTML parsing. Google’s web performance team recommends loading non-critical third-party scripts asynchronously and keeping them off the critical path. On a Hyva page, the provider script is exactly the kind of independent third-party code that should never sit render-blocking in the head.
The subtler problem is layout shift and interaction delay. A messaging widget that renders after the price, pushing content down, hurts Cumulative Layout Shift. Reserve vertical space for the widget with a min-height container so the estimate fills a slot that already exists rather than shoving the add-to-cart button down the page. And because these scripts execute on the main thread, they compete with Alpine.js for responsiveness; if you are watching your Interaction to Next Paint, treat every added provider script as a cost. The patterns for keeping interactions fast on Hyva are the same ones covered in Bemeir’s guide to reducing Magento INP on a Hyva storefront.
One more Hyva-specific gotcha: dynamic price components. On configurable products where the price changes when a shopper selects a variant, the messaging widget needs to recalculate. That means hooking the provider’s refresh method into the Alpine.js event that fires on variant change, rather than assuming the widget updates itself. Skipping this leaves shoppers seeing an installment estimate for the wrong price.
Content Security Policy and third-party payment scripts
If you run a strict Content Security Policy, and enterprise and B2B stores increasingly should, every BNPL script and its network calls need explicit allowances. Hyva’s move to inline Alpine.js makes CSP more achievable than it was on Luma, but a third-party messaging library that injects its own inline styles or scripts can violate a strict policy and silently fail to render. Confirm the provider is CSP compatible, add the required script-src and connect-src sources, and roll the policy out in report-only mode first so you catch violations before they break the widget. The full approach is in Bemeir’s walkthrough of Content Security Policy on a Hyva Magento storefront.
Consumer BNPL is not B2B net terms
A frequent point of confusion for merchants running both consumer and wholesale channels: Affirm, Klarna, and Afterpay are consumer financing products. They are not a substitute for B2B payment on account or company credit terms. A wholesale buyer expecting net 30 against an approved credit line is a different workflow entirely, usually tied to your ERP and company account structure, not a third-party consumer lender. If your store serves both audiences, scope them separately. Bemeir’s technology partner ecosystem spans both consumer BNPL providers and the B2B credit and ERP integrations that real net terms require, and getting the two channels to coexist cleanly is a core part of how Bemeir builds Magento stores.
FAQ
Does Buy Now Pay Later work with Hyva Checkout or only Luma checkout?
Both, but through different modules. Hyva Checkout needs a provider integration built for it, and 40-plus payment methods including Klarna, PayPal, Stripe, and Afterpay through Scalapay have Hyva Checkout compatibility. If you run the Luma checkout under a Hyva theme, the standard Luma payment module generally works because the payment step is not Hyva-rendered. Always confirm which checkout you run before choosing a module.
How much do BNPL providers charge the merchant?
More than card processing. Card rates sit around 2 to 3 percent per transaction, while BNPL merchant fees run higher and vary by provider, cart size, and risk. You are paying for conversion lift and up-front settlement, since the provider pays you immediately and carries the repayment risk. Model the fee against your real average order value before committing to a provider.
Will adding BNPL messaging slow down my product pages?
It can, if you load it carelessly. The messaging widget is third-party JavaScript. Load it with defer or async so it never blocks rendering, reserve layout space so it does not cause layout shift, and hook its refresh into variant-change events on configurable products. Treat every provider script as a main-thread cost that competes with your Core Web Vitals.
Can I offer more than one BNPL provider at once?
Yes, and many merchants do, pairing a pay-in-four provider for smaller carts with a longer-financing provider for higher tickets. The tradeoff is that each provider adds another messaging script and another checkout method to maintain. Only run the providers your cart mix justifies, and consolidate messaging placements so you are not stacking multiple widgets on one product page.
Is BNPL the same as offering B2B net terms to wholesale buyers?
No. Affirm, Klarna, and Afterpay are consumer financing products. B2B payment on account and company credit lines are a separate workflow, usually tied to your ERP and company account structure rather than a consumer lender. If your store serves both consumer and wholesale audiences, scope and build the two payment experiences separately.
Getting it right the first time
BNPL is not a plugin you flip on. The payment layer is straightforward Composer work. The messaging layer is where a Hyva store either keeps its speed or gives it back, and where a configurable-product edge case can quietly show shoppers the wrong number. Scope both layers, load the scripts with discipline, and test the messaging against your real catalog before launch. As the first US Hyva Gold Partner, Bemeir has shipped these integrations on real stores; you can read more about the team on the About Bemeir page.
