API and SDKsSupport
Account configuration management

Configure and manage Acquiring Partner and Payment Acquiring Accounts for seamless integration with Klarna, ensuring proper settlement setups and efficient operations.

As an Acquiring Partner integrating and distributing Klarna products, we work closely with you during the account setup process. Your Acquiring Partner Account will have access to specific resources assigned by Klarna, designed to streamline operations and support a seamless integration with Klarna services.

As an Acquiring Partner, your account is configured with an Acquiring Product that enables you to onboard Partners with Klarna. To support different acquiring configurations, your product may be connected to one or multiple Payment Acquiring Accounts.

Your Acquiring product also includes a set of Payment Profiles. Each profile contains a Price Plan and a Payment Program Plan, which are assigned to the partners onboarded. These configurations are linked to the newly onboarded payment product of a Partner.

classDiagram direction LR class APA["Acquiring Partner Account"] class AP["Acquiring Product"] class PAA["Payment Acquiring Account"] class LE["Legal Entity"] class SC["Settlement Configuration"] class PP["Price Plan"] class PPP["Payment Program Plan"] class PayPro["Payment Profile"] APA .. "1+" LE APA --> "1+" AP: pre-configured with AP --> "1+" PAA: pre-configured with PAA --> "1" SC : pre-configured with AP --> "1+" PayPro : pre-configured with PayPro --> "1" PP : pre-configured with PayPro --> "1" PPP : pre-configured with PAA --> "1" LE : pre-configured with

​

Further configuration points may become available in a future release.

Payment Acquiring Accounts are objects that represent your acquiring setup towards Klarna. Payment Acquiring Accounts have their own identifier and reference and are configured with a specific settlement configuration and acquiring legal entity.

Every Partner you onboard must be connected to a Payment Acquiring Accounts, which is assigned during onboarding. Payment Acquiring Accounts are especially useful for onboarding Partners in different acquiring regions, as they specify the legal entity responsible for acquiring and expanding the countries where you can onboard Partners to Klarna.

Payment Acquiring Accounts are created by Klarna and provided to you when your integration is set up.

Price Plans are read-only and cannot be modified through the Price Plans APIs. They outline the pricing rates for transactions based on the Merchant Category Code (MCC) and market specifics.

Each price plan encompasses rates that can vary depending on the market, payment program, and store type. Additionally, microtransaction caps may override the base pricing. Klarna creates and maintains these price plans.

The Payment Programs API allows Acquiring Partners to manage Klarna’s consumer value offerings through configurable Payment Programs.

Acquiring Partners can list and retrieve available programs, enable or disable optional ones, and tailor configurations based on country, currency, and merchant category.

Payment Programs are organized within Payment Program Plans. Each program can be enabled for specific conditions by creating a Payment Program Enablement. The API also supports reading detailed program info, validating eligibility, and managing enablements on behalf of Partners.

Learn more about Payment Programs here.

Payment Profiles are an assisting object that group multiple configuration identifiers into one. Payment profiles are provided to you by Klarna and can be read utilizing the List Payment Profiles API.

Currently, payment profiles contain both the price_plan_id and the payment_program_plan_id, and therefore are used to connect these two data points with the payment product of a Partner.

A settlement configuration outlines how Klarna will settle funds to a partner. This setup includes various components crucial for processing payouts:

  • Payout schedule: Specifies when the payout will occur based on when the transaction is captured.
  • Settling business entities: Identifies the legal entity receiving the funds. This is also the entity linked to the bank account where funds are deposited. This generally refers to the local entity of the Acquiring Partner that onboarded the Partner.
  • Bank account details: Information regarding where funds should be transferred.
  • Payout prefix: A defined prefix added to payouts to assist with identification and reconciliation.

As an Acquiring Partner onboarding Partners through Klarna, you manage their settlements, thereby simplifying their reconciliation process. Our recommendation is that the account structure used to onboard a Partner with Klarna matches the account structure defined in your platform, keeping a 1:1 account ratio between the two systems.

Example
  1. Local-Pay is a global Acquiring Partner that processes transactions across multiple regions. They prefers to receive payouts for all transactions globally to the same bank accounts for all Partners, regardless of their onboarding country or entity. Therefore, Local-Pay does not need to specify any specific settlement configurations during the Partner onboarding process.
  1. In contrast, Global-Pay is a global Acquiring Partner that also processes transactions across multiple regions. It prefers to settle payouts to different bank accounts by country and currency for administrative reasons. For example,
*Global-Pay prefers payouts for Partners onboarded in the UK to be directed to BankAccount1 for all currencies, while*Payouts for Partners onboarded in the EU should be directed to BankAccount2 for all currencies.Consequently, UK Partners will have a different Payment Acquiring Account than EU Partners. Global-Pay, as an Acquiring Partner, will be able to configure different settlement configurations based on the different Payment Acquiring Accounts in the Acquiring Product.