API リクエストにバージョンヘッダー 2025-11-17.preview またはそれ以降のプレビューバージョンヘッダーを含めることで、このパブリックプレビュー機能を使用できます。
Supplementary purchase data adds context to a transaction to improve payment outcomes and customer support. Use it to send industry-specific details for verticals such as events, transportation, marketplaces, and insurance.
When to use supplementary purchase data
Use supplementary purchase data if you operate in a supported vertical and want to improve your payment outcomes with Klarna.
The supplementary data shared with Klarna supports these use cases:
Post-purchase transparency: Provide detailed transaction breakdowns for your customers in the Klarna app, streamline disputes and returns, and reduce support requests.
Higher acceptance rates: Historical data informs underwriting and can increase approvals for legitimate transactions.
Enhanced fraud assessment: Detailed transaction insights support more effective fraud investigations, especially in high-risk segments.
Risk exposure monitoring: Transaction data supports continuous monitoring and timely mitigation.
Enhanced solution offerings: Based on historical behavior, Klarna can develop enhanced solutions for incentives and actions that benefit you and your customers.
Limitations
Keep these limits in mind:
No fee changes: Passing supplementary purchase data doesn’t impact the fees you pay for Klarna transactions. Your pricing remains the same whether or not you provide this data.
No validation feedback: Stripe and Klarna accept well-formed supplementary purchase data but don’t provide feedback on whether the specific data you send qualifies for improved outcomes.
Measure impact
Track your Klarna authorization rates over time in your payment analytics. After you implement supplementary purchase data, you might see more successful authorizations, though the impact varies based on your transaction patterns and the data you provide.
Test that your integration works correctly for your customers. Simulate API calls in a Stripe Sandbox with a sandbox key. Attach a payment method using the update method prior to confirming. For additional information, see Testing.