Payment Accounts
Payment Accounts represent a specific configuration that a Partner uses to process Payment Transactions in the Klarna Network.
24 min read
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.
operation. At least one Payment Account is required to allow a Partner to process transactions through Klarna’s Payment Products.Relationships & Dependencies
graph
%% Partner objects
PA(Partner Account
Partner)
PAY_PRO(Payment Product)
PA_BRANDS(Brands)
PA_STORE_GROUPS(Store Groups)
PA_PBE(Partner Business Entity)
PAY_PROFILE(Payment Profile)
PAY_ACC(Payment Account)
PA_MCC(Merchant Category Code)
%% Payments
TRANSACTION(Payment Transaction)
%% Acquiring Partner
PA_AP(Partner Account
Acquirer)
ACQ_PRO(Payment Acquiring Product)
%% Payment Acquiring Resources
ACQ_ACC(Payment Acquiring Account)
ACQ_ALE(Acquiring Legal Entity)
ACQ_SETTL(Settlement Configuration)
%% Partner relationships
PA_STORE_GROUPS -->|n..1| PA_BRANDS
%% Partner Payment relationships
PA -->|1..n| PAY_PRO
PAY_PRO -->|n..1| PAY_PROFILE
PAY_PRO -->|n..1| PAY_ACC
PAY_PROFILE -.->|defines configuration for| TRANSACTION
PAY_ACC -->|1..n| TRANSACTION
PAY_ACC -->|1| PA_MCC
PAY_ACC -->|default| PA_STORE_GROUPS
PAY_ACC -->|1| PA_PBE
%% Acquiring Partner
PA_AP -->|1| ACQ_PRO
ACQ_PRO -->|1..n| ACQ_ACC
ACQ_ACC -->|1..n| PAY_ACC
ACQ_ACC -->|n..1| ACQ_SETTL
ACQ_ACC -->|n..1| ACQ_ALE
ACQ_ALE -.->|counterparty for| PAY_ACC
class PAY_ACC primaryEntity
class PA teritiaryEntity
class TRANSACTION teritiaryEntity
- 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.
Resource Properties
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.
action and use it for new Payment Transactions.Lifecycle
A Payment Account’s lifecycle is managed internally by Klarna. It transitions between the following states:
flowchart LR
start((Start)):::teritiaryEntity -->|Creation| E[ENABLED]
E -->|Klarna disables| D[DISABLED]
D -->|Klarna enables| E
| Status | Definition |
|---|---|
ENABLED | The payment account can be used on the Payments API |
DISABLED | The payment account cannot be used on the Payments API |
Payment Account status reflects the state of the associated Payment Product and therefore cannot be changed directly through the API.
Webhooks
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.
Frequent Use Cases
Create a Payment Account
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.
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.Read Payment Accounts
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 as described in Resolve identifiers.
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_ and payment_ and need the payment_, use resolvePaymentAccountId as described in Resolve identifiers.Change a Payment Account configuration
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.
operation and start using the new Payment Account for subsequent Payment Transactions.Stop new Payment Transactions on a Payment Account
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.
Jump to section...