How Partner Accounts work

Learn how Partner Accounts are structured in the Klarna Network so you can support onboarding, operations, and flexible configurations for different business setups.

​Klarna’s Partner Account model defines how companies connect, are configured, and operate within the Klarna Network.

By understanding how Partner Accounts and Partner Products work together, you can design scalable integrations that support global operations and complex business structures.

flowchart LR subgraph Partner direction TB PA(Partner Account) PAY_PRO(Payment Product) PA_BRANDS_STORES(Brands & Stores) PA_PBE(Partner Business Entity) PA_PORTAL(Portal User / Access) PA -->|1| PAY_PRO PA -->|1..n| PA_PBE PA -->|1..n| PA_BRANDS_STORES PA -->|1..n| PA_PORTAL end subgraph Acquirer direction TB PA_AP(Partner Account) ACQ_PRO(Payment Acquiring Product) PA_AP_API_KEY(API Keys) PA_AP_WEBHOOK_CONFIG(Webhook Configuration) PA_AP -->|1| ACQ_PRO PA_AP -->|1..n|PA_AP_API_KEY PA_AP -->|1..n|PA_AP_WEBHOOK_CONFIG end Acquirer -->|onboards| Partner class PA primaryEntity class PA_AP primaryEntity

A Partner Account holds all relevant data that allows a company to work with Klarna. Products represent what the company is using from Klarna, and are connected to multiple configuration data points.

Some resources, like Stores, Brands and Business Entities, can be reused across the products, and are also directly connected to the Partner Account.

Link copied!

The Partner Account model describes how a company’s relationship with Klarna is represented, configured, and extended with specific products and shared resources.

flowchart LR subgraph Partner direction TB PA(Partner Account) PAY_PRO(Payment Product) PA_BRANDS_STORES(Brands & Stores) PA_PBE(Partner Business Entity) PA_PORTAL(Portal User / Access) PA -->|1| PAY_PRO PA -->|1..n| PA_PBE PA -->|1..n| PA_BRANDS_STORES PA -->|1..n| PA_PORTAL end subgraph Acquirer direction TB PA_AP(Partner Account) ACQ_PRO(Payment Acquiring Product) PA_AP_API_KEY(API Keys) PA_AP_WEBHOOK_CONFIG(Webhook Configuration) PA_AP -->|1| ACQ_PRO PA_AP -->|1..n|PA_AP_API_KEY PA_AP -->|1..n|PA_AP_WEBHOOK_CONFIG end Acquirer -->|onboards| Partner class PA primaryEntity class PA_AP primaryEntity

​At the center is the Partner Account, which represents the Partner or Acquiring Partner. Each Partner Account can have one or more Partner Products that define which Klarna services are available. Those products reference shared resources such as Partner Business Entities, Stores, Brands, and Store Groups.

Together, these building blocks let you model a wide range of organizational structures, from a single legal entity with one brand to global companies with multiple entities, brands, and store locations.

Link copied!

A Partner Account represents either an Acquiring Partner or a Partner working with Klarna. It is the core object that allows a Partner or Acquiring Partner to operate in the Klarna Payment Network.

Partner Accounts define who interacts with Klarna, while Partner Products define what services or features are available to that Partner.

Each Partner Account:

  • Holds the core data that identifies the Partner or Acquiring Partner.
  • Acts as the parent for Partner Products that expose specific Klarna services.
  • Connects to shared resources (Business Entities, Stores, Brands, and Store Groups) that describe how the Partner operates toward customers.

Link copied!

A Partner Product defines which Klarna services are available to a Partner Account.

Each Partner Product has a type that indicates the specific Klarna product it represents, and each type has its own configuration and linked resources.

Currently, there are two Partner Product types:

Payment Product

The Payment Product represents Klarna’s payments offering for a Partner Account, including pricing and all available Payment Programs.

Each Payment Product is connected to a Payment Profile, which specifies:

Below each Payment Product, you will find Payment Accounts. Payment Accounts are used to assign identifiers to specific Partner configurations, for example:

  • Merchant category codes (MCCs).
  • Associated brand or brands.
  • Specific stores or store groups.
  • Other configuration details relevant for processing payments.

Payment Accounts support complex account structures, such as companies with multiple legal entities, stores, and brands.

For more detailed modeling information, see how to model your Partner Account.

A Payment Acquiring Product represents an Acquiring Partner’s acquiring offering in the Klarna Payment Network and enables the Acquiring Partner to onboard and manage its own Partners within Klarna.

A Payment Acquiring Product holds:

This structure lets you support different types of Partners while handling cases where you work with multiple legal entities and settlement setups, so a global company can operate as a single, consistent Partner in the Klarna Payment Network.

For more details about modeling your own account as an Acquiring Partner, go to understand your own account.

Partner Accounts can include additional resources that enhance both operational accuracy and customer experience:

  • Partner Business Entities: Represent a legal entities their metadata
  • Stores: Represent locations, physical or digital, where Klarna’s products and services will be made available by your Partners
  • Brands: Are the consumer representation of a company, its visual assets and links.
  • Store Groups: Allow multiple stores to share one brand identity.

Maintaining accurate information in these resources ensures a better customer experience and supports Klarna’s fraud and risk controls