Klarna offers a global and interoperable platform designed to support partners management, transaction processing, post-purchase operations, and conversion rate optimization. Powered by the Web SDK and supported by extensive JavaScript SDK capabilities alongside Management and Partner Product APIs, this platform ensures seamless integration. As a Klarna partner, you are equipped to maximize the benefits of all available Klarna features.

As an Acquiring partner, understanding our solution principles and committing to them is essential before proceeding with integration and offering Klarna product suite to your Partners. This foundational understanding ensures that you can provide a best-in-class experience to your Partners, streamlining the integration and the adoption of future enhancements. A more detailed exploration of the following principles and their influence on the Klarna Network requirements, recommendations, and integration path is available in the Klarna Network Rules.

Integrate Klarna Network to offer a secure, globally accessible, and reliable payment experience. This document details required steps, recommended paths, and optional alternate flows, each marked according to their integration path and Klarna’s requirements.

Prerequisites

• Klarna account setup and credentials (API keys, mTLS, etc.).
• Verification of integration path for compliance with Klarna Network Rules.
• Thoroughly review the Klarna Integration Guidelines and Network Rules to avoid delays and ensure a smooth integration process.

Each integration must meet the following Klarna Network Requirements (KNR) principles:

• Safe and Secure Shopping
• Global Availability
• Integration Simplicity
• Product Suite Interoperability
• High Performance
• Payment Programs

To ensure Klarna is best able to integrate with your solution, Klarna provides multiple integration paths which may be combined as needed to suit your architecture.

Multiple integration paths can coexist across different touch points within a single Klarna integration. Apply the most relevant category to each touchpoint, and in cases where multiple categories overlap, ensure all applicable requirements are met.

Acquiring channels:

Integration requirements may also depend on the acquiring channel being used.

Partner account management:

For non-payment services, such as brand management, dispute handling, and access to external gateways, integration requirements vary based on the availability of a Partner-facing interface.

This framework provides a granular structure to clearly outline Klarna’s expectations for each integration path, ensuring a consistent and reliable experience for both Partners and customers.

Use this to verify that each integration step meets Klarna’s security, availability, interoperability, and performance standards. Integration paths are marked for specific requirements and alternate flows, each subject to Klarna approval.

Implement essential security measures to safeguard user data and maintain secure transactions.

Enable Klarna to verify the reliability, accuracy, and compliance of Acquiring Partner services: through the provisioning of a robust test environment.

• Required: provide a fully functional test environment that mirrors the production setup for all integration paths, allowing Klarna to perform end-to-end testing and validation of Acquiring Partner (AP) services.
• Required: include all available data points when onboarding partners. Optimizing partner acceptance rates requires the maximum amount of data - providing limited data will result in more partners being rejected. Additional data also helps to mitigate fraud and other financial crimes.

Make adding Klarna easy for Partners: Implement a streamlined process for onboarding Partners, ensuring complete and accurate account creation aligned with Klarna's requirements and enabling Partners to utilize Klarna services.

• Required: use Klarna’s Partner Management API to automate onboarding and create new accounts efficiently.
• Required: align Klarna account structures with internal systems, ensuring consistency and completeness during the onboarding process.
• Required: collect and provide all mandatory technical and risk-related data points for each Partner during onboarding. Failure to include required data points may result in escalations or delays.

Enable seamless system alignment to improve fraud detection and risk assessments, while enhancing customer trust and experience through accurate brand representation and reliable account management.

• Required: automate account updates within Klarna, confirm alignment through routine checks, and implement account suspension processes to maintain accurate statuses.
• Recommended: use resources-specific endpoints when making updates, allowing more robust capabilities and safer handling of resources.
• Alternative: use the “update all subresource” endpoint for handling all configurations within an account in a single call.

• Required: ensure account suspension propagates between systems automatically, so that changes in account status are consistently reflected.
• Required: integrate management webhooks to proactively manage account status changes, allowing timely updates and issue resolution.

Prevent unauthorized access to Klarna APIs: Ensure that only authorized users and systems can access your API, preventing unauthorized access.

• Required: use API keys for server-side REST APIs and Client IDs for the Web SDK.
• Required: transmit all API requests over HTTPS using TLS 1.2 or higher.
• Required: generate and securely store signing keys for each webhook. Configure webhooks to use the designated signing key, and validate each notification.
• Recommended: use unique API keys for each service or system interacting with Klarna.
• Recommended: generate mTLS certificates according to Klarna’s requirements and rotate certificates well ahead of certificate expiry.
• Recommended: rotate provided API Key when onboarded. Use the API key provided via secure link to retrieve new API credentials. Disable initial credentials.

Maintain a high standard of data protection: Follow (at a minimum) Klarna’s recommended Security Protocols and Best Practices.

• Recommended: encrypt all stored credentials and enforce strong password policies.
• Recommended: conduct regular security audits and implement two-factor authentication for admin accounts.
• Recommended: use separate API credentials for each service to limit risk in the event of a security breach.

Efficiently collaborate to mitigate outages and other incidents: maintain an incident response plan that ensures prompt action and collaboration in the event of data breaches, outages, or fraud detection.

Ensure your integration is designed for worldwide accessibility, maintaining consistent performance and service reliability.

Display Klarna to all customers: verify the Payment status and Klarna’s availability for the purchase, and present across all integrations and customer markets.

• Required: Klarna Payment Services integration is built to function the same in all customer Markets: meaning payment request functions are identical in all markets without local changes.
• Required: addition of new Acquiring or customer Markets to Klarna Payment Services do not incur any technical or configurational changes to Partner Integrations.

​Ensure Klarna is presented with accurate and up-to-date messaging to all customers. Klarna may add issuing markets or update wording according to regulatory or market requirements.

Be consistent in currency conversion: maintain parity in Transaction Currency usage and availability across all payment methods, including Klarna.

Implement Klarna with minimal friction to ensure ease of use, efficient onboarding, and reliable operation.

Improve payment session outcomes and conversion, simplify post-purchase operations: enhance the accuracy and efficiency of payment sessions by ensuring that all relevant data is provided to Klarna for optimal processing.

• Required: ensure your API accepts klarna_interoperability_data as a passthrough field to allow Partners to share key information related to the payment session.
• Recommended: map any supplementary purchase information gathered by your APIs to the supplementary_purchase_data (SPD) object on payments to pass relevant data points, including line item details to Klarna.
• Recommended: educate Enterprise Partners to implement the Shopping Session API to share additional customer and transaction data points during the shopping journey.

Simplify dispute resolution: set up a dispute resolution process that enables partners to efficiently resolve payment disputes.

Make reconciliation easy: Manage pricing configurations and reconcile Klarna settlements to ensure accurate payment handling.

​Required: Configure and subscribe to settlement webhooks for timely event notifications.

Recommended: Integrate the Klarna Settlements API.

Alternate flow: Set up Klarna SFTP.

Make reconciliation easy: manage pricing configurations and reconcile Klarna settlements to ensure accurate payment handling.

• Required: configure and subscribe to settlement webhooks for timely event notifications.
• Recommended: integrate the Klarna Settlements API.
• Alternate flow: set up Klarna SFTP.

Ensure integration robustness by integrating proactive communication across services and integration paths.

Enable interoperability across Klarna’s product suite in all solutions to ensure seamless integration across all features.

Distribute Klarna Boost products: ensure all partners are able to access Klarna’s Partner Portal to retrieve credentials or access keys.

​Enable Partners to benefit from providing conversion boost products to their end customers by supporting streamlined purchase flows .

• Required: Enable partners to pass interoperability_token in your “order creation” or “payment confirmation” endpoint directly with no earlier interaction via, enabling transaction confirmation.
• Alternate: if order is in Status=completed, present a UX which reflects this state, when the interoperabilitytoken is passed in a create_session call. Allow the partner to explicitly call out the status in this interaction.

Enable Partners to deliver a consistent and streamlined customer journey. Retrieve and forward interoperability data to Klarna across all use cases and integration paths.

Optimize performance by adhering to Klarna’s presentation guidelines and prioritizing robustness and stability when integrating.

Partners are enabled to present Klarna in accordance with Klarna’s best practices; all products are available and all use cases supported.

• Required: document each step of the Klarna customer journey, from pre-purchase to post-purchase, allowing Partners to align their service experience with Klarna’s best practices.
• Required: include a full technical integration guide, covering API integration, platform plugins, mobile SDK, and in-store solutions. Ensure all methods for enabling Klarna are clearly defined for Partners of varying technical capabilities.
• Required: provide access to Klarna branding assets, including logo lock-ups, badges, and messaging templates, allowing Partners to maintain brand consistency in their marketing and storefronts.
• Recommended: use product matrices or interactive pages to clearly display geographical and product availability, ensuring Partners know where Klarna’s services are supported.

Public documentation is compliant with Klarna standards and aligned with agreed requirements, ensuring a consistent and high-quality experience for partners and users

• Required: complete a review with Klarna before releasing public documentation to ensure compliance with Klarna standards, clarity, and alignment.

Deliver a purchase experience on par with direct Klarna integration: Integrate Klarna’s payment solutions to support multiple transaction types, ensuring consistent and efficient payment processing for Partners.

​Deliver a post-purchase experience on par with direct Klarna integration: Implement robust transaction management processes to support captures, updates, refunds, and voids.

• Required: follow Klarna’s Transaction Management guidelines to handle all aspects of transaction management, including capturing payments, updating transaction data, issuing refunds, and voiding transactions as needed.
• Required: utilize webhooks for real-time notifications on transaction events, ensuring accurate transaction tracking and prompt action on changes.

Gracefully handle volume spikes: mitigate potential service disruptions due to flash sales or malicious behavior.

• Required: handle Klarna rate limiting and throttling mechanisms to manage traffic spikes effectively.
• Recommended: implement DDOS protection tools that can detect and mitigate high-frequency attacks.

Build a resilient integration to maintain stability, reliability, and high performance under varying loads.

• Required: use idempotency keys in POST and PATCH requests to prevent unintended duplication.
• Required: follow Klarna’s error codes and types for consistent handling and quick recovery.
• Recommended: use a structured logging approach to track webhook verifications, storing signatures and relevant identifiers for troubleshooting and auditing purposes.
• Recommended: perform regular load and performance testing of their integrations to ensure high availability and response times under peak traffic conditions.

Enable granular monitoring and streamlined troubleshooting.

• Required: set up real-time monitoring and alerting for quick issue detection and response.
• Recommended: apply Partner tagging for each API operation to improve tracking and troubleshooting.

Provide every Klarna customer with the same shopping experience across all integration approaches; all products are available and all use cases supported.

• Required: educate Partners on using interoperability features to maintain seamless customer experiences and pass Supplementary Purchase Data to Klarna.
• Required: emphasize Klarna's conversion-boosting features such as On-site messaging, Express checkout, and Sign-in with Klarna, helping Partners understand how these features enhance customer interactions.
• Required: guide Partners to include Klarna in key touchpoints (e.g., checkout pages, product pages), using dynamic presentation wherever possible to align with Klarna’s brand guidelines.
• Required: provide a clear overview of Klarna’s value proposition, highlighting the benefits of increased conversions, repeat business, and customer reach. Use a pre-approved Klarna payment descriptor to prevent misinterpretation and maintain brand integrity.