Create dispute 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 in the Disputes overview guide. This feature is only available for Mastercard and Elo.

This endpoint generates a Dispute fee status created 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 401 Unauthorized message.

Body Params

Dispute fee data

double
required

Fee amount.

number
required

Pismo card ID.

boolean
required
Defaults to false

Credit the sender?

boolean
required
Defaults to false

Credit the receiver?

string
required
length ≤ 3

ISO 4217 fee currency code.

string
required
length ≤ 6

Destination member for the fee collection. These values are known to the network and identify either the issuer or acquirer.

date
required
length ≤ 10

Date the fee was attached to the claim, format = yyyy-mm-dd.

string
enum
required

Network brand

Allowed:
string
required
length ≤ 4

Collection reason code. These codes can be found in Mastercard's Global Clearing Management System Reference Manual starting on page 408.

number

Authorization ID. REQUIRED if claim_id and arn is not passed.

string

Acquirer reference number. REQUIRED if claim_id is not passed.

double

Transaction amount. REQUIRED if claim_id is not passed.

date-time

Transaction date, format = yyyy-mm-dd hh:mm:ss. REQUIRED if claim_id is not passed.

string
length ≤ 19

Fee item claim ID

string
length ≤ 15

Merchant ID associated with this fee collection, if any.

string
length ≤ 3

ISO 3166 3-letter country code.

string
length ≤ 100

Message regarding fee - 100 chars maximum.

date
length ≤ 10

Settlement date, format = yyyy-mm-dd.

string
length ≤ 19

Fee ID to be sent in reply to created Fee.

string
length ≤ 7

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.

Headers
string
required

Account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a 401 Unauthorized message.

Responses

400

Bad Request

401

Unauthorized. Invalid or missing access token.

422

Unprocessable entity

500

Internal server error

Language
Credentials
Bearer
JWT
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json