Payment Accounts

A Payment Account represents a specific Partner configuration in Klarna Network. It is used on the Payments API to define how Payment Transactions are processed across the network, connecting data points such as the Partner Business Entity, the Merchant Category Code (MCC) and Branding to each transaction.

Payment Accounts are created and managed by Acquiring Partners and are used to process transactions on the network. Each Payment Account is assigned a unique Payment Account Reference, which uniquely identifies the Payment Account within that Acquiring Partner.

A Payment Account sits under the Payment Product of a Partner. It can be created during onboarding or later using the createPaymentAccount operation. At least one Payment Account is required to allow a Partner to process transactions through Klarna’s Payment Products.

• Payment Product: The Payment Account belongs to a Payment Product. Pricing and Payment Program settings are inherited from the Payment Product.
• Partner Business Entity: Identifies which Partner Business Entity is offering the service to the customer on the other side of the transaction. This defines the country or jurisdiction under which the Partner is legally incorporated or registered to conduct business.
• Payment Acquiring Account: Determines both:

  • Which Settlement Configuration is applied to this Partner.
  • Which Acquiring Legal Entity is the counterparty for Payment Transactions under this Payment Account.
• Store Group: Specifies which branding is applied to Payment Transactions processed through this Payment Account.
• Payment Transactions: Every Payment Transaction is linked to a specific Payment Account to determine how it is processed within Klarna’s systems, including pricing, settlement, and branding configuration.

All Payment Account properties are immutable. To make changes, create a new Payment Account using the createPaymentAccount action and use it for new Payment Transactions.

A Payment Account’s lifecycle is managed internally by Klarna. It transitions between the following states:

Payment Account status reflects the state of the associated Payment Product and therefore cannot be changed directly through the API.

There are currently no webhooks associated with Payment Accounts. To receive status change notifications that affect whether a Payment Account can be used, subscribe to the Payment Product status change webhook.

Create a Payment Account during the Partner’s onboard flow or afterward using the createPaymentAccount operation. The number and configuration of Payment Accounts depend on how the Partner is modeled within the Acquiring Partner’s system (for example, multiple MCCs, brands, etc). For modeling guidance, refer to the Modeling your Partner Account article.

Retrieve all Payment Accounts associated with a Partner using the getPaymentAccounts operation. The response returns a list of Payment Accounts for the Partner. There is no list-by-single-reference action; when you already know payment_acquiring_account_id and payment_account_reference and need the payment_account_id, use resolvePaymentAccountId as described in Resolve identifiers.

Because Payment Accounts are immutable, you cannot update an existing Payment Account in place. To change the configuration (for example, MCC, branding, or acquiring setup), create a new Payment Account using the createPaymentAccount operation and start using the new Payment Account for subsequent Payment Transactions.

Payment Accounts are permanent and cannot be deleted or suspended. To prevent new Payment Transactions from being created under a Payment Account, disable the associated Payment Product instead.