Skip to main content

Endpoint switch for WooCommerce

A technical, step-by-step guide for switching a WooCommerce integration from legacy Klarna endpoints to Kustom endpoints.

Updated this week

Overview

This guide explains what is changing, which WooCommerce setups are affected, and how to complete the switch depending on whether you use the Kustom WooCommerce plugin or a custom API integration.


What is the endpoint switch?

Historically, many integrations have called Kustom services via *.[klarna.com](<http://klarna.com>) domains. The endpoint switch means updating those calls so they go to *.[kustom.co](<http://kustom.co>) instead.


What’s changing

Update your integration to use the new base endpoint:

Production:

Playground:


What systems are affected

This change can affect API traffic to the following services:

Production:

  • Checkout API

  • Order Management API

  • Settlement API

  • Hosted Payment Page (HPP) API

Playground

  • Checkout API

  • Order Management API

  • Settlement API

  • Hosted Payment Page (HPP) API


Key things to know

  • You must update all environments you operate (staging and production).

  • If you use the WooCommerce plugin, the endpoint update is handled by upgrading the plugin (note: it may still be listed as Klarna Checkout in plugin directories).

  • If you use a custom integration, you must update the base URL in code or configuration.

  • It is recommended to generate new Kustom API credentials as part of this change.

  • sFTP-based settlement files use separate credentials.


Before you start

  • Identify your setup:

    • Kustom WooCommerce plugin

    • Custom or direct API integration

  • Ensure you can do a full end-to-end checkout test in staging.

  • Ensure you have access to update plugin versions and configuration, and to rotate credentials if needed.


How to complete the switch

Option 1: Kustom WooCommerce plugin

Use this option if you use the official WooCommerce plugin (currently listed as Klarna Checkout).

  1. Update the plugin to the latest version (via WordPress Admin or your deployment flow).

  2. Apply the update to your staging environment first.

  3. Confirm your checkout still loads and you can complete a test purchase end-to-end.

  4. Apply the same update to production.

  5. Complete a production test purchase.

Option 2: Custom or direct API integration

Use this option if your WooCommerce site calls the APIs directly (for example via a custom plugin, middleware, or server-to-server integration).


Identify what to change

Search your codebase and configuration for:

Update the base URL

  1. Identify where the API base URL is defined (environment variables, wp-config, plugin settings, secrets manager, or code constants).

  2. Update the base URL to https://api.kustom.co.

  3. Deploy the change to staging.

  4. Run an end-to-end test in staging.

  5. Deploy the change to production.

  6. Run a production test purchase.


Verification checklist

  • Confirm outbound calls go to api.kustom.co.

  • Confirm there are no remaining outbound calls to api.klarna.com.

  • Complete an end-to-end purchase test.

  • Confirm post-purchase actions work as expected (capture, refunds, order status updates if applicable).

  • Confirm settlement reporting continues as expected.


References

Did this answer your question?