# How to view Klarna Chargeback Loss Reason Codes

When managing [Klarna disputes](https://docs.stripe.com/payments/klarna/disputes), chargeback loss reason codes, such as **did\_not\_reply\_to\_dispute\_request**, help explain the rationale behind Klarna’s lost dispute decisions. A comprehensive list of reason codes is available in [our disputes documentation](https://docs.stripe.com/payments/klarna/disputes#klarna-chargeback-loss-reason-code).
Chargeback loss reason codes are a separate category from Dispute reason codes that occur during the inquiry process.
### What’s changing?
With the rollout of this update, businesses that use our Dashboard will be able to see the reason codes appear in the dashboard without any changes.
For businesses that use our API integration, we are surfacing a new field **payment\_method\_details.klarna.chargeback\_loss\_reason\_code** available in the [API](https://docs.stripe.com/api/disputes/object?api-version=2025-08-27.preview&rds=1#dispute_object-payment_method_details-klarna) for all new lost disputes and [**charge.dispute.closed**](https://docs.stripe.com/api/events/types?api-version=2025-08-27.preview&rds=1#event_types-charge.dispute.closed) webhook. This is only visible to users with the feature **dispute\_chargeback\_loss\_reason\_code.**
Businesses can benefit from these additional insights by improving how they operationally manage disputes internally, like ensuring compliance with Klarna’s shipping and return policies or timely responses to outstanding dispute requests.
### How can I confirm these changes were made on my account?
All businesses that use our Dashboard should automatically start seeing chargeback loss reason codes starting Oct 20th.
From the Disputes dashboard view on your [Stripe Dashboard](https://dashboard.stripe.com/), filter the status to **lost disputes**. Look for Klarna reason codes associated with these disputes.
All businesses that rely on our APIs should see the newly exposed field and a reason code supplied for chargebacks in **lost** status. You'll need to update to the latest API version to see this.