Supplementary Purchase Data refers to additional data points that provide additional context related to a transaction to improve outcomes and customer experience. While these data points are technically optional, they are often required to enhance underwriting and fraud assessment, as well as to improve the customer's post-purchase experience.

This information supports different use cases and may include data associated to specific industries or business models such as airline, marketplaces, as well as data related to the transaction (line items, subscriptions and on demand transactions) or even custom data.

The supplementary data shared with Klarna will support multiple use cases and add value in different fronts such as:

• Enhance post purchase experience: Enhance customer’s post-purchase experience with detailed transaction breakdowns, streamlining disputes and returns, reducing support requests, and boosting affiliate revenue through upselling and repurchasing opportunities—all within the Klarna app.
• Acceptance Rate Improvement: Historical data informs underwriting processes, allowing for increased credit limits and improved acceptance rates.
• Enhancement of solution offering:  Based on historical behavior of the consumer with a brand, Klarna is able to develop enhanced solutions for incentives and to drive particular actions.
• Effective Fraud Case Investigation: Detailed transaction insights support thorough investigations, tailoring responses to unique characteristics in high-risk segments.
• Klarna’s Risk Exposure Monitoring: Data points facilitate ongoing monitoring of risk exposure in high-risk segments, ensuring timely identification and control of potential risks.
• Enhance underwriting and fraud assessment processes: enhance the underwriting and fraud assessment for Partners and Klarna can make better-informed decisions in assessing the risk of the transaction. Historical data informs underwriting processes, allowing for increased credit limits and improved acceptance rates.

The following table list the supplementary_purchase_data shared with Klarna will support multiple use cases and add value in different fronts such as:

Line items stand at the crossroads of Klarna's operations and are crucial in enhancing Klarna's fraud detection, underwriting capabilities, and customer experience. By breaking down transactions into individual units, they provide detailed insights that streamline dispute resolution and efficient interaction within the Klarna app, while reducing customer support errands.

The purchase_reference field is a required identifier used throughout the payment process to support various partner and customer-facing activities. This parameter should correspond to the Partners customer-facing order reference. Ensuring this parameter is both consistently applied and understandable to end consumers is helpful in minimizing errands and ensuring customer satisfaction. Below are some key use cases:

• Customer Service: It provides a clear, recognizable identifier that customers can use during disputes, inquiries, or interactions with customer support, improving the overall user experience.
  
  • In addition, Klarna leverages the purchase_reference in all touchpoints with the consumer, ensuring clear communication and understanding within the Klarna App, email communications, and push notifications regarding order status.
  
• Dispute Resolution: purchase_reference provides all involved parties with an aligned understanding of the order being discussed, reducing the chances for confusion or human error for both customers and customer service agents.
• Fallback Identifier: When other session identifiers are unavailable, the purchase_reference may act as a fallback to ensure continuity and traceability within the transaction.

Purchase reference plays a key role in supporting visibility and alignment between all parties, and drives increased customer satisfaction.

Acquiring Partners must map existing fields in their payment API with the fields defined in the supplementary_purchase_data object of the Payment Authorize API.

Sample Authorize Payment request with supplementary_purchase_data

{
  "currency": "EUR",
  "request_payment_transaction": {
    "amount": 2079,
    "payment_transaction_reference": "payment-transaction-reference-36ac766a-[...]"
  },
  "supplementary_purchase_data": {
    "purchase_reference": "merchant-purchase-reference-deafb375-6fe4-4856-8087-36d8296d1dc7",
    "line_items": [
      {