How to use enriched data to increase approval rates and reduce false declines, boosting your sales by helping Klarna make smarter decisions. When your transactions are enriched with complete purchase and customer details, you help Klarna approve more shoppers — raising your acceptance rate and delivering a smoother checkout that converts.
How to use enriched transaction data to increase Klarna approvals and reduce false declines
This guide explains how Partners can improve approval rates and fraud protection by sending complete and structured Supplementary Purchase Data (SPD) in each transaction request.
Sharing detailed data helps Klarna make accurate real-time underwriting and fraud assessments, which leads to:
- Higher approval rates
- Fewer false declines caused by missing information
- Faster dispute resolution and improved customer satisfaction
More accurate data → smarter decisions → fewer false declines → higher conversion.
Klarna’s decisioning engine evaluates hundreds of signals in milliseconds for every transaction.
The quality of Partner-provided data directly influences Klarna’s ability to assess affordability, detect fraud, and resolve disputes efficiently.
| Component | What it does | How your data helps |
|---|---|---|
| Underwriting intelligence | Klarna’s AI-driven underwriting models combine behavioral insights, historical payment performance, and device data with SPD. This allows Klarna to make adaptive, real-time lending decisions — extending intelligent credit to the right customers at the right moment. | Detailed SPD fields such as line_items, category_path, and loyalty_tier help Klarna assess creditworthiness and intent accurately. This increases legitimate approvals and reduces unnecessary declines caused by missing or incomplete information. |
| Fraud and transaction risk management | As a licensed bank and full-stack network operator, Klarna manages its own fraud and transaction risk decisions. Its fraud engine analyzes behavioral patterns, device data, transaction context, and SPD in real time to flag anomalies before a payment completes. | Comprehensive SPD data — including product, delivery, and customer details — enhances fraud detection precision. This enables Klarna to distinguish genuine customers from fraudulent behavior early and reduce false positives that could block valid transactions. |
| Dispute risk monitoring and protection | Klarna also monitors non-fraud dispute risks such as shipping delays, product misrepresentation, or communication gaps. Automated processes resolve 93% of disputes before escalation, improving transparency and protecting Partner reputation. | Accurate fields such as line_items, shipping, and purchase_reference ensure aligned understanding across all parties, reducing investigation time and improving approval confidence. |
Supplementary Purchase Data (SPD) refers to additional information Partners send with each transaction to provide context about the payment, products, shipping, and customer.
High-quality SPD enables Klarna to deliver more accurate decisions, personalized experiences, and better fraud prevention while maintaining privacy and compliance.
SPD supports multiple use cases across industries and business models. Examples include:
- Post-purchase support: Improves customer experience by offering detailed order visibility in the Klarna App, streamlining disputes and returns, and reducing support requests.
- Improved approval rate: Rich data informs Klarna’s underwriting process, allowing for increased credit limits and higher acceptance rates.
- Enhanced Partner insights: Behavioral and historical purchase data helps Klarna develop tailored incentives and reactivation offers.
- Detailed fraud assessment: Granular product and shipping data help identify patterns and high-risk segments more effectively.
- Risk monitoring: SPD fields allow ongoing monitoring of exposure in high-risk sectors to support proactive controls.
Start with these high-impact actions to improve Klarna approval rates.
| ✅ Action | 💡 Why it matters |
|---|---|
Include detailed line_items | Helps Klarna approve more transactions by improving underwriting accuracy and fraud detection while streamlining disputes, returns, and in-app order visibility. |
| Provide complete shipping and billing details | Enables Klarna to verify identities, detect fraud, and assess delivery risk more accurately — improving approval rates and reducing false positives and support requests. |
Add purchase_reference and customer identifiers | Creates a consistent, customer-facing reference that improves traceability across Klarna touchpoints, simplifies disputes, and ensures smoother customer communication and post-purchase experiences. |
The following SPD fields support multiple use cases and add value across Partner integrations.
/v2/accounts/{partner_account_id}/payment/requests| Parameter | Required | Description |
|---|---|---|
Copied supplementary_purchase_data | No | Provide additional details about the transaction to help reduce fraud risk and enhance transparency. Include only the specific fields you wish to update within |
Copied -purchase_reference | No | Used for storing the customer-facing order number. It will be displayed to customers on the Klarna app and other communications. It will also be included in settlement reports for the purpose of reconciliation. If you are a direct merchant... Show more |
Copied -customer | No | This object provides information about the customer based on their previous interactions with the merchant. These data points may be used by Klarna to simplify sign-up and during fraud assessment, as well as for underwriting purposes to pro... Show more |
Copied --given_name | No | Provide the given name (first name) of the person associated with the transaction. Klarna uses this value for customer communication, fraud assessment, and delivery validation. Ensure the name is accurate and matches the individual's legal... Show more |
Copied --family_name | No | Provide the family name (last name) of the person associated with the transaction. Klarna uses this value for customer communication, fraud assessment, and delivery validation. Ensure the name is complete and correctly reflects the recipien... Show more |
Copied --email | No | E-mail address.
Regex ^(?=.{1,64}@.{1,255}$)(?:[a-zA-Z0-9!#$%&'+/=?^_ |
Copied --email_last_verified_at | No | Date of the most recent email verification done in ISO 8601 with timezone e.g. 2024-01-01T12:00:00Z |
Copied --phone | No | Provide the phone number in local format. Ensure the number includes at least one digit and only contains valid characters: +, digits, spaces, parentheses, periods, or hyphens. The system validates format based on the customer's country. Tr... Show more |
Copied --phone_last_verified_at | No | Date of the most recent phone verification done in ISO 8601 with timezone e.g. 2024-01-01T12:00:00Z |
Copied --address | No | Domicile address of the customer (billing address). Klarna will only use this as an indicator for fraud and to simplify sign-up. The address will not be used for underwriting and will not be persisted on created Payment Transactions. Klarna... Show more |
Copied ---street_address | No | Provide the first line of the street address, including the primary information, such as street name and number. Treat the value as an opaque string, do not validate or infer its structure. |
Copied ---street_address2 | No | Provide the second line of the street address if additional address details are needed. Klarna uses this field to capture supplementary information such as apartment, suite, or unit numbers. Treat the value as an opaque string, do not valid... Show more |
Copied ---postal_code | No | Provide the postal code formatted according to the rules of the specified country. Treat the postal code as an opaque string, do not parse or validate its format beyond country-specific requirements. |
Copied ---city | No | Provide the city or town name for the address indicated. Treat the city name as an opaque string, do not validate or infer its structure. |
Copied ---region | No | State/county/province/region formatted according to country. Mandatory for US and AU market. Validations according to ISO 3166-2 format, e.g. US-OH, US-NJ, AU-ACT, etc. |
Better data = better decisions.
Every enriched SPD field helps Klarna’s underwriting and fraud assessment models make faster and fairer decisions — leading to more approvals, fewer false declines, and higher Partner revenue.