Payment Products are Klarna's Payments offering, applied to a specific Partner. It contains all configuration and operational resources to enable a Partner Account to utilize Klarna Payments.
The Payment Product object represents Klarna’s Payment offering. It defines how a Partner can use Klarna's Payments, including which payment programs are enabled and pricing.
Payment Products are created and managed by Acquiring Partners on the onboarded Partner Accounts, and are used whenever Payments need to be processed or managed for a given Partner.
A unique identifier assigned by Klarna to this product. Used to reference the product in Klarna's systems and APIs.
Copied
type
PAYMENT
Yes
The type of product available to the merchant or partner.
Values:
PAYMENT: Klarna's payment services
Copied
payment_profile_id
Yes
The payment profile identifier. Previously known as Distribution Profile ID
Copied
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.
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
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
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.
Copied
state_reason
APPROVED
Yes
Additional state information when the Payment product state is ENABLED
The Payment Product lifecycle includes the following states:
flowchart LR
start((Start)):::teritiaryEntity --> E[ENABLED]
E -->|disabled by Acquirer| D[DISABLED]
E -->|disabled by Klarna| D
D -->|enabled by Acquirer| E
D -->|enabled by Partner| E
D -->|terminated by Klarna| T[TERMINATED]
T -->|re-activated by Klarna| E
Status
Definition
ENABLED
The product can process new payment requests.
DISABLED
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.
TERMINATED
The product is disabled 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. Any lifecycle change can be triggered by Klarna and will trigger the corresponding webhooks.
When Klarna triggers a state change for a Payment Product, a webhook is dispatched to the Acquiring Partner, which can be used to synchronize the states between Klarna and the Acquiring Partner systems.
Event name
When
Use cases
partner.account.change.created
The status of the payment product is changed by Klarna
Klarna disabled the payment product due to suspected fraud
Payment Products are exclusively created as part of the onboard call. The Acquiring Partner must declare the Payment Product as part of the products object, and a Payment Product must be created for all Partners being onboarded to Klarna Payments.
Payment Products can be listed using the listAccountPaymentProducts operation. All information connected to a payment product will be returned in the response. The read endpoint can be used after onboarding to obtain the list of Payment Accounts and to identify which Payment Profile was configured on a Payment Product.
There is no way to update the data points inside of a Payment Product. In case there is a change of status on the Acquiring Partner side, this change can be reflected at Klarna by using the disableAccountPaymentProductById or the enableAccountPaymentProductById operations and it should be applied as soon as there are changed on the Acquiring Partner systems.
It's not possible to completely delete a Payment Product. In order to disable new transactions from taking place into a Partner Account, the Payment Product should be instead disabled by using the disableAccountPaymentProductById operation, and should be called whenever the Partner is disabled on the Acquiring Partner systems.