Overview
This guide explains what is changing, which PrestaShop setups are affected, and how to complete the switch depending on whether you use the Kustom PrestaShop add-on 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.comWith:
api.kustom.co
Playground:
Replace:
api.playground.klarna.comWith:
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 the PrestaShop add-on, the endpoint update is handled by upgrading the add-on.
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 PrestaShop add-on
Custom or direct API integration
Ensure you can do a full end-to-end checkout test in staging.
Ensure you have access to update module versions and configuration, and to rotate credentials if needed.
How to complete the switch
Option 1: Kustom PrestaShop add-on
Use this option if you use the official Kustom Checkout module for PrestaShop.
Update the add-on to the latest version (via PrestaShop Addons Marketplace or your back office deployment flow).
Apply the update to your staging environment first.
Confirm your checkout still loads and you can complete a test purchase end-to-end.
Apply the same update to production.
Complete a production test purchase.
Option 2: Custom or direct API integration
Use this option if your PrestaShop setup calls the APIs directly (for example via a custom module, middleware, or server-to-server integration).
Identify what to change
Search your codebase and configuration for:
Any service-specific Klarna URLs your integration uses
Update the base URL
Identify where the API base URL is defined (environment variables, module configuration, 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.