--- title: "Escalate an Issuing dispute" method: POST path: "/issuing/disputes/{disputeId}/escalate" tags: ["Issuing disputes"] --- # Escalate an Issuing dispute `POST /issuing/disputes/{disputeId}/escalate` ## Request - Base URL: `https://{prefix}.api.sandbox.checkout.com` - URL: `https://{prefix}.api.sandbox.checkout.com/issuing/disputes/{disputeId}/escalate` - Auth: OAuth 2 - Client credentials - Token URL: `string` scopes: `issuing:disputes-write` - TypeScript: (a function with typed inputs; its response is checked against the schema) Beta

Escalate an [Issuing dispute](https://www.checkout.com/docs/card-issuing/manage-cardholder-transactions/manage-issuing-disputes) to pre-arbitration or arbitration. ## Path parameters - `disputeId` string, required: The unique identifier for the Issuing dispute. ## Headers - `Cko-Idempotency-Key` string, required ## Request body - EscalateDisputeRequest - `additional_evidence` IssuingDisputeEvidence[]: Your evidence for escalating the dispute, in line with the [card scheme's requirements](https://www.checkout.com/docs/card-issuing/manage-cardholder-transactions/manage-issuing-disputes#Evidence_file_requirements). If the request goes to arbitration, the card scheme ignores any evidence you provide at this stage using this request. - `name` string, required: The complete file name, including the extension. - `content` string, required: The base64-encoded string that represents a single JPG, PDF, TIFF, or ZIP file. ZIP files can contain multiple JPG, PDF, or TIFF files. - `description` string: A brief description of the evidence. - `amount` number: The updated disputed amount, in the [minor unit](https://www.checkout.com/docs/payments/accept-payments/format-the-payment-amount) of the representment currency. - `reason_change` IssuingDisputeReasonChange: The change to the dispute reason and your justification for changing it. - `reason` string, required: The updated four-digit scheme-specific [reason code](https://www.checkout.com/docs/developer-resources/codes/chargeback-codes) for the chargeback. - `justification` string, required: Your justification for changing the dispute reason. Allowed characters are: - Letters - Numbers - Spaces - The following special characters:
`~!@#$%^&*()_+{}|:"<>?,./;'[]-=`. - `fraud_details` IssuingDisputeFraudDetails: Fraud-related information required when the dispute reason code is fraud-related. - `fraud_type` 'card_lost' | 'card_stolen' | 'card_never_received' | 'fraudulent_account' | 'counterfeit_card' | 'account_takeover' | 'card_not_present_fraud' | 'merchant_misrepresentation' | 'cardholder_manipulation' | 'incorrect_processing' | 'other', required: The type of fraud the cardholder is asserting. This can be one of: - `card_lost`: The cardholder does not have the physical card and cannot explain how it was lost. - `card_stolen`: The cardholder does not have the physical card and provided an explanation as to how it was lost. For example, their wallet was stolen. - `card_never_received`: The card was issued and mailed but was not received by the cardholder. - `fraudulent_account`: The account was opened fraudulently using a stolen, fake, or synthetic identity. - `counterfeit_card`: The cardholder has their physical card but a duplicate or altered card was used in an unauthorized card-present transaction. - `account_takeover`: A fraudster gained control of the cardholder's account or credentials. For example, they may have changed the registered address, ordered a new card, or provisioned the card to a digital wallet. - `card_not_present_fraud`: The cardholder still has the card but the card details were used in an unauthorized card-not-present transaction. For example, it was used in an ecommerce transaction, or in a mail order/telephone order (MOTO) payment. - `merchant_misrepresentation`: The merchant deliberately misled the cardholder. For example, the goods provided were sub-standard, there were hidden charges, or the services advertised were fake. - `cardholder_manipulation`: The cardholder was tricked into authorizing the transaction themselves. For example, due to a scam, an impersonation, or authorized push payment (APP) fraud. - `incorrect_processing`: A security check failed and made fraudulent activity possible. For example, a card verification value (CVV) check was not performed, or the EMV cryptogram was not validated. - `other`: The confirmed fraud does not fit any of the other fraud type categories, or there were multiple fraud types applicable to the same transaction. - `description` string: A description of the fraud circumstances, for internal reference. This is not forwarded to the scheme. - `justification` string, required: Justification for escalating the dispute. Allowed characters are: - Letters - Numbers - Spaces - The following special characters: `~!@#$%^&*()_+{}|:"<>?,./;'[]-=`. ## Response `202` Issuing dispute escalation requested successfully ## Other responses - `401`: Unauthorized Request - `404`: Issuing dispute not found - `409`: Issuing dispute cannot be escalated - `422`: Request missing required information --- [API](https://skmtc.dev/checkout/apis/checkout-com-api-reference.md) - [All operations](https://skmtc.dev/checkout/apis/checkout-com-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/checkout/apis/checkout-com-api-reference/revisions/0f1abdb1c3e9?raw)