Streamline partner onboarding with Klarna by using the Onboarding API, ensuring accurate data submission, compliance, and seamless access to Klarna Payment Services.
To start offering Klarna Payment Services to their Partners, Acquiring Partners must first onboard them to Klarna.
During this process, it's crucial to define the appropriate structure based on the Partner's business model, as detailed in the in Determine account structure.
To onboard a Partner, the Acquiring Partner must use the Onboard API endpoint and specify the following parameters:
Parameter | Description |
---|---|
Reference for the Acquiring Partner in relation to the Partner being onboarded. | |
The name of the Partner Account, business name or similar. | |
The contact details of the Partner Account owner. | |
Detailed information about the Partner Business Entities to which the Acquiring Partner is offer Klarna Payment Product. Fore more information, please refer to the Partner Business Entities section | |
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. Fore more information, please refer to the Payment Products section | |
branding data from the Partner which apply to the store groups defined. Fore more information, please refer to the Partner Stores and Brands section | |
Stores groups contain the details of the website, mobile app or physical store where Klarna products are going to be made available. Fore more information, please refer to the Partner Stores and Brands section |
Selecting a payment product will activate all related payment services in all markets where Klarna is available, allowing a Partner to offer Klarna as a payment method.
It is essential Acquiring Partners provide all relevant and available Partner information as specified in the data transfer and cooperation agreement with Klarna.
Sharing correct and accurate data allows Klarna to perform a better assessment of the risk associated with your Partners, enabling a safer experience to all parties.
It's also important to have in mind the following about the onboarding properties:
Sample request
{
"partner_account_reference": "M123786123412",
"partner_account_name": "John Doe Stakehouse",
"partner_account_contact": {
"given_name": "John",
"family_name": "Doe",
"email": "john.doe@example.com",
"phone": "+18445527621"
},
"partner_business_entities": [
When a Partner is successfully onboarded with Klarna, Klarna will create an account for the Partner and return an partner_account_id
in the onboarding response. At this point, they are ready to begin transacting in all markets where Klarna is available.
Remember to store the partner_account_id
associated with the Partner as it is a required parameter for the integration of the Partner Product API.
The combination of acquiring_account_id
and payment_account_reference
may also be used later for the integration of the Partner Product API, in cases where multiple Payment Accounts exist for the same Partner Account.
Other references, such as for Stores, Store Groups and similar, may also be relevant later on when integrating with other APIs, which emphasize the importance of setting the correct identifiers during onboarding
Sample response
{
"partner_account_id": "krn:partner:global:account:test:MABCDEFG",
"partner_account_reference": "M123786123412",
"partner_account_name": "John Doe Stakehouse",
"state": "PARTIALLY_OPERATIONAL",
"state_reason": "INITIAL_SETUP"
}
The example provided here is for illustrative purposes only. The parameters required for onboarding may vary based on your commercial agreement and the parameters available to you.
Once the onboarding is executed, the account is ready to transact, but might still be set up in Klarna systems, the details about this process is available on the Account Lifecycle Webhooks page.
During the onboarding, there are some data points and connections that are immutable and cannot be changed. Make sure the information provided is accurate:
Payment Account:
Payment Product:
Partner Legal Entity:
Integrating Klarna Payment Services requires accurate and complete Partner data to ensure seamless transaction processes and fraud prevention. This section covers the essential steps and protocols activated when discrepancies in Partner data are detected during the onboarding process.
Klarna's Partner management API performs real-time validations on all incoming data. In most of the cases when data fields are missing or incorrect, the system triggers an automated response outlining the specific issues. These validations cover critical information such as business details, tax IDs, and contact information.
Whenever incomplete or invalid data for a brand is submitted during the onboarding, Klarna will trigger a account brand data incomplete webhook to which you can subscribe to:
EVENT NAME | WHEN |
---|---|
| to receive notifications when the brand data submitted during account onboarding is invalid or incomplete |
The partner.account.brand.data-incomplete
webhook event will notify Partners when the brand data submitted during account onboarding is invalid and any invalid or incomplete brand will be removed, while valid brand information will be persisted.
While this webhook is informational and does not block onboarding, Klarna highly recommends that the invalid information is updated with corrected elements to ensure optimal brand representation.