The tables below define values used in dispute management. For instructions on managing disputes with API, you should primarily reference the Dispute Management Guide. See the relevant endpoints' implementation guides and API reference for further detail. For more information on the dispute process and how to use the Maast Manager portal for disputes, see Disputes in the Maast Knowledge Base.

Received Dispute Conventions

This section describes values that give information about a dispute case. See the Dispute Management guide for instructions on receiving dispute case information.

GET Dispute Fields Returned

The table below provides the fields returned for each dispute case in a relevant webhook post or in response to a 'Get Disputes' request.

Field Name	Definition
`rec_id`	Control number - The control number for the dispute, a unique number associated with each dispute case received. One transaction can receive multiple disputes.
`merchant_id`	Merchant ID (MID) - The ID assigned to the merchant account.
`incoming_date`	Incoming date - The date the card issuer initiated the dispute.
`amt_tran`	Transaction amount - The amount of the original settled transaction in USD.
`amt_dispute`	Disputed amount - The amount being disputed. (This is equal to or less than the original transaction amount.)
`reason_code`	Reason code - The code providing the reason for the dispute. To view reason codes, reason categories, and response requirements for each reason code, see Dispute Reasons or Retrieval Requests and Response in the Maast Knowledge Base.
`reason_desc`	Reason description - Describes why the dispute was issued, per the dispute reason code.
`data_type`	Dispute type - The type of dispute. You can receive data on all dispute types. You can use the Dispute API to respond to retrieval requests and first-time disputes. For information on all dispute types, see Dispute Types in the Maast Knowledge Base.
`cbr_workflow`	Dispute workflow - The type of workflow assigned to the dispute. The returned values are `C` (Collaboration) and `A` (Allocation). For further information, see Visa Dispute Workflows or Mastercard Dispute Workflows in the Maast Knowledge Base.
`status`	Dispute status - The current status of the dispute.
`date_status_change`	Dispute status date - The date the dispute's status most recently changed.
`card_number`	Original card number - The masked number of the card associated with the dispute, formatted as 123456xxxxxx1234.
`tran_date`	Transaction date - The date the original transaction was authorized.
`reference_number`	Transaction reference number - This 23-digit number is associated with the original transaction data. Maast and the issuer use this number to identify a transaction.
`cb_ref_num`	Issuer reference number - A reference number assigned by the issuing bank to identify a unique dispute.

Dispute Types

The table below shows all dispute types currently possible (returned as data_type). For more information, see Dispute Types in the Maast Knowledge Base.

Dispute Type Code	Description
`C`	Chargeback - First Time
`V`	Retrieval Request
`P`	Pre-Arbitration (Visa, Mastercard, Discover)
`A`	Arbitration (Visa, Mastercard, Discover)
`M`	Compliance Notification (Visa, Discover)
`R`	Chargeback Reversal

Dispute Workflows

The table below shows the code and description for all possible dispute workflows. For more information, see Mastercard Dispute Workflows and Visa Dispute Workflows in the Maast Knowledge Base.

Dispute Workflow Code	Description
`S`	Standard
`C`	Collaboration
`A`	Allocation

Dispute Reason Codes: VISA

The table below shows reason codes (reason_code) provided for Visa dispute type C as well as the documentation you need to win in response to each dispute type. Alternatively, if you have already processed a credit or reversal, provide documentation of that and include the amount and the date it was processed. For more information, see Visa's Dispute Management Guidelines for Visa Merchants. For the other major card brands, see Dispute Reason Codes: MC, AMEX, DISC.

Dispute Reason Code (`reason_code`)	Description	Dispute Category
10.1	EMV Liability Shift Counterfeit Fraud	Fraud
10.2	EMV Liability Shift Non-Counterfeit Fraud	Fraud
10.3	Other Fraud – Card-Present Environment	Fraud
10.4	Other Fraud – Card-Absent Environment	Fraud
10.5	Visa Fraud Monitoring Program	Fraud
11.1	Card Recovery Bulletin	Authorization
11.2	Declined Authorization	Authorization
11.3	No Authorization	Authorization
12.1	Late Presentment	Processing Errors
12.2	Incorrect Transaction Code	Processing Errors
12.3	Incorrect Currency	Processing Errors
12.4	Incorrect Account Number	Processing Errors
12.5	Incorrect Amount	Processing Errors
12.6.1	Duplicate Processing	Processing Errors
12.6.2	Paid by Other Means	Processing Errors
12.7	Invalid Data	Processing Errors
13.1	Merchandise/Services Not Received	Consumer Disputes
13.2	Canceled Recurring Transaction	Consumer Disputes
13.3	Not as Described or Defective Merchandise/Services	Consumer Disputes
13.4	Counterfeit Merchandise	Consumer Disputes
13.5	Misrepresentation	Consumer Disputes
13.6	Credit Not Processed	Consumer Disputes
13.7	Canceled Merchandise/Services	Consumer Disputes
13.8	Original Credit Transaction Not Accepted	Consumer Disputes
13.9	Non-Receipt of Cash or Load Transaction Value	Consumer Disputes

Dispute Reason Codes: MC, AMEX, DISC

This section provides reason code descriptions and dispute categories for Mastercard, American Express, and Discover dispute reason codes (rcode). For Visa, see Dispute Reason Codes: VISA.

Dispute Reason Codes: MC

Dispute Reason Code (`reason_code`)	Reason Code Description	Dispute Category
4807	Card Recovery Bulletin	Authorization
4808	No Authorization	Authorization
4808	Declined Authorization	Authorization
4831	Incorrect Transaction Code	Processing Errors
4831	Paid by Other Means	Processing Errors
4834	Duplicate Processing	Processing Errors
4837	Fraud Card Not Present	Fraud
4837	Fraud Card Present	Fraud
4841	Canceled Recurring Transaction	Consumer Disputes
4842	Late Presentment	Processing Errors
4846	Incorrect Currency	Processing Errors
4855	Merchandise/Services Not Received	Consumer Disputes
4853 4854	Not as Described/Defective Merchandise or Services	Consumer Disputes
4860	Credit Not Processed	Consumer Disputes
4870 4871	Chip/PIN Liability Shift	Fraud

Dispute Reason Codes: AMEX

Dispute Reason Code (`reason_code`)	Reason Code Description	Dispute Category
A02	No Authorization	Authorization
C02	Credit Not Processed	Consumer Disputes
C08	Merchandise/Services Not Received	Consumer Disputes
C28	Canceled Recurring Transaction	Consumer Disputes
C31 C32	Not as Described/Defective Merchandise or Services	Consumer Disputes
127 F10 F14	Fraud Card Present	Fraud
F29	Fraud Card Not Present	Fraud
F30 F31	Chip/PIN Liability Shift	Fraud
P07	Late Presentment	Processing Errors
P03 P04 P05	Incorrect Transaction Code	Processing Errors
P23	Incorrect Currency	Processing Errors
P22	Incorrect Account Number	Processing Errors
P08	Duplicate Processing	Processing Errors

Dispute Reason Codes: DISC

Dispute Reason Code (`reason_code`)	Reason Code Description	Dispute Category
AP	Canceled Recurring Transaction	Consumer Disputes
C14	Paid by Other Means	Processing Errors
DA	Declined Authorization	Authorization
DA	Incorrect Transaction Code	Processing Errors
DP	Duplicate Processing	Processing Errors
EX	Expired Card	Authorization
EX	Incorrect Currency	Processing Errors
IN	Incorrect Account Number	Processing Errors
LP	Late Presentment	Processing Errors
NA	No Authorization	Authorization
RG	Merchandise/Services Not Received	Consumer Disputes
RM	Not as Described/Defective Merchandise or Services	Consumer Disputes
RN2	Credit Not Processed	Consumer Disputes
UA01	Fraud Card Present	Fraud
UA02	Fraud Card Not Present	Fraud
UA05 UA06	Chip/PIN Liability Shift	Fraud

Response Conventions

This section describes values used when sending a dispute response. See Response Conventions: MC, AMEX, DISC and Response Conventions: VISA for values permitted by each card type. For instructions on sending a dispute response, refer to the Dispute Management guide.

Response Reasons

This table shows the code and description for each response reason (cbr_response_type) you can input.

Response Reason Code	Description
`ND`	Cardholder No Longer Disputes
`CP`	Credit Processed
`CE`	Compelling Evidence
`OT`	Other
`ID`	Invalid Dispute
`MI`	Proof of Manual Imprint

For information on Visa's Remedy response option, see Visa Compelling Evidence 3.0 (CE 3.0) and April 2023 Changes in the Maast Knowledge Base.

Compelling Evidence (CE) Reason Detail Codes

If you input a CE response reason (cbr_response_type), this table provides all reason detail codes (cbr_ce_type) you can use and which card brands accept each code. Note that, for a Visa dispute, reason detail code options are based on the reason code (reason_code); see CE Reason Detail Codes: VISA.

Reason Detail Code (`cbr_ce_type`)	Description	Applicable Card Brands
`CE01`	Documentation to prove the cardholder is in possession of and/or using the merchandise. For Visa, the documentation type is limited to photographs and email.	MC, AMEX, DISC, VISA
`CE02`	Signed delivery form or copy/details of identification from the cardholder as proof goods were picked up at the merchant location.	MC, AMEX, DISC, VISA
`CE03`	AVS or Y or M and proof of delivery (date and time).	MC, AMEX, DISC, VISA
`CE04`	Digital goods download with time and date.	MC, AMEX, DISC, VISA
`CE05`	Delivery to the cardholder at their place of employment.	MC, AMEX, DISC, VISA
`CE06`	Travel and entertainment: loyalty transactions related to the purchase.	MC, AMEX, DISC
`CE07`	Travel and entertainment: subsequent purchases made throughout the service period.	MC, AMEX, DISC
`CE08`	Passenger transport: proof ticket was received, scanned at gate, or other transaction related to original (e.g. frequent flyer miles)	MC, AMEX, DISC
`CE09`	Evidence of one or more non-disputed payments for the same merchandise or service.	MC, AMEX, DISC, VISA
`CE10`	Authorized signer known by the cardholder.	VISA
`CE11`	Signed mail order/phone order form.	MC, AMEX, DISC, VISA
`CE12`	Legitimate spend across multiple payment types for the same merchandise.	MC, AMEX, DISC, VISA
`CE13`	Recurring transaction with a binding contract or previous undisputed recurring transactions and proof the cardholder is using the merchandise or service.	MC, AMEX, DISC, VISA
`CE14`	Signer is a member of the cardholder's household.	MC, AMEX, DISC, VISA

CE04 Required Fields

This table shows the additional fields required when you input a CE response reason (cbr_response_type) and a CE04 reason detail code (cbr_ce_type) in your dispute response:

Field Name	Format	Description
`download_description`	Variable length, up to 1000 AN	A description of what was downloaded.
`download_timestamp`	Fixed length, 25AN year, month, day, and time in ISO date-time format with offset (ex: `2022-12-03T10:15:30+01:00`)	The date and time of download.
`ce_indicators`	String	List the indicators that you are including with your response. See CE04 Indicators.

CE04 Indicators

this table shows the fields that you can use in the ce_indicators string when you input a CE response reason (cbr_response_type) and a CE04 reason detail code (cbr_ce_type) in your dispute response. You must use at least two of these fields:

Field Name	Description
`ip_address_geo`	The purchaser's IP address and the device's geographical location at the date and time of the transaction.
`device_id_name`	The device ID and name of the device.
`name_email`	The purchaser's name and email address linked to the customer profile held by the merchant.
`profile_access`	Evidence that the profile was set up by the purchaser on the merchant's website or the application was accessed by the purchaser and has been successfully verified by the merchant before the transaction date.
`website_access`	Proof that the merchant's website or application was accessed by the cardholder for merchandise or services on or after the transaction date.
`prev_not_disputed`	Evidence that the same device and card used in the disputed transaction were used in any previous transaction that was not disputed. NOTE: With this option, you must supply the following transaction information for the previously undisputed transaction: • `tran_date` - The transaction date of the previously undisputed payment. • `amt_purch` - The payment amount of the previously undisputed payment. • `reference_number` - The reference number of the previously undisputed payment. This 23-digit number associated with the original transaction data is generated by the product initiating the transaction. Maast and the issuer use this number to identify a transaction. To locate the transaction and view its associated data, use 'Get Non-Disputed Transaction'.

CE09 Required Fields

This table shows the additional fields required when you input a CE response reason (cbr_response_type) and a CE09 reason detail code (cbr_ce_type) in your dispute response:

Field Name	Format	Description
`tran_date`	Fixed length, 10 AN year, month, and date in ISO date format (ex: `2022-12-03`)	The transaction date of the related and previously undisputed payment. To locate the transaction and view the associated data, use GET Non-Disputed Transaction.
`amt_purch`	Variable length, N	The payment purchase amount.
`reference_number`	Fixed length, 23 N	Reference number of the payment. This 23-digit number associated with the original transaction data is generated by the product initiating the transaction. Maast and the issuer use this number to identify a transaction.
`ce_indicators`	Variable length, AN	List the indicators you are including with your response. You must include at least three indicators. See CE09 Indicators.

CE09 Indicators

This table shows the fields you can use in the ce_indicators string when you input a CE response reason (cbr_response_type) and a CE09 reason detail code (cbr_ce_type) in your dispute response. Use at least three of these fields:

Value	Description
`ip_address`	IP address
`email_address`	Email address
`physical_address`	Physical address
`phone_number`	Phone number
`login_id`	Customer account login ID
`device_id_or_fingerprint`	Device ID / device fingerprint

See the example code of a CE09 response detail below:

{
"message": "Test Response Description for CE09",
"cbr_response_type": "CE",
"cbr_ce_type": "CE09",
"ce_indicators": ["phone_number", "ip_address", "email_address"],
"amt_tran": 2.12,
"tran_date":"2017-01-01",
"amt_purch":2,
"reference_number":"12312345690989765789478"
}

CE13 Required Fields

This table shows the additional fields required when you input a CE response reason (cbr_response_type) and a CE13 reason detail code (cbr_ce_type) in your dispute response:

Field Name	Format	Description
`tran_date`	Fixed length, 10 AN year, month, and date in ISO date format (ex: `2022-12-03`)	The transaction date of the related and previously undisputed payment. To locate the transaction and view the associated data, use GET Non-Disputed Transaction.
`amt_purch`	Variable length, N	The payment purchase amount.
`reference_number`	Fixed length, 23 N	Reference number of the payment. This 23-digit number associated with the original transaction data is generated by the product initiating the transaction. Maast and the issuer use this number to identify a transaction.

See the example code of a CE13 response detail below:

{
"message": "Test Response Description for CE13",
"cbr_response_type": "CE",
"cbr_ce_type":"CE13",
"amt_tran": 2.12,
"tran_date":"2011-12-03",
"amt_purch":50,
"reference_number":"123767878787878788p8788"
}

Response Conventions: MC, AMEX, DISC

This section provides conventions to use in your response to a first-time chargeback (C) dispute involving Mastercard, American Express, or Discover.

Response Body Parameters: MC, AMEX, DISC

The table below shows the body parameters required for a first-time chargeback (C) response:

Field	Format	Description
`file`	PDF	Supporting PDF documentation
`disputeResponse`	JSON message body	To populate this array, see the `disputeResponse` Array Fields: MC, AMEX, DISC table below.

`disputeResponse` Array Fields: MC, AMEX, DISC

The table below shows fields to include in the disputeResponse array in a first-time chargeback (C) response for a dispute involving Mastercard, American Express, or Discover:

Field	Requirement	Format	Description
`message`	Required	Variable length, up to 5000 AN	Message - A description of the response.
`cbr_response_type`	Required	Fixed length, 2A	Response reason - Select from the following: • `ND`: Cardholder no longer disputes. • `CP`: Credit processed. • `CE`: Compelling evidence. • `OT`: Other.
`amt_tran`	Optional	Variable length, N	Dispute amount - The amount that you are challenging. You may challenge any amount less than or equal to the full dispute amount.
`batch_date`	Conditional Requirement: Required for `CP` response reason.	Fixed length, 10 AN year, month, and date in ISO date format (ex: `2022-12-03`)	Batch date - The date the credit was processed.
`reference_number`	Conditional Requirement: Required for `CP` response reason.	Fixed length, 23 N	Reference number - The reference number of the credit, which was generated by the product initiating the transaction. Send a 'Get non-disputed transaction' request to find this number.
`cbr_ce_type`	Conditional Requirement: Required for `CE` response reason.	Fixed length, 4 AN	Reason detail - Select from the following: • `CE01`: Documentation proving the cardholder is in possession of and/or using the merchandise. • `CE02`: A signed delivery form or a copy/details of identification from the cardholder as proof that goods were picked up at the merchant location. • `CE03`: AVS or Y or M and proof of delivery (date and time). • `CE04`: A digital goods download with time and date (additional fields required; see CE04 Required Fields). • `CE05`: Delivery to the cardholder at their place of employment. • `CE06`: Travel and entertainment: loyalty transactions related to the purchase. • `CE07`: Travel and entertainment: Subsequent purchases made throughout the service period. • `CE08`: Passenger transport: Proof the ticket was received, scanned at gate, or other transaction related to origin. • `CE09`: Evidence of one or more non-disputed payment(s) for the same merchandise or service (additional fields required; see CE09 Required Fields). • `CE11`: Signed mail order or phone order form. • `CE12`: Legitimate spend across multiple payment types for the same merchandise. • `CE13`: A recurring transaction with a binding contract or previous undisputed recurring transactions and proof the cardholder is using the merchandise or service (additional fields required; see CE13 Required Fields). • `CE14`: Signer is a member of the cardholder's household.

Response Conventions: VISA

This section provides conventions to use in your response to a first-time chargeback (C) dispute involving Visa.

Response Body Parameters: VISA

The table below shows the required fields for a response to a first-time chargeback dispute involving Visa:

Field	Format	Description
`file`	PDF	Supporting PDF documentation
`disputeResponse`	JSON message body	To populate this array, see the `disputeResponse` Array Fields: VISA table below.

`disputeResponse` Array Fields: VISA

The table below shows the fields to include in a disputeResponse array within a first-time chargeback Visa dispute response:

Field	Requirement	Format	Description
`message`	Required	Variable length, up to 5000 AN	Message - A description to the response.
`cbr_response_type`	Required	Fixed length, 2A	Response reason - Submit one response reason. Your options for response reason are dependent on the dispute reason code (`reason_code`) provided. See the Response Reason Options: VISA table below.
`amt_tran`	Optional	Variable length, N	Dispute amount - The amount that you are challenging. You may challenge any amount less than or equal to the full dispute amount.
`batch_date`	Conditional Requirement: Required for `CP` response reason.	Fixed length, 10 AN	Batch date - The date the credit was processed.
`reference_number`	Conditional Requirement: Required for `CP` response reason.	Fixed length, 23 N	Reference number - The reference number of the credit, which was generated by the product initiating the transaction. Send a 'Get Non-Disputed Transaction' request to find this number.
`cbr_ce_type`	Conditional Requirement: Required for `CE` response reason.	Fixed length, 4 AN	Reason detail - Submit one reason detail code. Your options for reason detail code are dependent on the dispute reason code (`reason_code`) provided. See the CE Reason Detail Codes: VISA table below.

Response Reason Options: VISA

You must submit one response reason (cbr_response_type) when responding to a first-time chargeback Visa dispute. The dispute reason code provided (reason_code) determines your options for which response reason you may submit. The table below shows the options available for each dispute reason code:

Reason Code (`reason_code`)	Reason Code Description	Response Reason (`cbr_response_type`) Options
10.1	EMV Liability Shift Counterfeit Fraud	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
10.2	EMV Liability Shift Non-Counterfeit Fraud	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
10.3	Other Fraud - Card-Present Environment	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute • `MI`: Proof of manual imprint
10.4	Other Fraud - Card-Absent Environment	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `CE`: Compelling evidence. Reason detail required; see CE Reason Detail Codes: VISA for options. • `ID`: Invalid dispute For the Remedy response option, see this article in the Maast Knowledge Base.
10.5	Visa Fraud Monitoring Program	• `ND`: Cardholder no longer disputes • `CP`: Credit processed
11.1	Card Recovery Bulletin	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
11.2	Declined Authorization	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
11.3	No Authorization	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
12.1	Late Presentment	• `ND`: Cardholder no longer disputes • `CP`: Credit processed
12.2	Incorrect Transaction Code	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
12.3	Incorrect Currency	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
12.4	Incorrect Account Number	• `ND`: Cardholder no longer disputes • `CP`: Credit processed
12.5	Incorrect Amount	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
12.6.1	Duplicate Processing	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
12.6.2	Paid by other Means	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute
12.7	Invalid Data	• `ND`: Cardholder no longer disputes • `CP`: Credit processed
13.1	Merchandise/Services Not Received	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `CE`: Compelling evidence. Reason detail required; see CE Reason Detail Codes: VISA for options. • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.2	Cancelled Recurring	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.3	Not as Described or Defective	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.4	Counterfeit Merchandise	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.5	Misrepresentation	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.6	Credit Not Processed	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.7	Cancelled Merchandise/Services	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.
13.8	Original Credit Transaction Not Accepted	• `ND`: Cardholder no longer disputes • `CP`: Credit processed
13.9	Non-Receipt of Cash or Load Transaction Value	• `ND`: Cardholder no longer disputes • `CP`: Credit processed • `ID`: Invalid dispute. Reason detail required; see ID Codes: VISA for options.

Compelling Evidence (CE) Reason Detail Codes: VISA

You may input a CE response reason (cbr_response_type) for dispute reason code (reason_code) 10.4 or 13.1. If you do so, a reason detail code (cbr_ce_type) is required. This table provides the reason detail codes you may use. Reason detail code options are based on the dispute reason code provided:

Reason Detail Code (`cbr_ce_type`)	Description	Applicable to `reason_code` 10.4?	Applicable to `reason_code` 13.1?
`CE01`	Photographic or email evidence to prove the cardholder is in possession of and/or using the merchandise or services.	✅	✅
`CE02`	Signed delivery form or a copy or details of identification from cardholder as proof goods were picked up at the merchant location.	✅	✅
`CE03`	AVS or Y or M and proof of delivery (date and time).	✅	✅
`CE04`	Digital goods download with time and date. Additional fields required; see CE04 Required Fields.	✅	✅
`CE05`	Delivery to cardholder at the place of employment.	✅	✅
`CE09`	Evidence of one or more non disputed payments for same merchandise or service. Additional fields required; see CE09 Required Fields.	✅	❌
`CE10`	Authorized signer known by the cardholder.	❌	✅
`CE11`	Signed mail order/phone order form.	✅	❌
`CE12`	Legitimate spend across multiple payment types for same merchandise.	✅	❌
`CE13`	Recurring transaction with binding contract or previous undisputed recurring transactions and proof the cardholder is using the merchandise or service. Additional fields required; see CE13 Required Fields.	✅	❌
`CE14`	Signer is a member of the cardholder's household.	✅	❌

Invalid Dispute (ID) Codes: VISA

When you send an Invalid Dispute response reason ("cbr_response_type": "ID") for a Visa dispute, you may also be required to provide a response reason detail (cbr_id_type). The dispute reason code (reason_code) returned with the dispute case's data determines your options for response reason details. The table below shows which response reason details you may use for each reason code:

Reason Code (`reason_code`)	Response Reason Detail (`cbr_id_type`)
12.2	Use one of the following: • `IDRP1` - Transaction code is correct. • `IDRP2` - Credit was processed correctly.
12.3	`IDRP3` - Currency is correct.
13.1	Use one of the following: • `IDRC7` - Cardholder received merchandise at the agreed upon location or by the agreed time. • `IDRC4` - Cardholder canceled before the expected receipt date of the merchandise/services. • `IDRC5` - Merchandise is being held at the cardholder's customs agency. • `IDRC6` - The balance of a partial prepayment was not paid, and the merchant was willing and able to provide the merchandise/services. • `IDRC25` - Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.)
13.2	Use one of the following: • `IDRC1` - Services or merchandise were provided prior to the cancellation date. • `IDRC2` - Acquirer or merchant was not notified that the account was closed. • `IDRC3` - Cardholder requested cancellation for a different date, and the services were provided until that date. (NOTE: If selected, you must provide the `cancellation_date` field with the cancellation date the cardholder requested.) • `IDRC24` - Cardholder did not attempt to return the merchandise. • `IDRC25` - Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.) Visa rules now require issuers to provide the date a customer canceled a recurring transaction and the cancellation details when sending reason code 13.2.
13.3	Use one of the following: • `IDRC11` - Merchandise or service matched what was described. • `IDRC12` - Merchandise was not damaged. • `IDRC13` - Merchandise or service was not defective. • `IDRC14` - Merchandise or service quality matched what was described. • `IDRC24` - Cardholder did not attempt to return the merchandise. • `IDRC25` - Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.)
13.4	`IDRC21` - Docs to support merchant claim that merchandise is not counterfeit.
13.5	Use one of the following: • `IDRC22` - Docs to prove terms of sale were not misrepresented. • `IDRC24` - Cardholder did not attempt to return the merchandise. • `IDRC25` - Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.)
13.6	Use one of the following: • `IDRC15` - Dispute is for the cash back portion of a Visa cash back transaction. • `IDRC16` - Dispute is for quality and services, and there was no credit receipt provided. • `IDRC17` - Disputed amount is a value-added tax, and there was no credit receipt provided. • `IDRC24` - Cardholder did not attempt to return the merchandise. • `IDRC25` - Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.)
13.7	Use one of the following: • `IDRC18` - Merchant properly disclosed a limited return or cancellation policy at the time of the transaction. • `IDRC19` - Cardholder received merchant cancellation or return policy and did not cancel according to the policy. • `IDRC1` - Services or merchandise was provided prior to the cancellation date. • `IDRC9` - Dispute amount is due to a value-added tax. • `IDRC10` - Returned merchandise is being held in a customs agency outside the merchant's country. • `IDRC23` - Dispute is for quality. • `IDRC24` - Cardholder did not attempt to return the merchandise. • `IDRC25` - Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.)
13.9	`IDRC20` - A copy of the ATM transaction record confirming the cash disbursement or load transaction value was successful.

Invalid Dispute (ID) Code Descriptions: VISA

This table shows codes and descriptions for all possible response reason details (cbr_id_type) for an Invalid Dispute response reason (cbr_response_type) in a dispute involving Visa. Note that the response reason details you may use are limited by the dispute's reason code (reason_code); see ID Codes: VISA for more information.

Response Reason Detail Code (`cbr_id_type`)	Description
`IDRP1`	Transaction code is correct.
`IDRP2`	Credit was processed correctly.
`IDRP3`	Currency is correct.
`IDRC1`	Services or merchandise were provided prior to the cancellation date.
`IDRC2`	Acquirer or merchant was not notified that the account was closed.
`IDRC3`	Cardholder requested cancellation for a different date, and the services were provided until that date. (NOTE: If selected, you must provide the `cancellation_date` field with the cancellation date the cardholder requested.)
`IDRC4`	Cardholder canceled before the expected receipt date of the merchandise/services.
`IDRC5`	Merchandise is being held at the cardholder's customs agency.
`IDRC6`	The balance of a partial prepayment was not paid, and the merchant was willing and able to provide the merchandise/services.
`IDRC7`	Cardholder received merchandise at the agreed upon location or by the agreed time.
`IDRC9`	Dispute amount is due to a value-added tax.
`IDRC10`	Returned merchandise is being held in a customs agency outside the merchant's country.
`IDRC11`	Merchandise or service matched what was described.
`IDRC12`	Merchandise was not damaged.
`IDRC13`	Merchandise or service was not defective.
`IDRC14`	Merchandise or service quality matched what was described.
`IDRC15`	Dispute is for the cash back portion of a Visa cash back transaction.
`IDRC16`	Dispute is for quality and services, and there was no credit receipt provided.
`IDRC17`	Disputed amount is a value-added tax, and there was no credit receipt provided.
`IDRC18`	Merchant properly disclosed a limited return or cancellation policy at the time of the transaction.
`IDRC19`	Cardholder received merchant cancellation or return policy and did not cancel according to the policy.
`IDRC20`	A copy of the ATM transaction record confirming the cash disbursement or load transaction value was successful.
`IDRC21`	Docs to support merchant claim that merchandise is not counterfeit.
`IDRC22`	Docs to prove terms of sale were not misrepresented.
`IDRC23`	Dispute is for quality.
`IDRC24`	Cardholder did not attempt to return the merchandise.
`IDRC25`	Not listed above. (NOTE: If selected, please include the `reason_desc` field with a description in 100 characters of why the dispute is invalid.)

Test Dispute Data

Below are all possible test dispute cases that you can use to test Dispute API integration. Use the 'Reason Code' column to populate the reasonCode string in a Create Dispute Data request:

Reason Code (`reasonCode`)	Card Type	Workflow	Dispute Type	Test Case
4837	Mastercard	Standard (S)	First-Time Dispute (C)	Status = “N” (New). Test response to a Mastercard dispute.
RG	Discover	Standard (S)	Pre-Arbitration (P)	Status = “N” (New). Test response to a pre-arbitration.
28	Visa	Standard (S)	Retrieval Request (V)	Status = “N” (New). Test response.
75	Visa	Standard (S)	First-Time Dispute (C)	Status = “C” (Issuer Accepted). Test change in dispute status.
83	Visa	Standard (S)	First-Time Dispute (C)	Status = “A” (Accepted). Test change in dispute status.
10.3	Visa	Allocation (A)	First-Time Dispute (C)	Status = “O” (Challenge Expired). Test change in dispute status.
10.3	Visa	Allocation (A)	First-Time Dispute (C)	Status = “N” (New). Test responses.
10.4	Visa	Allocation (A)	First-Time Dispute (C)	Status = “N” (New). Test responses.
11.1	Visa	Allocation (A)	First-Time Dispute (C)	Status = “N” (New). Test responses.
12.2	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
12.3	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.1	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.2	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.3	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.4	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.5	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.7	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.
13.9	Visa	Collaboration (C)	First-Time Dispute (C)	Status = “N” (New). Test responses.