The Payment Acquiring Product represents Klarna’s acquiring offering used by an Acquiring Partner. It links directly to a Partner Account, allowing the Acquirer to onboard, manage, and operate its Partners in the Klarna Payment Network.

The Payment Acquiring Product is created and maintained internally by Klarna as part of the Partner’s configuration. It does not expose its own public API schema.

• Partner Account: The Payment Acquiring Product always connects to a Partner Account. This Partner Account represents the Acquiring Partner operating within Klarna.
• Payment Acquiring Account: Each Payment Acquiring Account defines a specific acquiring configuration for the Acquiring Partner. Multiple Payment Acquiring Accounts can link to the same Payment Acquiring Product.
• Payment Profile: An Acquiring Partner has a list of Payment Profiles available to them, connected to their Payment Acquiring Product. These profiles can be used to onboard Partners.

The Payment Acquiring Product does not expose any resource properties in public APIs. It acts as a logical container that connects the Partner Account to its associated Payment Acquiring Accounts inside Klarna’s domain model.

There are no public API operations available for reading, creating, or managing Payment Acquiring Products. This resource is defined and managed internally by Klarna as part of Acquiring Partner configuration.

The Payment Acquiring Product is created when Klarna sets up an Acquiring Partner’s Partner Account and acquiring configuration. It does not have its own public state machine, lifecycle events, or dedicated webhooks.

Any changes to the Payment Acquiring Product are handled by Klarna as part of Partner configuration and are reflected through the underlying Partner Account and Payment Acquiring Accounts, rather than through direct updates to this resource via API.

You will typically encounter the Payment Acquiring Product in documentation, architecture diagrams, or configuration discussions rather than in direct API calls. Common scenarios include:

• Understanding the hierarchy of acquiring resources as: Partner Account → Payment Acquiring Product → Payment Acquiring Accounts.
• Mapping Klarna’s model to your own account or product structure while knowing that only Partner Accounts and Payment Acquiring Accounts are addressable via public APIs.
• Interpreting references to “Payment Acquiring Product” as the bridge between a Partner Account and the individual acquiring configurations represented by Payment Acquiring Accounts.