Payment Products are Klarna's Payments offering applied to a specific Partner. A Payment Product contains the configuration and operational resources that allow a Partner Account to use Klarna Payments.
The Payment Product object represents Klarna’s Payments offering for a specific Partner Account. It defines how a Partner can use Klarna Payments, including which payment programs are enabled and how pricing is applied.
Payment Products are created and managed by Acquiring Partners on onboarded Partner Accounts. A Payment Product is used whenever payments need to be processed or managed for a given Partner, and is required for the Partner to accept Klarna Payments.
Relationships & Dependencies
- Partner Account - A Partner Product belongs to a Partner Account, representing a company that is utilizing Klarna Payments to sell goods to consumers.
- Payment Profile – Defines the pricing and payment program configuration applied to transactions placed on this Payment Product.
- Payment Account(s) – Represents Partner-specific configuration, including Merchant Category Codes (MCCs), brands, and legal entities.
- Payment Program Enablements – Enables non-standard payment programs, such as Financing 0% APR, on this Payment Product.
Resource Properties
/v2/accounts/{partner_account_id}/products/payment| Parameter | Required | Description |
|---|---|---|
state | Yes | The current state for the Payment Product |
product_id | Yes | A unique identifier assigned by Klarna to this product. Used to reference the product in Klarna's systems and APIs. |
type | Yes | The type of product available to the merchant or partner. Values:
|
payment_profile_id | Yes | The payment profile identifier. Previously known as Distribution Profile ID |
payment_accounts | Yes | List of Payment Accounts. Payment accounts connect a set of configuration data points to an integrator-defined reference that can be used to operate Klarna's payment products. |
-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. |
-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 | 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. |
state_reason | Yes | Additional state information when the Payment product state is |
Lifecycle
The Payment Product lifecycle includes the following states:
| Status | Definition |
|---|---|
| The product can process new payment requests. |
| The product cannot process new payment requests but can be re-enabled by the Acquiring Partner. Post-purchase actions such as dispute management may still function. |
| The product is terminated by Klarna due to AML, fraud, or risk concerns. |
The Acquiring Partner can enable or disable a Payment Product based on operational or compliance needs using the corresponding API calls. When Klarna changes the lifecycle state of a Payment Product, Klarna triggers the corresponding webhook so the Acquiring Partner can keep its internal systems synchronized.
Webhooks
When Klarna triggers a state change for a Payment Product, a webhook is dispatched to the Acquiring Partner. This webhook can be used to synchronize the Payment Product state between Klarna and the Acquiring Partner systems.
| Event name | When | Use cases |
|---|---|---|
| The status of the payment product is changed by Klarna | Klarna disabled the payment product due to suspected fraud |
Example webhook payload
{
"metadata": {
"event_type": "partner.account.change.created",
"event_id": "baddd96c-c753-4864-a164-e3f9698fe703",
"event_version": "v1",
"occurred_at": "2024-02-01T12:00:00Z",
"subject_account_id": "krn:partner:account:live:2AIMNWR6IYZVD",
"recipient_account_id": "krn:partner:account:live:2AIMNWR6IYZVD",
"product_instance_id": "krn:partner:product:payment:0842e683-97d5-462d-99a9-c8e450deb98f",
"webhook_id": "krn:partner:global:notification:webhook:e708ffdf-3ae3-4e39-831b-c7affd12f897",
"live": true
},Frequent Use Cases
Create a Payment Product
Payment Products are created as part of the onboard operation. The Acquiring Partner must declare one Payment Product inside the products object to allow a Partner to use Klarna Payments.
There is no need to add subsequent products to a Partner Account, therefore there is no API operation to create new Payment Products.
Read a Payment Product
Payment Products can be listed using the listAccountPaymentProducts operation. The response returns the Payment Product configured on the Partner Account, including linked Payment Accounts and the Payment Profile configured product. Use this operation after onboarding to:
- Identify which Payment Accounts and Payment Profile are configured for each Payment Product.
- Obtain the current status of the product
- List the Payment Accounts connected to this product.
Update a Payment Product
There is no operation to update individual data fields inside a Payment Product. To reflect a change of status on the Acquiring Partner side, update the Payment Product state at Klarna by calling:
disableAccountPaymentProductById– when the Payment Product should no longer accept new transactions.enableAccountPaymentProductById– when the Payment Product should start accepting new transactions again.
Call these operations as soon as the corresponding state changes in the Acquiring Partner systems to keep Klarna and the Partner aligned.
Delete a Payment Product
You cannot delete a Payment Product. To prevent new transactions from being processed on a Partner Account, disable the Payment Product by using the disableAccountPaymentProductById operation whenever the Partner is disabled in the Acquiring Partner systems.