Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
Overview
About Stripe payments
Upgrade your integration
Payments analytics
Online payments
OverviewFind your use caseManaged Payments
Use Payment Links
Build a checkout page
Build an advanced integration
Build an in-app integration
Payment methods
Add payment methods
    Overview
    Payment method integration options
    Manage default payment methods in the Dashboard
    Payment method types
    Cards
    Pay with Stripe balance
    Crypto
    Bank debits
    Bank redirects
    Bank transfers
    Credit transfers (Sources)
    Buy now, pay later
      Affirm
      Afterpay / Clearpay
      Alma
      Billie
      Capchase Pay
      Klarna
        Accept a payment
        Set up future payments
        Optimize conversion
        Comply with Klarna rules
        Respond to disputes
      Kriya
      Mondu
      Payment on Invoice
      Scalapay
      SeQura
      Sunbit
      Zip
    Real-time payments
    Vouchers
    Wallets
    Enable local payment methods by country
    Custom payment methods
Manage payment methods
Faster checkout with Link
Payment interfaces
Payment Links
Checkout
Web Elements
In-app Elements
Payment scenarios
Handle multiple currencies
Custom payment flows
Flexible acquiring
Orchestration
In-person payments
Terminal
Beyond payments
Incorporate your company
Crypto
Financial Connections
Climate
Understand fraud
Radar fraud protection
Manage disputes
Verify identities
HomePaymentsAdd payment methodsBuy now, pay laterKlarna

Respond to disputes

The lifecycle of Klarna disputes and how to respond to them.

Note

This guide is specific to Klarna payment disputes. Learn how card disputes work.

A dispute occurs when the Klarna customer files a complaint or return request for a specific order using the Klarna consumer app. Customers have up to 180 calendar days to file a dispute from the date of capture.

These complaints and return requests correspond to specific reason codes that Stripe shares back with you. When someone files a Klarna dispute, the process varies slightly by reason code, but typically follows a standard pattern.

Comparison to card disputes

There are a few key similarities and differences between how Klarna and card disputes work.

Card disputesKlarna disputes
Inquiry supportSelect card networks support inquiries, also known as a “retrieval” or “request for information”.All Klarna disputes, except for fraudulent disputes start as inquiries. Unlike cards, businesses aren’t expected to submit evidence at this stage, and are expected to resolve the issue directly with the customer.
Responding to disputesBusinesses can use the Stripe Dashboard or Disputes API to manage and respond to disputes.Same as cards.
Dispute feesThere are separate fees for receiving a dispute, in addition to countering a dispute. Dispute fees are assessed when the dispute is created and apply regardless of whether you ultimately win or lose the dispute.There is only a single fee for losing a dispute. Dispute fees are assessed when the dispute is created, but are reversed if you ultimately win the dispute.
Partial disputesPartial disputes are supported.Same as cards.
Credit not processed Stripe dispute categoryThis dispute category can refer to several card network reason codes, although the most common reason is when a customer has made a return and hasn’t yet received a refund.For Klarna, this dispute category refers to two distinct scenarios, although both reasons share the same reason code.
  • Return: The most common scenario where a customer requests to initiate a return using the Klarna app.
  • Credit not processed: The customer has already completed the return but hasn’t yet received a refund.

Inquiries

Inquiry disputes are an opportunity to resolve a customer’s issue before the dispute escalates to a chargeback and carries a fee. Stripe notifies you of an inquiry as soon as Klarna opens one. Inquiry creation is triggered by the customer taking action on the Klarna app, either by filing a complaint or requesting to return the purchase. When a customer files an inquiry, Klarna pauses any outstanding repayments from the customer until the dispute is resolved.

Almost all Klarna disputes begin as inquiry disputes, which have a 21 calendar day timeframe before they are escalated. Among the exceptions documented by Klarna are disputes raised because of fraudulent transactions, which escalate immediately. Klarna doesn’t accept evidence during this stage.

The intent of an inquiry is to give you early notice that the customer has an issue with the order so that you can proactively address the customer’s concern and potentially avoid chargeback disputes. During this stage, you can perform one of the following actions:

  • Contact your customer to understand the reason for raising the dispute, and try to mutually find a resolution before the inquiry escalates to a chargeback. Customers have the ability to withdraw their inquiry using the Klarna app.
  • Accept the dispute by issuing a refund of the full disputed amount. Refunding during the inquiry dispute period avoids a dispute fee.
  • Allow the dispute to escalate. If you ignore the inquiry or are unable to resolve the issue, it will automatically escalate to a chargeback. At this point you can submit evidence to challenge the dispute.

Responding to return inquiries

Customers paying with Klarna use inquiry disputes as a means to pause repayments while they’re in the process of completing a return for physical goods purchases. Klarna allows customers to file an inquiry and pause repayments before they’ve completed their return, but ask customers to provide proof of return, such as the return tracking ID.

Stripe only notifies you of a return inquiry when a customer has provided the necessary information. However, if you’re using Stripe’s Disputes API, Stripe notifies you as soon as a customer files an inquiry, even if the return hasn’t yet been completed.

If you receive an inquiry dispute with the Return Klarna dispute code, make sure to handle these appropriately:

  • Click into the dispute object view in your Stripe Dashboard for details on the return dispute.
  • Select Issuer evidence. This provides the return tracking details.
  • After you’ve verified that the return is in transit or has already been returned to you, process a refund within the 21-day inquiry period.

Chargeback disputes

If an inquiry dispute remains unresolved after the 21 calendar day timeframe, the dispute automatically escalates to a chargeback dispute. At this point, Stripe withholds the disputed funds and the associated dispute fee from your account for this payment until the dispute is resolved.

During the chargeback dispute stage, you can counter disputes by submitting evidence to Klarna, either in the Dashboard or with the API. You need to submit evidence by the deadline displayed in the Dashboard or evidence_due_by for API users.

If you counter the dispute by submitting evidence, Klarna evaluates your response to decide the outcome.

  • If you win the dispute, Stripe releases the withheld funds to your account, including the associated dispute fee.
  • If you lose the dispute, Stripe debits the withheld funds, including the associated dispute fee. Klarna then returns the disputed amount to the customer.

Submit evidence for chargeback disputes

You can only submit evidence after a dispute gets escalated to a chargeback. Use the Dashboard or the API to submit evidence against a chargeback dispute. If you fail to submit evidence, Klarna rules the dispute in favor of the customer.

Businesses have 12 calendar days from chargeback escalation to provide evidence, except for fraud disputes, which have a 5 day timeframe.

It’s only possible to submit a single round of evidence for Klarna disputes. Therefore, it’s important to ensure that all necessary evidence is gathered and submitted during the evidence submission window. Below we provide recommended guidelines based on dispute reasons below. For additional best practices, refer to Klarna’s guide.

Stripe dispute reasonKlarna dispute reasonSuggested evidence fieldsDescription
Product not receivedGoods not received
  • shipping_tracking_number
  • shipping_carrier
  • shipping_date
  • customer_communication
  • All shipping related information
Credit not processedReturn
  • uncategorized_file
  • refund_refusal_explanation
DuplicateAlready paid
  • uncategorized_file
  • customer_communication
  • Supporting evidence for your case in an attachment
  • Any communication with the customer
FraudulentUnauthorized
  • customer_communication
  • shipping_tracking_number
  • shipping_address
  • shipping_documentation
  • All shipping related information
  • Communication with the customer
General
  • Incorrect invoice
  • High risk order
  • shipping_documentation
Product unacceptableFaulty goods
  • customer_communication

Use the Dashboard or the API to submit evidence against a chargeback dispute. You can’t submit evidence for inquiry disputes.

  1. Navigate to the Disputes Dashboard, and click the Needs Response tab.
  2. Click the disputed payment. If you want to counter the dispute, click Counter dispute.
  3. Select the reason why you should win the dispute, and click Next.
  4. Enter and attach all the applicable supporting evidence. The recommended label indicates the best documents for the type of dispute.
  5. After entering all the evidence, verify the information is correct by selecting the checkbox.
  6. Click Submit Evidence.

Submit evidence on time

If you fail to submit evidence, Klarna rules the dispute in favor of the customer. See Respond to disputes for more information.

Alternatively, you can accept a dispute loss from the Disputes Dashboard by clicking Accept Dispute.

Guidelines

Follow these guidelines to submit the most relevant evidence for both Dashboard and API disputes.

Create test disputes

You can simulate dispute creation by creating a transaction in a sandbox using the following email addresses and phone numbers in the given Klarna checkout region. A dispute automatically opens on the transaction. You can submit evidence on the dispute, but you can’t simulate the final dispute outcome in a testing environment.

Below, we have specially selected test data for the currently supported customer countries.

Stripe dispute reasonKlarna dispute reasonEmailPhone number
Credit not processedReturncustomer+disputed-return@email.au+61491574118
Product not receivedGoods not receivedcustomer+disputed-goods_not_received@email.au+61491574632
DuplicateAlready paidcustomer+disputed-already_paid@email.au+61491575254
Product unacceptableFaulty goodscustomer+disputed-faulty_goods@email.au+61491575789
GeneralIncorrect invoicecustomer+disputed-incorrect_invoice@email.au+61491575789
GeneralHigh risk ordercustomer+disputed-high_risk_order@email.au+61491576801
FraudulentUnauthorized purchasecustomer+disputed-unauthorized_purchase@email.au+61491577426

Dispute API

A Dispute object contains a dispute type and Klarna dispute reason. These parameters are useful for countering a dispute.

Type

The Status parameter indicates the dispute type. The following table explains the dispute status and the state of the dispute.

StatusDispute typeDescription
warning_needs_responseInquiryThe inquiry is open and the business can issue a refund.
warning_closedInquiryThe inquiry is closed.
needs_responseChargebackThe chargeback is open and the business can submit evidence.
under_reviewChargebackThe chargeback is open and the evidence is submitted to Klarna.
lostChargebackThe chargeback is closed and the business lost the dispute.
wonChargebackThe Chargeback is closed and the business won the dispute.

Klarna reason

The Klarna reason is mapped to Stripe dispute reason and displayed in the Dashboard as Network Reason Code.

The Stripe reason is available in the Dispute object as reason and the Klarna reason is available in payment_method_details.klarna.reason_code. The data is available in the API and webhook.

See also

  • Respond to disputes
  • Dispute categories
  • Dispute evidence object
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Join our early access program.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc