---
title: "Create dispute fee"
method: POST
path: "/v1/fee"
tags: ["Fees"]
---

# Create dispute fee

`POST /v1/fee`

A dispute fee, or *fee collection* in network terminology, is a way for an acquirer and issuer to exchange money outside the normal chargeback process. Typically, this means reversing a settled chargeback, but not always,

You can use this endpoint to create a dispute fee with or without a chargeback claim ID. You can create a dispute fee for a claim that already exists or, if it doesn't, you can pass the necessary authorization information to create it.

For more information, refer to [Dispute fees](https://developers.pismo.io/pismo-docs/docs/disputes-overview#dispute-fees) in the Disputes overview guide. This feature is only available for Mastercard and Elo.

This endpoint generates a [Dispute fee status created](https://developers.pismo.io/events/docs/disputes-dispute-fee-events-1) event.

**Note:** This endpoint takes an account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a <b>401 Unauthorized</b> message.

## Headers

- `Authorization` string, required

## Request body

- DisputeFee — Dispute fee object
  - `amount` number, double, required — Fee amount.
  - `card_id` integer, required — Enrolled card ID
  - `credit_sender` boolean, required — Credit the sender? Default is `false`.
  - `credit_receiver` boolean, required — Credit the receiver? Default is `false`.
  - `currency` string, required — ISO 4217 fee currency code.
  - `destination_member` string, required — Destination member for the fee collection. These values are known to the network and identify either the issuer or acquirer.
  - `fee_date` string, date, required — Date the fee was attached to the claim, format = yyyy-mm-dd.
  - `network_brand_type` 'Visa' | 'Mastercard' | 'Elo', required — Network brand
  - `reason_code` string, required — Collection reason code. These codes can be found in Mastercard's [Global Clearing Management System Reference Manual](https://pismoassets.pismo.io/pismo-docs/mc_gcms_rm.pdf) starting on page 408.
  - `authorization_id` number — Authorization ID. **REQUIRED** if `claim_id` and `arn` is not passed.
  - `arn` string — Acquirer reference number. **REQUIRED** if `claim_id` is not passed.
  - `transaction_amount` number, double — Transaction amount. **REQUIRED** if `claim_id` is not passed.
  - `transaction_date` string, date-time — Transaction date, format = yyyy-mm-dd hh:mm:ss. **REQUIRED** if `claim_id` is not passed.
  - `claim_id` string — Fee item claim ID
  - `card_acceptor_code` string — Merchant ID associated with this fee collection, if any.
  - `country_code` string — ISO 3166 3-letter country code.
  - `message` string — Message regarding fee - 100 chars maximum.
  - `settlement_date` string, date — Settlement date, format = yyyy-mm-dd.
  - `reply_fee_id` string — Fee ID to be sent in reply to created Fee.
  - `control_number` string — Control number. Used in routing chargeback and retrieval documentation - either a MasterCom endpoint suffix, in case of 2 characters, or a full MasterCom endpoint in case of 7 characters. When MasterCom control number is present, it cannot be all spaces or all zeros.

## Response `200`

OK

- DisputeFeeResponse — Dispute fee response object
  - `id` number — Dispute fee ID
  - `arn` string — Acquirer reference number. **REQUIRED** if `claim_id` is not passed.
  - `transaction_amount` number, double — Transaction amount. **REQUIRED** if `claim_id` is not passed.
  - `transaction_date` string, date-time — Transaction date, format = yyyy-mm-dd hh:mm:ss. **REQUIRED** if `claim_id` is not passed.
  - `card_id` integer — Enrolled card ID
  - `card_acceptor_code` string — Merchant ID associated with this fee collection..if any.
  - `country_code` string — ISO country code.
  - `destination_member` string — Destination member for the fee collection. These values are known to the network and identify either the acquirer or issuer.
  - `fee_date` string, date — Date the fee was attached to the claim, format = yyyy-mm-dd
  - `currency` string — ISO 4217 currency code.
  - `amount` number, double — Fee amount.
  - `message` string — Message regarding fee - 100 chars maximum.
  - `reason_code` string — Collection reason code. These codes can be found in Mastercard's [Global Clearing Management System Reference Manual](https://pismoassets.pismo.io/pismo-docs/mc_gcms_rm.pdf) starting on page 408.
  - `settlement_date` string, date — Settlement date, format = yyyy-mm-dd.
  - `control_number` string — Control number
  - `credit_sender` boolean — Credit the sender? Default is `false`.
  - `credit_receiver` boolean — Should receiver be credited?
  - `network_brand_type` 'Visa' | 'Mastercard' | 'Elo' — Network brand
  - `status` 'PENDING' | 'PROCESSED' | 'FAILED' — Dispute fee status - `PENDING`, `PROCESSED`, or `FAILED`.
  - `chargeback_ref_num` string — Chargeback reference number
  - `reconciliation_amount` number, double — Reconciliation amount
  - `reconciliation_currency` string — Reconciliation currency
  - `japan_common_merchant_code` string — Japanese common merchant codes
  - `installment_data` string — Installment data
  - `reply_fee_id` string — Fee ID to send to reply to created fee.
  - `reject_reason` string — Reject reason
  - `created_at` string — When dispute created, format = yyyy-mm-ddThh:mm:ss"
  - `updated_at` string, date-time — Datetime program calendar strategy was updated. Format = YYYY-MM-DDTHH:MM:SS:MM
  - `created_at_utc` string, date-time — Dispute created in UTC date/time.
  - `updated_at_utc` string — When dispute updated in UTC date/time.

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `422` — Unprocessable entity
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)