Overview

dispute_data is a dynamic field required by Klarna. It must be submitted in key-value object format. The following are all available fields and their value constraints:

Parameters

Key	Value	Type / Rules
return_info	yes_will_make_changes_to_order, yes_but_not_accepted, return_not_received	Enum
tracking_id		≤ 1000 characters
shipping_date		date-time, yyyy-MM-dd format, ≤ 100 characters
shipping_carrier	postnord, bring, dhl, ups, db_schenker, posten, bring, gls, swipbox, posti, posti_pakettiautomaatit, smartpost, matkahuolto, deutsche_post, hermes, dpd, osterreichische_post, post_nl, kiala, fedex, usps, laser_ship, canpar, shipping_chimp, canpost, purolator, other, order_not_sent	Enum
received_payment	yes_will_make_changes_to_order, yes_refunded_consumer, not_received_payment	Enum
order_type	services, physical_goods, tickets_travel	Enum
service_already_used	yes, no	Enum
customer_has_been_contacted	yes, no	Enum
service_delivered_by	email, online, phone, physically, other	Enum
order_already_shipped	yes_in_full, yes_partially, no	Enum
delivery_address		string
shipment_country	at, de, es, it, fr, be, nl, ie, fi, gr, pt, se, no, dk, gb, us, ca, au, nz, pl, cz, ro, ch, mx, other	Enum
delivered_with_proof	yes, no	Enum
goods_returned	yes_in_full, yes_partially, no	Enum
last_digits_of_phone_for_delivery_notification		≥ 3 characters
order_is_cancellable	yes_will_cancel, no	Enum
order_is_refundable	yes_in_full, yes_partially, no	Enum
order_already_used	yes_in_full, yes_partially, no	Enum
is_travel_order	yes_will_cancel, no	Enum
is_shipping_company_contacted	yes_and_the_shipping_company_is_currently_attempting_to_recall_the_order, yes_and_the_order_was_delivered_back_to_us, yes_but_order_has_already_been_delivered, no_but_we_will_do_as_soon_as_possible, no_but_we_allow_klarna_to_reach_out_to_the_shipping_company_in_order_to_try_to_stop_the_order, order_was_shipped_without_a_tracking_id_and_cannot_be_recalled	Enum
is_order_shipped	yes_in_full, yes_partially, no_will_cancel_the_order	Enum
shipment	Processed internally by the system, no merchant input required	—
list_of_shipments	Processed internally by the system, no merchant input required	—
proof_of_delivery	Processed internally by the system, no merchant input required	—
capture_id	Processed internally by the system, no merchant input required	—

Dispute Evidence Examples

{
  "dispute_evidence": [
    {
      "evidence_code": "47",
      "evidence_description": "The Order is still on the way, Please wait patiently",
      "evidence_optional": false,
      "evidence_example": "Not listed above. Additional documentation substantiating the case",
      "evidence_submitted": "xxxxx xxxx xxxxxx xxxxxxxxx",
      "evidence_file": "222"
    },
    {
      "evidence_code": "44",
      "evidence_description": "The order has been shipped, please see the following detailed information.",
      "evidence_optional": true,
      "evidence_example": "The detail information of the order: 1. Tracking ID is 1234567; 2. The shipping company used was xxxxx; ...",
      "evidence_submitted": "",
      "evidence_file": ""
    },
    {
      "evidence_code": "19",
      "evidence_description": "Merchandise was Delivered.",
      "evidence_optional": false,
      "evidence_example": "The service was rendered/merchandise was delivered: This order was processed correctly. ...",
      "evidence_submitted": "xxxxx xxxx xxxxxx xxxxxxxxx",
      "evidence_file": "456"
    }
  ]
}

Complete dispute_data Example

{
  "return_info": "yes_will_make_changes_to_order",
  "customer_has_been_contacted": "yes",
  "delivered_with_proof": "yes",
  "delivery_address": "xxxxxxx",
  "goods_returned": "yes_in_full",
  "is_order_shipped": "yes_in_full"
}

References Klarna Disputes API Official Documentation.