Partner self-service in Klarna's Partner portal
Let your Partners self-serve Payment Program enablement directly inside Klarna's Partner portal. Cover standard portal access and the optional deep-link entry point from your own portal into the enablement screen, and surface Partner-specific sell rates so the choice is informed.
Overview
With this method, the Partner self-serves Payment Program enablement inside Klarna's Partner portal. They evaluate available Payment Programs and turn on the optional ones from a Klarna-hosted UI. As the Acquiring Partner, you don't build any enablement screens yourself: you provide access to the portal, supply sell rates so Klarna can render real Partner-specific pricing, and (when webhooks are available) consume notifications.
Awareness and discovery of optional Payment Programs still happen in your own surfaces. Klarna's Partner portal hosts enablement, but Partners learn that optional Payment Programs exist through your portal, lifecycle communications, and account-manager touchpoints. See Drive Partner awareness and adoption in the overview.
This method is the fastest way to expose Payment Program enablement to your Partners and the lowest-maintenance option in the long term, since UX changes ship from Klarna's side.
The two integration methods are mutually exclusive. If you pick this method, you do not surface a Partner-facing enablement UI in your own portal. See the overview for the full exclusivity rules.
sequenceDiagram
participant P as Partner
participant AP as Acquiring Partner portal
participant K as Klarna Partner portal
P->>K: Reaches the Payment Programs screen<br/>(directly, or via deep link from AP portal)
K-->>P: Renders available Payment Programs
K-->>P: Displays sell rate (fetched from Acquiring Partner)<br/>or generic message if no sell-rates API
P->>K: Confirms enablement
K->>K: Creates Payment Program Enablement
Prerequisites
Before implementing this method, make sure you have completed the common prerequisites.
In addition, you need:
- Partner portal access already configured for your Partners. Follow Grant access to Klarna Partner portal before starting here.
- Sell rates priced and available for every optional Payment Program at Partner onboarding. Any Partner with portal access can land on the Payment Programs screen at any time so your pricing for every optional program needs to be ready to display (or referenced via your fallback message) from day one. Decide which path you'll take per the Surfacing sell rates in the portal section below.
The optional deep-link entry point reuses the mechanism documented in Grant access via Deep Link. If you've already implemented deep linking for portal access, you can extend it to land Partners directly on the Payment Program enablement screen.
Confirm the enablement configuration agreed with Klarna
You and Klarna agree at the Acquiring Partner level on whether your Partner base runs on global enablement (one click: applies to all Klarna-supported consumer countries, including ones added in the future) or advanced enablement (Partners enable specific consumer countries, and any new Klarna-supported countries are not enabled by default). The two configurations are mutually exclusive and the choice applies across all the Partners you onboard. Your Partners see only the configuration agreed for you when they open the Payment Programs screen. See Global vs. advanced enablement in the overview for the definitions and the criteria Klarna uses to recommend the right configuration for you.
Implementation
With this method there is no enablement UI to build. The Payment Programs experience lives inside Klarna's Partner portal. The integration work is to make sure Partners can reach it, and to drive awareness of the optional Payment Programs available to them. Even when enablement is hosted by Klarna, awareness and adoption stay your responsibility. See Drive Partner adoption of optional Payment Programs (coming soon) for the channels and patterns to use.
Step 1: Confirm Partners can reach the Klarna Partner portal
Verify that your Partners can log in via the access method you've implemented (Deep Link, IdP/SAML, or User Management API). Once they can, the Payment Programs section is available to them automatically. Communicate to your Partners that they can manage their Payment Programs from inside Klarna's Partner portal.
Step 2 (optional): Add a deep-link entry point from your own portal
For a more integrated experience, add a "Manage Payment Programs" entry point inside your own Partner-facing portal that takes Partners directly to the enablement screen. Use createDeepLink
with a
with a target that points to the Payment Programs section. The deep link includes a signed JWT that authenticates the Partner without an extra login step.A dedicated
target value that lands Partners directly on the Payment Programs enablement screen is on the roadmap and will be documented in the deep link reference once it ships. Until then, use the closest existing Partner portal target and coordinate with your Klarna Business Developer.| Do | Don't |
|---|---|
Place the entry point where Partners already manage their Klarna integration. | Bury the entry point somewhere disconnected from the Partner's Klarna management flow. |
Open the deep link in a new tab so Partners don't lose their place in your portal. | Navigate Partners away from your portal to reach the enablement screen. |
Restrict the signed deep link to the authenticated Partner it was issued for. | Cache, share, or expose the short-lived JWT to anyone other than that Partner. |
Treat Klarna's Partner portal as the single surface for managing Payment Program enablement state. | Duplicate per-Payment-Program enablement state in your own UI — it creates two surfaces to keep in sync. |
Surfacing sell rates in the portal
Sell rates are negotiated between you and your Partner. Klarna does not own that pricing. The Klarna Partner portal supports two paths for surfacing the price next to each Payment Program; pick the one that matches how your pricing is managed.
Path A: you expose a sell-rates API to Klarna
Klarna calls a pricing endpoint that you expose and renders the Partner-specific sell rate (or a link to where the Partner can view it) inline next to each Payment Program. This is the recommended path because Partners see the actual rate (or know where to find it) at the moment of choice.
The inbound pricing API that Klarna will call to fetch your sell rates is currently in design phase. Specs are not yet implemented. The full contract will be documented here once it ships; coordinate with your Klarna Business Developer for early-access timing.
Path B: you don't expose a sell-rates API
You can also choose not to expose a sell-rates API. In that case, the Klarna Partner portal renders a generic message in the price column that refers the Partner back to you for price details. For example, "For pricing, contact your Acquiring Partner." The Partner can still self-serve the enablement; they learn the price from you out-of-band rather than seeing it inline.
Both paths are first-class. Klarna always renders one of the two outcomes, so the Partner never sees a blank price field. Decide which one fits your pricing model and Partner experience.
Staying in sync: enablement webhooks
When a Partner enables or ends a Payment Program in the Klarna Partner portal, you may want a notification so you can keep your own systems aligned. Whether webhooks add value here depends on what you do with the information on your side. Coordinate with your Klarna Business Developer if your use case calls for it.
A webhook that notifies you when a Payment Program Enablement is created or deleted is on the roadmap. Until it's available, periodically reconcile state by calling listPaymentProgramEnablements for each Partner.
for each Partner.Testing
Use your test environment to verify the end-to-end flow:
- Portal access: log in to Klarna's Partner portal as a test Partner and confirm the Payment Programs section is reachable.
- Sell rate display: depending on your scenario, confirm either the Partner-specific sell rate (Path A) or the "contact your Acquiring Partner" message (Path B) appears next to each Payment Program.
- Enablement persistence: after a test Partner enables a Payment Program, call listPaymentProgramEnablements for that Partner Account and confirm the new enablement is returned.
- End-to-end activation: after 15 minutes (the time it takes for internal Klarna caches to refresh), confirm the enabled Payment Program is available at checkout for that Partner.
Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| Partner sees no Payment Programs in the portal | The Partner Account has no active Payment Program Plan, or the plan exposes no OPTIONAL programs in their region | Verify with listPaymentProgramsForPaymentProgramPlan. |
| Partner sees the "contact your Acquiring Partner" message but expected inline pricing | You're on Path B (no sell-rates API exposed) | If you intended to be on Path A, coordinate with your Klarna Business Developer on the inbound pricing API. Otherwise, make sure the touchpoint referenced in the generic message is one your Partner already has with you. |
| Enablement appears in the portal but not at checkout | Klarna caches not yet refreshed | Wait 15 minutes and retry. |
Next steps
- If you need full UX control inside your own portal instead, see Method 2: Partner self-service in your Partner portal, which offers two paths:
- Method 2a: Compose the screen yourself. You build the UI and source the screen data from your own systems.
- Method 2b: Use Klarna's Payment Programs Presentation API. You host the UI but render Klarna-curated presentation data.
- For the underlying resource model, see Payment Program Enablement.