CHcheckout
Issuing disputes

Amend an Issuing dispute

<span style="font-size: 12px; font-weight: 500; color: rgb(0, 0, 0); background-color: rgb(255, 176, 97); border-radius: 4px; padding: 2px 6px" >Beta</span><p></p> Amend an Issuing dispute that has been blocked from proceeding. This endpoint is used when the dispute's submission could not go through — either because the DR team requested changes before sending to the card scheme, or because the card scheme returned the submission for a fixable reason (in which case the DR team reviews the rejection and instructs the consumer via action_details).

This endpoint is only applicable when status is action_required and the status_reason is one of chargeback_change_requested, chargeback_evidence_invalid_or_insufficient, escalation_change_requested,prearbitration_evidence_invalid_or_insufficient. The _links.amend link in the GET response is present whenever an amendment is required.

Check action_details.instructions in GET /issuing/disputes/{id} for the specific changes required before calling this endpoint.

Chargeback stage (status_reason: chargeback_change_requested, chargeback_evidence_invalid_or_insufficient)

Address changes required before the chargeback can proceed. This covers two scenarios:

  • issuing rejection: The Disputes Resolution team reviews the submission and rejects providing corrective instructions via action_details.

  • Scheme rejection: The card scheme returned the chargeback for a fixable reason.

Escalation stage (status_reason: escalation_change_requested, prearbitration_evidence_invalid_or_insufficient)

Address changes required before the escalation (pre-arbitration or arbitration) can proceed. The same two scenarios apply as at the chargeback stage. reason_change_justification is required when changing the reason at this stage.

post/issuing/disputes/{disputeId}/amend

Request

Path parameters

disputeIdstring required

The unique identifier for the Issuing dispute.

Example:idsp_fa6psq242dcd6fdn5gifcq1491

Headers

Cko-Idempotency-Keystring required

An idempotency key for safely retrying requests.

Request body

reasonstring

The updated four-digit scheme-specific reason code. If a value is not provided, the existing reason code is retained.

amountnumber

The updated disputed amount, in the minor unit of the transaction currency. If not provided, the existing amount is retained.

reason_change_justificationstring

Explains the justification for the reason change. This is shared with the Dispute Resolution review team and may be submitted to the card scheme. This field is required if you change the reason at the escalation stage.

Allowed characters are:

  • Letters
  • Numbers
  • Spaces
  • The following special characters: ~!@#$%^&*()_+{}|:"<>?,./;'[]-=.
action_responsestring

Free-form text that you can use to explain your choices, provide additional context, or ask questions about the requested changes.

Example request

{
  "reason": "4807",
  "amount": 1500,
  "evidence": [
    {
      "name": "evidence.pdf",
      "description": "Goods were not received."
    }
  ],
  "fraud_details": {
    "fraud_type": "card_not_present_fraud",
    "description": "Cardholder confirmed they made no online purchases on this date."
  },
  "reason_change_justification": "New evidence confirms this was an unauthorized transaction, making reason 4837 more appropriate.",
  "action_response": "Updated reason as requested. The cardholder confirmed the goods were never delivered."
}

Response

Your corrections were accepted; the dispute continues processing.

idstring

The unique identifier for the Issuing dispute.

reasonstring

The four-digit scheme-specific reason code you provide for the chargeback.

status'created' | 'canceled' | 'processing' | 'action_required' | 'won' | 'lost'

The dispute status as returned to the client.

status_reason'' | 'expired' | 'chargeback_pending' | 'chargeback_change_requested' | 'chargeback_evidence_invalid_or_insufficient' | 'chargeback_processed' | 'chargeback_rejected' | 'chargeback_reversal_pending' | 'chargeback_reversed' | 'chargeback_response_accepted' | 'prearbitration_pending' | 'escalation_change_requested' | 'prearbitration_evidence_invalid_or_insufficient' | 'prearbitration_processed' | 'prearbitration_rejected' | 'prearbitration_reversal_pending' | 'prearbitration_reversed' | 'prearbitration_response_accepted' | 'arbitration_pending' | 'arbitration_processed' | 'presentment_reversed'

The status reason as returned to the client. An empty string indicates no status reason currently applies.

transaction_idstring

The transaction's unique identifier.

presentment_message_idstring

The message's unique Checkout.com identifier.

created_onstring date-time

The date and time when the dispute was created, in UTC. <br/>Format – ISO 8601 code <br/>Example – 2025-01-31T10:20:30.456

modified_onstring date-time

The date and time when the dispute was last modified, in UTC. <br/>Format – ISO 8601 code <br/>Example – 2025-01-31T10:20:30.456

Example response

{
  "id": "idsp_fa6psq242dcd6fdn5gifcq1491",
  "reason": "4802",
  "disputed_amount": {
    "amount": 100,
    "currency": "USD"
  },
  "status": "processing",
  "status_reason": "chargeback_processed",
  "transaction_id": "trx_aayhhfwbdyxwcaeyhhfwbd4xga",
  "presentment_message_id": "msg_fa6psq242dcd6fdn5gifcq1491",
  "merchant": {
    "id": "(*)123456789",
    "name": "Software Company",
    "city": "Paris",
    "country_code": "FR",
    "category_code": "5331",
    "evidence": [
      "file_6lbss42ezvoufcb2beo76rvwly"
    ]
  },
  "chargeback": {
    "submitted_on": "2025-09-10T10:11:12.0000000+00:00",
    "reason": "4802",
    "amount": {
      "amount": 100,
      "currency": "USD"
    },
    "evidence": [
      {
        "file_id": "file_6lbss42ezvoufcb2beo76rvwly",
        "description": "Goods were not received."
      }
    ]
  },
  "representment": {
    "amount": {
      "amount": 100,
      "currency": "USD"
    },
    "evidence": [
      {
        "file_id": "file_6lbss42ezvoufcb2beo76rvwly",
        "description": "Goods were not received."
      }
    ]
  },
  "pre_arbitration": {
    "submitted_on": "2025-09-10T10:11:12.0000000+00:00",
    "evidence": [
      {
        "file_id": "file_6lbss42ezvoufcb2beo76rvwly",
        "description": "Goods were not received."
      }
    ],
    "amount": {
      "amount": 100,
      "currency": "USD"
    },
    "reason_change": {
      "reason": "4807"
    },
    "merchant_evidence": [
      {
        "file_id": "file_6lbss42ezvoufcb2beo76rvwly",
        "description": "Goods were not received."
      }
    ]
  },
  "arbitration": {
    "submitted_on": "2025-09-10T10:11:12.0000000+00:00",
    "amount": {
      "amount": 100,
      "currency": "USD"
    },
    "decided_on": "2025-01-31T10:20:30.0000000+00:00"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.