Klarna Payments vs Klarna Checkout: plugin choice

Compare the actual Klarna payment and checkout integrations for your platform, checking regional support, customer flow and order/payment records.

Choose Klarna Payments to add Klarna to your existing WooCommerce checkout. Choose Kustom Checkout, formerly Klarna Checkout, when you want its checkout experience and your merchant country is supported.

For an Australian WooCommerce store, Klarna Payments is the relevant starting point: WooCommerce lists Australia among its supported markets. Kustom’s plugin lists other merchant countries, without Australia. Selling to Australian customers and accepting an Australian merchant are different questions.

Choose by the actual checkout responsibility

Klarna Payments keeps WooCommerce’s checkout in place, while Kustom Checkout supplies a checkout experience that includes payment selection and customer details. This comparison uses their WooCommerce plugins, where the similar names can otherwise hide a substantial change.

The former Klarna Checkout is now Kustom Checkout, operated by an independent company. Its plugin still has a Klarna-labelled download address, so an old link does not identify the current provider. The official plugin listing names Kustom and lists supported merchant countries.

Klarna for WooCommerce is the plugin that includes Klarna Payments. It also includes optional tools such as Express Checkout and Sign in with Klarna. Those tools do not make it the former Klarna Checkout product.

An existing Australian store that wants to retain its delivery fields and other payment methods has a clear reason to start with Klarna Payments. A merchant in a Kustom-supported market can consider Kustom when replacing the customer-facing checkout is part of the requirement.

Compare the customer and order flow

WooCommerce retains the store order in both approaches, but the customer enters details and selects payment through different interfaces.

ResponsibilityKlarna PaymentsKustom Checkout
Checkout interfaceKlarna payment component within the existing checkoutKustom checkout interface connected to WooCommerce
Customer detailsExisting checkout fields, with optional Klarna sign-in toolsDetails entered through Kustom and saved to the WooCommerce order
Payment selectionKlarna alongside the store’s other methodsMethods enabled through the Kustom setup and agreement
Order recordWooCommerce order linked to the provider transactionWooCommerce order linked to the Kustom order
Capture and cancellationControlled by configured order-management settingsControlled by Kustom order-management settings or its portal

Klarna’s WooCommerce overview describes its hosted payment component within the existing checkout. Payment approval remains a provider decision. A customer’s store account and their payment-provider identity have separate purposes.

Kustom’s configuration guide explains that its customer details populate the WooCommerce order. Removing underlying WooCommerce checkout fields can break that handover, even when customers never see those fields.

Confirmation also needs more than a visible thank-you page. Kustom’s documented flow creates a pending WooCommerce order before the payment is finalised. The plugin confirms payment status during the return journey. Staff must not manually promote an unpaid pending order to a paid status. See the checkout flow.

Refunds need the same separation of records. With Kustom order management enabled, WooCommerce can send order actions to Kustom. When staff manage payments in the provider portal instead, they must also maintain the corresponding WooCommerce records. Assign one refund workflow so two staff members cannot refund the same enquiry through different screens.

Check support, fees and compatibility

Compare the exact plugin release and merchant agreement before comparing implementation quotes. A downloadable plugin does not establish your processing fees or supported payment methods.

Krokedil’s technical pages list these minimum requirements for the documented releases.

RequirementKlarna for WooCommerce 4.14.0Kustom Checkout 2.24.1
WordPress6.75.0
WooCommerce5.6.09.7.0
PHP8.07.4

Use the Klarna technical requirements and Kustom technical requirements for the release being installed. A plugin’s minimum version is a compatibility floor, not a recommendation to run an unsupported platform release.

WooCommerce’s older Klarna guide gives a lower PHP requirement than the current plugin information. Use the current technical information when planning the installation. Its compatibility guidance also identifies altered checkout templates and removed fields as common trouble spots.

For the commercial comparison, request each provider’s written terms for the same merchant country and turnover. Compare the transaction percentage and fixed charge, then refund treatment, dispute charges and settlement timing. Include tax treatment and the currency of each charge. Add the developer’s cost for checkout changes and ongoing support.

Klarna’s configuration documentation requires an agreement for each enabled country. Country credentials and currency configuration must match the intended transactions. A payment method appearing for one customer does not establish availability for every customer or market.

Verify one test order and recovery

Follow one order through the store and provider’s test environments, then check what happens when that journey is interrupted. Installation success proves that the plugin activates. Payment readiness requires matching order and payment records.

  1. Use an isolated test store with test credentials. Buy a product with delivery and tax so the final total exercises the checkout calculation.
  2. Record the WooCommerce order reference and provider reference. Compare the amount and currency in both systems, then check the customer confirmation and stock change.
  3. Apply the configured capture action. Confirm that the provider records the capture before treating the money as captured.
  4. Cancel an uncaptured test order. Separately refund a captured test order, checking both systems after each action.
  5. Abandon a payment and trigger a failed payment using the provider’s test cases. Confirm that neither order becomes ready for fulfilment.
  6. In the test environment, interrupt the return journey or callback delivery. Restore it and confirm that the same transaction reconciles without creating another paid order.
  7. Where the integration supports safe callback replay, repeat a notification. Check that stock, captures and customer emails are not duplicated.

Krokedil’s callback requirements explain why HTTPS, working permalinks and reachable callback addresses matter. A security rule that blocks those requests can leave the store and payment provider out of sync.

Keep fulfilment paused whenever the two records disagree. Resolve the existing transaction by its provider reference before inviting another payment attempt. For an Australian store retaining WooCommerce checkout, complete this journey with Klarna Payments before considering a broader checkout replacement.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup