Overview

This guide explains what is changing, what setups are affected, and how to complete the switch depending on whether you use the Kustom extension, a legacy Klarna 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:

Replace: api.klarna.com
With: api.kustom.co

Playground:

Replace: api.playground.klarna.com
With: api.playground.kustom.co

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 are using a plugin, the endpoint update should be handled by upgrading the plugin.
If you are using 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 Adobe Commerce extension
- Legacy Klarna Adobe Commerce 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 secrets or API credentials (if required).

How to complete the switch

Option 1: Kustom Adobe Commerce extension

Use this option if you use the Kustom extension from the Adobe Commerce Marketplace.

Update the extension to the latest version from the Adobe Marketplace, version 1.1.1.
Deploy the update to your staging environment.
Run your standard Adobe Commerce deployment steps.
- Apply database upgrades if your deployment process requires it.
- Clear caches.
Complete an end-to-end test purchase in staging.
Deploy the same update to production.
Complete a production test purchase.

Option 2: Legacy Klarna Adobe Commerce plugin

Use this option if you are still on a legacy Klarna plugin.

Plan and execute a migration from the legacy Klarna plugin to the Kustom extension 1.1.1.
After migration, verify your integration is calling api.kustom.co.
Complete an end-to-end test purchase in each environment.

Option 3: Custom or direct API integration

Use this option if you call the APIs directly (without the Kustom extension handling endpoints for you).

Identify what to change

Search your codebase and configuration for:

api.klarna.com
klarna.com
Any service-specific Klarna URLs your integration uses

Update the base URL

Identify where the API base URL is defined (environment variables, configuration files, secret manager, or code constants).
Update the base URL to https://api.kustom.co.
Deploy the change to staging.
Run an end-to-end test in staging.
Deploy the change to production.
Run a production test purchase.

Verification checklist

Verify that you have the correct plugin.
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.