Overview

This guide explains what is changing, which OXID setups are affected, and how to complete the endpoint switch depending on whether you use an OXID module (by Fatchip) 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 use an OXID module, the endpoint update is handled by upgrading that module.
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:
- OXID 7 using the Kustom Checkout module by Fatchip
- OXID 6 using the Klarna Checkout module by Fatchip
- Custom or direct API integration
Ensure you can do a full end-to-end checkout test in a test or staging environment.
Ensure you have access to update your module version and to rotate credentials if needed.

How to complete the switch

Option 1: OXID 7 (Kustom Checkout module by Fatchip)

Use this option if you use the Kustom Checkout module for OXID 7.

Update to the latest module version.
Follow the module update documentation.
- German: https://wiki.fatchip.de/public/faqkustom7
- English: https://github.com/FATCHIP-GmbH/kustom-checkout-oxid7/wiki
Deploy the update in all relevant environments.
Complete a test purchase to verify the checkout is live.

Option 2: OXID 6 (Klarna Checkout module by Fatchip)

Use this option if you use the Klarna Checkout module for OXID 6.

Update to the latest module version.
Follow the module update documentation: https://wiki.fatchip.de/public/faqklarna
Deploy the update in all relevant environments.
Complete a test purchase to verify the checkout is live.

Option 3: Custom or direct API integration

Use this option if your OXID setup calls the APIs directly (for example via custom module code or middleware).

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, config files, secrets 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

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.