---
title: "Merchant action"
method: POST
path: "/v1/disputes/{disputeId}/actions"
tags: ["Disputes"]
---

# Merchant action

`POST /v1/disputes/{disputeId}/actions`

Use this endpoint to perform actions like accept, challenge or offer on a dispute

## Path parameters

- `disputeId` string, required

## Headers

- `Request-Reference` string
- `Request-Idempotency-Key` string

## Request body

- MerchantActionRequest — Request body for merchant action
  - `type` 'ACCEPT' | 'CHALLENGE' | 'OFFER', required — Action that can be performed on the dispute
  - `resolution` string — The resolution chosen by the merchant for this action. Required if defined in the config for certain action types.
  - `message` string — Message text. Required if defined in the config for certain action types.
  - `amount` Amount
    - `value` integer, required
    - `currency` string, required

## Response `202`

Success with status as ACCEPT_PROCESSING, CHALLENGE_PROCESSING or OFFER_PROCESSING depending on the action

- MerchantActionResponse
  - `disputeId` string
  - `status` string

## Other responses

- `400` — Bad Request
- `404` — Not found
- `409` — Target event could not be reset due to a concurrent update.
- `500` — Internal Server Error

---

[API](https://skmtc.net/ppro/apis/payment-charges.md) · [All operations](https://skmtc.net/ppro/apis/payment-charges/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ppro/payment-charges/revisions/112e8bb4c815/schema)