Payment Accounts are technical resources that represent a specific configuration a Merchant uses to operate. Payment transactions are always placed under a Payment Account.
A Payment Account defines how transactions are processed for a given Merchant. Each Payment Account represents a specific operational configuration for that Merchant, allowing the Acquiring Partner to associate an identifier (payment_account_reference) to this configuration for later use in Payment API operations.
A Payment Account sits under the Payment Product of a Merchant. It can be created during onboarding or later using the createPaymentAccountAPIoperation. At least one Payment Account is required to allow a Merchant to process transactions through Klarna's Payment Products.
A Payment Account is connected to the following resources:
- Payment Product: The Payment Account belongs to a Payment Product, the configuration for pricing and payment programs comes directly form the Payment Product, and cannot be set per Payment Account
- Partner Business Entity: Used to define which Partner Business Entity is responsible for transactions placed using this Payment Account
- Payment Acquiring Account: Used to determine the which legal entity and settlement configuration will be connected to transactions placed using this Payment Account.
- Store Group: Used to define which Branding is applied to transactions placed using this Payment Account.
/v2/accounts/{partner_account_id}/products/payment/{product_id}/payment-accounts/{payment_account_id}| Parameter | Required | Description |
|---|---|---|
Copied payment_account_reference | Yes | A unique string reference for the payment account, used by the partner to identify the payment account without relying on Klarna-generated IDs. |
Copied partner_business_entity_id | Yes | Klarna Resource Identifier (KRN) used to identify the partner business entity. |
Copied payment_acquiring_account_id | Yes | Unique account identifier assigned by Klarna to the Acquiring Account. |
Copied default_merchant_category_code | 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 |
Copied 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. |
The Payment Account lifecycle includes the following states:
| Status | Definition |
|---|---|
| The payment account can be used on the Payments API |
| The payment account cannot be used on the Payments API |
The status of Payment Accounts follow the status of the Payment Product, and cannot be manipulated via the API.
There are no webhooks connected to Payment Accounts
1. Local online store
If a Merchant sells only one type of product in under a single legal entity, only one Payment Account is needed to process transactions. The Payment Account will be connected to the only existing Partner Business Entity of the Merchant, the Merchant's MCC and their Store Group (which is connected to a brand)
2. Global online store
If a Merchant has a single global website but operates with multiple legal entities worldwide, then one Payment Account is needed per Partner Business Entity. All Payment Accounts will share the same Store Group and MCC, but each will have its own Partner Business Entity. Each Payment Account will need to have its own unique Payment Account Reference, in order to be identified on the Payments API operations.
3. Multi MCC company
If the company operates with multiple MCCs, let's say a company that is a supermarket but also has a gas station, then multiple Payment Accounts should be created. Each payment account will have its own specific MCC, and then when utilizing the Payments API, the specific Payment Account should be identifier on the API calls.
4. Multi Brand physical store company
If for example the Merchant operates a multi-brand conglomerate but still operates locally, with a single legal entity, and all brands share the same MCC, there are two ways to model it.
If you support brand and stores as a concept on your systems: Then only one Payment Account is needed. When utilizing the Payments API, different stores can be passed and will be used to override the default store group, and therefore the default brand set on the Payment Account.
If you have one Merchant identifier per brand: Then multiple Payment Accounts, one per brand can be created, in order to facilitate identification when utilizing the Payments API.
For more detailed examples that include API calls, refer to Klarna Docs - Modeling your Partner Account.