Payment Profiles connect payment configuration details, such as pricing and product availability, to payment products, allowing one configuration to be shared across multiple partners.
A Payment Profile connects a Payment Product to a Price Plan and a Payment Program Plan. Klarna creates and manages these profiles, which are shared with Acquiring Partners together with API credentials. Payment Profiles enable multiple Partners under the same Acquiring Partner to share a unified payment configuration, simplifying management and reducing duplication.
A Payment Profile is connected to
- Payment Products:The payment profile may be used for one or many different Payment Products
- A Price Plan: defines the pricing structure applied to transactions.
- A Payment Program Plan: defines which Klarna Payment Programs the consumer will interact with.
/v2/distribution/products/payment/profiles| Parameter | Required | Description |
|---|---|---|
Copied payment_profile_id | Yes | ID assigned to the payment product at onboarding, outlining all configurations such as price plans and payment program plans. |
Copied price_plan_id | Yes | The identifier assigned to the price plan |
There is no specific lifecycle associated with a Payment Profile because it is a static configuration object managed entirely by Klarna.
No webhook or event notifications are connected to this resource.
Payment Profiles are primarily used during onboarding. When onboarding a new Merchant, the Merchant's Payment Product must be connected to a specific Payment Profile. This connection determines the Price Plan and Payment Program used for that Merchant's transactions.
In order to know the list of Payment Profiles available and their configuration, the listPaymentDistributionProfilesAPIoperation can be executed, returning the following data:
[
{
"payment_profile_id": "krn:partner:global:account:distribution-profile:206bbb83-9b6e-46fa-940d-337153c04a58",
"price_plan_id": "krn:partner:global:payment:price-plan:171080e7-2637-4675-a224-ec032723ebdf",
"payment_program_plan_id": "krn:network:global:all:payment:payment-program-plan:33deb549-aa35-4102-b9ec-56c527386111"
}
]
Which means only one Payment Profile is available to use, with the ID krn:partner:global:account:distribution-profile:206bbb83-9b6e-46fa-940d-337153c04a58.
For example, the following request can be used to onboard a merchant using the onboardAPIAPI operation:
{
"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"
},
"products": [Which will in turn make that any transaction placed for this specific merchant uses the Price Plan and Payment Program defined on the Payment Profile.