Plan and submit changes

Ensure data is accurate at Klarna for compliance with Klarna Network Rules and regulations by keeping Partners updated.

Maintaining accurate and up-to-date Partner information within Klarna systems is critical for enabling a high quality integration while maintaining compliance with Klarna Network Rule.

Whenever a data point is updated on the Acquiring Partner systems, it should be immediately replicated to Klarna systems. Ensuring accurate Partner data is stored at Klarna is required for all Acquirers integrating to Klarna.

Maintaining consistency using the APIs

The Acquiring Partner is required to maintain data synchronized between their systems and Klarna systems. Whenever an update occurs, the corresponding API operation must be triggered immediately after the update is done on the Acquirer systems:

Resource	API Operations	Use cases
Partner Account	updateAccount	When the primary contact of the account has changed
Partner Business Entity	updatePartnerBusinessEntity createPartnerBusinessEntity	When any legal entity data point changed, such as a new financial license was added, the registration address changed or similar When the Partner became Payouts Enabled, the payout delay changed or similar When any Stakeholder data changed due to a structural change of the company or similar When the operating address of the Partner has moved When a new legal entity is introduced for this Partner, for example when the Partner started selling in a new market under a new legal entity.
Brand	updateBrand createBrand	When branding assets (such as logo) changed When the Partner changed their display name When a new brand is added to the Partner Account
Stores	updateStore createStore	When a new physical, online or mobile store was added by the Partner When an existing store changed information When the URL of the partner has changed
Store Groups	updateStoreGroup createStoreGroup	When set of stores has moved to a different brand When a new store group is needed, for example when a new sub-brand is added
Partner Account Relationships	createPartnerAccountRelationship updatePartnerAccountRelationship	When a Partner becomes part of a corporate group represented by another Partner Account, for example as a subsidiary of an existing organization When a Partner joins a platform that manages or aggregates payments on its behalf When a Partner leaves a platform or corporate group — end the relationship by setting `effective_to` to a past or current date When the effective period (`effective_from` or `effective_to`) of an existing relationship changes

Some resources are immutable and must be recreated to reflect changes:

Resource	API Operations	Use cases
Payment Account	createPaymentAccount	When the Partner has onboarded a new legal entity in which Payments are going to be offered

Partner Accounts

Partner Business Entities

Partner Stores and Brands

Partner Account Relationships

Payment Accounts

API & SDK references

Update Partner Account

Update a Partner Business Entity

Create a Partner Business Entity

Update a Brand

Create a Brand