Update dispute fee

Update dispute fee - only if status is PENDING or FAILED. Requires a dispute fee ID in the path. You can get fee IDs with the List dispute fees endpoint.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Body Params

Dispute fee object

double
required

Fee amount.

number
required

Pismo card ID.

boolean
required
Defaults to false

Credit the sender? Default is false.

boolean
required
Defaults to false

Credit the receiver? Default is false.

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.

Responses

400

Bad Request

401

Unauthorized. Invalid or missing access token.

404

Not found

422

Unprocessable entity

500

Internal server error

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