Manage Klarna Payment Products seamlessly by understanding their lifecycle stages, onboarding process, and enabling or disabling options for security and efficiency.
During onboarding, the Acquiring Partner grants the Partner access to the Klarna Payment Product which consists of:
- A Payment Profile, defining the pricing plan and payment program used by the Acquiring Partner to onboard a Partner.
- Payment Accounts defining the default Merchant Category Code, contractual relationship and settlement route between the Partner and the Acquiring Partner.
The Acquiring Partner will need to send the following parameters when declaring the products in the onboarding call to Klarna
| Parameter name | Description |
|---|---|
type | set to PAYMENT, the payment product enables Klarna Payment on the onboarded account |
payment_profile_id | The payment profile identifier. It defines the pricing plan and payment program used to onboard the partner. This identifier will be communicated by Klarna to the Acquiring Partner |
payment_accounts | Payment accounts connect various configurations, such as the Partner Business Entity, the Payment Acquiring Accounts Klarna Created for the Acquiring Partner, and the default Merchant Category Code for the Partner Business Entity:
|
Sample request - products submitted when onboarding a Partner
{
...
"products": [
{
"type": "PAYMENT",
"payment_profile_id": "krn:partner:global:account:payment-profile:206bbb83-[...]",
"payment_accounts": [
{
"payment_acquiring_account_id": "krn:partner:global:payment-acquiring-account:b44b[...]327502",
"payment_account_reference": "REF995847",Once the onboarding is successful, the Acquiring Partner can list the payment products which were created for the partner account using the List Payment Products API endpoint.
In addition to the parameters submitted in the onboarding request, Klarna will also return the following identifiers in the response to this API call:
| Parameter name | Description |
|---|---|
product_id | Unique identifier assigned by Klarna to a product configured on the partner account |
payment_account_id | Unique identifier assigned by Klarna to a payment account product |
state | The current state for the Payment Product. A Product can either be:
|
Sample response - List Payment Product
[
{
"product_id": "krn:partner:global:account:product:payment:ad71bc48-8a07-4919-a2c1-103dba3fc918",
"type": "PAYMENT",
"payment_profile_id": "krn:partner:global:account:payment-profile:206bbb83-[...]",
"payment_accounts": [
{
"payment_account_id": "krn:partner:global:payment-account:test:3440b9b7-7ca2-44a3-8f62-776caacdaa0b",
"status": "ENABLED",
"payment_acquiring_account_id": "krn:partner:global:payment-acquiring-account:b44b[...]327502",If an onboarded Partner Account has multiple Payment Accounts created, the Acquiring Partner will need to specify which payment account must be used when utilizing the Payment Product APIs for the corresponding partner_account_id.
Payment Products within the Partner Accounts follow a specific lifecycle, ensuring they are managed efficiently from inception to discontinuation. Familiarize yourself with these processes and actively use the available tools to optimize account actions and product handling.
The lifecycle diagram below provides detailed insight into these stages:
| Status | Definition |
|---|---|
ENABLED | The product is capable of processing new payment requests. |
DISABLED | The product cannot process new payment requests. It can be reverted if you are the one that disabled it. Other actions, such as post-purchase calls, may still succeed. |
TERMINATED | The payment product is fully disabled by Klarna for AML, fraud or risk reasons. |
Account termination can only be triggered by Klarna. The Acquiring Partner can however decide to disable or enable a payment product on a partner account using the following API endpoints:
Klarna may disable an account based on fraud or other unsavory behavior. More information on this process can be found in the Account lifecycle webhooks section.
Klarna relies on Acquiring Partners to safeguard the reliability and security of the Klarna Network. If a Partner account has only one Payment Product configured and it is disabled, the account will be unable to process transactions, but may continue to manage completed payments.
In case the Partner is suspended by the Acquiring Partner or instead decides to close their account, the Acquiring Partner must immediately disable all products configured on the account so Klarna has an accurate understanding of the Partner status. Updates to the product configuration should reflect changes applied in the Acquiring Partner systems, and should not be triggered more than once per account per second where possible. Any update or disabling of a product may take up to 10 minutes to be reflected towards customers.
Depending on the status of a Partner when their Klarna products are disabled, Klarna may continue to receive outreach from customers for months after the disablement action. Ensuring accurate and up to date account and product status towards Klarna will allow higher accuracy on adjudication of customer claims and other outreaches.
To disable the payment product on a given partner Account, the Acquiring Partner must use the Suspend a Payment Product endpoint and indicate the reason why the payment product is being disabled:
| Reason | Definition |
|---|---|
FRAUD | In case Klarna Product is being disabled due to fraud suspicion. More information on fraud and account security is available in Payments on restricted businesses. |
VOLUNTARY | In case the Klarna Productis being disabled due to voluntary cancellation of the account |
An open text details field is also available for more information about why the payment product is being disabled.
Additional enums will be added in a future release.
To re-enable a disabled payment—whether due to a misidentified fraud case or the Partner choosing to restore their integration, the Acquiring Partner must use the Enable a Payment Product endpoint.