Payment Accounts represent a specific configuration that a Partner uses to process Payment Transactions in the Klarna Network.
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.
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.
A unique string reference for the payment account, used by the partner to identify the payment account without relying on Klarna-generated IDs.
partner_business_entity_id
Yes
Klarna Resource Identifier (KRN) used to identify the partner business entity.
payment_acquiring_account_id
Yes
Unique account identifier assigned by Klarna to the Acquiring Account.
default_merchant_category_code
0742
Yes
The Merchant Category Code (MCC) is a four-digit number that is used to classify the type of goods or services
offered by a business.
[Read more here]( https://docs.klarna.com/klarna-network-distribution/manage-partners/onboard-and-manage-p...
Show more
default_store_group_id
Yes
A unique identifier assigned by Klarna to an existing store group. Used to reference the store group in Klarna's systems and APIs.
Here you can find all required parameters for this operation getPaymentAccounts
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.
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 currently no support for retrieving a single Payment Account by ID or by reference.
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.