Payment Profiles
Payment Profiles connect payment configuration details, such as pricing and product availability, to Payment Products. A single Payment Profile configuration can be shared across multiple Partners under the same Acquiring Partner.
A Payment Profile connects a Payment Product to a Price Plan and a Payment Program Plan. Klarna creates and manages Payment Profiles and shares them with Acquiring Partners together with API credentials.
By referencing a Payment Profile, multiple Partners under the same Acquiring Partner can share a unified payment configuration. This reduces configuration duplication and ensures consistent pricing and Payment Programs across Payment Products.
Relationships & Dependencies
graph
%% Partner objects
PA(Partner Account
Partner)
PAY_PRO(Payment Product)
PAY_PROFILE(Payment Profile)
PAY_PRICE(Payment Price Plan)
PAY_PROGRAM(Payment Program Plan)
PAY_ACC(Payment Account)
%% Payments
TRANSACTION(Payment Transaction)
%% Acquiring Partner
PA_AP(Partner Account
Acquirer)
ACQ_PRO(Payment Acquiring Product)
%% Partner Payment relationships
PA -->|1| PAY_PRO
PAY_PRO -->|n..1| PAY_PROFILE
PAY_PRO -->|n..1| PAY_ACC
PAY_ACC -->|1..n| TRANSACTION
PAY_PROFILE -.->|defines configuration for| TRANSACTION
PAY_PROFILE -->|n..1| PAY_PRICE
PAY_PROFILE -->|n..1| PAY_PROGRAM
%% Acquiring Partner
PA_AP -->|1| ACQ_PRO
ACQ_PRO -->|1..n| PAY_PROFILE
class PAY_PROFILE primaryEntity
class PA tertiaryEntity
class TRANSACTION tertiaryEntity
- Payment Products: The Payment Profile is referenced by a Payment Product and defines how that product is configured for payments.
- A Price Plan: Defines the pricing structure (for example, fees and rates) applied to the Payment Transactions that use this Payment Profile.
- A Payment Program Plan: Defines which Klarna Payment Programs the customer will interact with when using this Payment Product.
Resource Properties
Lifecycle
A Payment Profile is a static configuration object managed entirely by Klarna.
- Clients do not create, update, or delete Payment Profiles directly.
- Klarna creates and maintains Payment Profiles and shares them with Acquiring Partners together with API credentials.
- Partners and their systems treat Payment Profiles as read-only references that they select and use when configuring Payment Products.
Webhooks
No webhook or event notifications are currently connected to this resource. Changes to Payment Profiles are managed by Klarna and are not delivered as events to client systems.
Example use cases
Use a Payment Profile during onboarding
When onboarding a Partner Payment Product, you must specify which Payment Profile the product will use. The selected Payment Profile determines:
- Which Price Plan is applied to the Payment Transactions for that Payment Product.
- Which Klarna Payment Programs customers will see when using that Payment Product.
For details on how to include the Payment Profile in the onboarding payload, see the Prepare the onboarding payload guide.
List available Payment Profiles
To retrieve all Payment Profiles available to an Acquiring Partner and their configuration, execute the listPaymentDistributionProfiles
operation. A typical response looks like:
operation. A typical response looks like:JSON
1
2
3
4
5
6
7
8
[
{
"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"
}
]
In this example, only one Payment Profile is available. Its identifier is:
krn:partner:global:account:distribution-profile:206bbb83-9b6e-46fa-940d-337153c04a58You can then:
- Use this
payment_profile_idwhen onboarding a Partner Payment Product. - Ensure that the corresponding Price Plan and Payment Program Plan are applied to all Payment Transactions processed for that Payment Product.
API & SDK references