No momento, esta página não está disponível em português

Disputes API reference

You can use the Disputes Service to automate the dispute handling process so that you can respond to disputes and chargebacks as soon as they are initiated. The Disputes API lets you retrieve defense reasons, supply and delete defense documents, and accept or defend disputes.

For more information on how the API works, refer to Disputes API.

Authentication

Each request to the Disputes API must be signed with an API key. For this, obtain an API Key from your Customer Area, as described in API credentials. Then set this key to the X-API-Key header value, for example:

curl
-H "Content-Type: application/json" \
-H "X-API-Key: Your_API_key" \
...

Note that when going live, you need to generate new web service user credentials to access the live endpoints.

If you already have a test environment up and running, you can assign the API dispute management role to the API user.

Endpoints

To communicate with the Adyen API you should submit HTTP POST requests to corresponding endpoints. These endpoints differ for test and live accounts, and also depend on the data format (SOAP, JSON, or FORM) you use to submit data to the plataforma de pagamentos da Adyen.

This page gives you a reference to integrate with the test platform and run QA checks.

JSON

Use the following endpoints in test environment. To switch to live, change the domain to ca-live.adyen.com.

Endpoint	Description
https://ca-test.adyen.com/ca/services/DisputeService/v30/retrieveApplicableDefenseReasons	Retrieves a list of applicable defense reasons. For parameters, refer to: - DefenseReasonsRequest - DefenseReasonsResponse
https://ca-test.adyen.com/ca/services/DisputeService/v30/supplyDefenseDocument	Uploads defense documents. For parameters, refer to: - SupplyDefenseDocumentRequest - SupplyDefenseDocumentResponse
https://ca-test.adyen.com/ca/services/DisputeService/v30/deleteDisputeDefenseDocument	Deletes previously uploaded defense documents. For parameters, refer to: - DeleteDefenseDocumentRequest - DeleteDefenseDocumentResponse
https://ca-test.adyen.com/ca/services/DisputeService/v30/defendDispute	Submits final dispute defense to the schemes. For parameters, refer to: - DefendDisputeRequest - DefendDisputeResponse
https://ca-test.adyen.com/ca/services/DisputeService/v30/acceptDispute	Lets you accept a dispute without defending it. For parameters, refer to: - AcceptDisputeRequest - AcceptDisputeResponse

SOAP

Test	https://ca-test.adyen.com/ca/services/DisputeService
Live	https://ca-live.adyen.com/ca/services/DisputeService

The data schema for the corresponding SOAP objects is available at:

Test	https://ca-test.adyen.com/ca/services/DisputeService?wsdl
Live	https://ca-live.adyen.com/ca/services/DisputeService?wsdl

AcceptDisputeRequest

Accepts a specific dispute.

Field	Type	Required	Description
`disputePspReference`	String		The PSP reference assigned to the dispute. You can retrieve the `pspReference` from the webhook that you received.
`merchantAccountCode`	String		The merchant account identifier, for which you want to accept the dispute.

AcceptDisputeResponse

A container for the result of the response.

Field	Type	Required	Description
`disputeServiceResult`	DisputeServiceResult		A container for the response result.

DefendDisputeRequest

Defends a specific dispute.

Field	Type	Description
`defenseReasonCode`	String	The defense reason code that was selected to defend this dispute. For possible values per scheme, see the list of defense reason codes.
`disputePspReference`	String	The PSP reference assigned to the dispute. You can retrieve the `pspReference` from the webhook that you received.
`merchantAccountCode`	String	The merchant account identifier, for which you want to defend the dispute.

DefendDisputeResponse

A container for the result of the response.

Field	Type	Required	Description
`disputeServiceResult`	DisputeServiceResult		A container for the response result.

DefenseDocument

A container for a defense document.

Field	Type	Description
`content`	Base64 binary	The content of the defense document in Base64 binary format. Must be encoded in the format that is specified in the `contentType` field.
`contentType`	String	The content type of the document. Possible values: image/jpg image/jpeg image/tiff application/pdf
`defenseDocumentTypeCode`	String	The document type code of the defense document. For possible values per scheme, see the list of defense document type codes. You can add a generalized defense document type. Contact our Support Team to enable this document type. When enabled, you can supply a generic defense document for all schemes and set the `defenseDocumentTypeCode` to AlternativeDefenseMaterial.

DefenseDocumentType

A container for a defense document type.

Field	Type	Description
`available`	Boolean	When true, you've successfully uploaded this type of defense document. When false, you haven't uploaded this defense document type.
`defenseDocumentTypeCode`	String	The document type code of the defense document. For possible values per scheme, see the list of defense document type codes.
`requirementLevel`	String	Indicates to what extent the defense document is required in the defense process. Possible values: Required You must supply the document. OneOrMore You must supply at least one of the documents with this label. Optional You can choose to supply the document. AlternativeRequired You must supply a generic defense document. Contact our Support Team to enable the generic defense document type. When enabled, you can supply a generic defense document for all schemes.

DefenseReason

A container for a defense reason.

Field	Type	Description
`defenseDocumentTypes`	Array of DefenseDocumentType	Array of defense document types for a specific defense reason. Indicates the document types that you can submit to the schemes to defend this dispute, and whether they are required.
`defenseReasonCode`	String	The defense reason code that was selected to defend this dispute. For possible values per scheme, see the list of defense reason codes.
`satisfied`	Boolean	Indicates if sufficient defense material has been supplied to defend the dispute with a specific reason code.

DefenseReasonsRequest

Returns a list of all applicable defense reasons to defend a specific dispute.

Field	Type	Required	Description
`disputePspReference`	String		The PSP reference assigned to the dispute. You can retrieve the `pspReference` from the webhook that you received.
`merchantAccountCode`	String		The merchant account identifier, for which you want to process the dispute transaction.

DefenseReasonsResponse

Contains a list of all available defense reasons that can be used to defend a specific dispute.

The defense reason object in the response contains the applicable defense reason codes, specified by scheme regulations. It also contains the corresponding document types, whether those document types are required or not, and if the documents are already available.

Field Type Required Description

defenseReasons

Array of DefenseReason

A list of defense reasons that are applicable to the dispute.

disputeServiceResult

DisputeServiceResult

A container for result of this response.

DeleteDefenseDocumentRequest

Deletes a specific dispute defense document that was supplied earlier.

Field	Type	Description
`disputePspReference`	String	The PSP reference assigned to the dispute. You can retrieve the `pspReference` from the webhook that you received.
`merchantAccountCode`	String	The merchant account identifier, for which you want to process the dispute transaction.
`defenseDocumentType`	String	The document type code of the defense document. For possible values per scheme, see the list of defense document type codes.

DeleteDefenseDocumentResponse

A container for the result of the response.

Field Type Required Description

disputeServiceResult

DisputeServiceResult

A container for result of this response.

DisputeServiceResult

A container for result of the response.

Field Type Required Description

success

Boolean

Outcome of the operation. If unsuccessful, an error message will be given in the next field.

errorMessage

String

Description of the error. Possible values:

Dispute already defended.
Dispute cannot be accepted.
Dispute defense period has ended.
Dispute expired.
Dispute is not defendable.
Dispute not found.
Error processing file. Please try again later or contact support if the problem persists.
Error retrieving dispute.
Failed to store defense documents.
Failed to validate defense documents.
File exceeds the limit of allowed pages (statusCode : maxFileSizeInPages).
File is too large for this format.
File was found to possibly contain malware or a virus. Not accepted.
Files exceed the total limit of allowed pages across documents (statusCode : maxFileSizeInPages).
Invalid disputePspReference provided.
Invalid file format or extension. This file is not a JPG/JPEG file.
Invalid file format or extension. This file is not a PDF file.
Invalid file format or extension. This file is not a TIFF file.
No content of defense document specified.
No content type of defense document specified.
No defense document type of defense document specified.
No defense documents supplied.
No defense reason code specified.
No document found to delete.
Non-existing defense document type specified.
Not allowed content type of defense document specified.
Request object not found.
Unable to delete.
Unable to process the uploaded defense document.
Unknown dispute.

SupplyDefenseDocumentRequest

Supplies a specific dispute defense document.

Field	Type	Description
`defenseDocuments`	Array of DefenseDocument	A container for the defense documents.
`disputePspReference`	String	The PSP reference assigned to the dispute. You can retrieve the `pspReference` from the webhook that you received.
`merchantAccountCode`	String	The merchant account identifier, for which you want to process the dispute transaction.

SupplyDefenseDocumentResponse

A container for the result of the response.

Field	Type	Required	Description
`disputeServiceResult`	DisputeServiceResult		A container for the result of this response.

defenseReasonCode

American Express

defenseReasonCode	Description
`AutomaticRFIresponse`	Response to a Request for Information (Automatic Response)
`CardNotPresentRFIresponse`	Normal response to a Request for Information
`CreditPreviouslyIssued`	Credit previously issued
`DuplicateChargeback`	Duplicate Chargeback
`GoodsOrServicesProvided`	The goods or services were provided by the merchant, or there was a delay in delivery.
`GoodsWereAsDescribed`	The merchant can proof that the goods were delivered as described.
`MerchandiseReceived`	Merchandise received by shopper.
`PastChargebackTimeLimit`	Past Chargeback Time Limit
`SupplyDefenseMaterial`	Defense Material can be supplied that remedies the chargeback.

Elo

defenseReasonCode	Description
`AdditionalInformation`	Additional Information
`AirlineFlightProvided`	Shopper has or could have used the provided airline ticket.
`AutomaticRFIresponse`	Response to a Request for Information (Automatic Response)
`CreditPreviouslyIssued`	Credit previously issued
`CardNotPresentRFIresponse`	Normal response to a Request for Information
`GoodsNotReturned`	The cardholder did not return the goods to the merchant.
`GoodsOrServicesProvided`	The goods or services were provided by the merchant, or there was a delay in delivery.
`GoodsRepairedOrReplaced`	The merchant documents that the goods were repaired or replaced.
`GoodsWereAsDescribed`	The merchant can proof that the goods were delivered as described.
`PastChargebackTimeLimit`	Past Chargeback Time Limit
`ServicesProvidedAfterCancellation`	The merchant has provided services after the cancellation data which have been used by the cardholder.
`SupplyDefenseMaterial`	Defense Material can be supplied that remedies the chargeback.

Discover

defenseReasonCode	Description
`AdditionalInformation`	Additional Information
`AirlineRFIresponse`	Response to a Request for Information (Airlines)
`AuthorisedTransaction`	Authorisation was received for the transaction amount or greater from the issuer.
`AutomaticRFIresponse`	Response to a Request for Information (Automatic Response)
`CancellationTermsFailed`	The cardholder failed to meet the cancellation terms of the contract.
`CardNotPresentRFIresponse`	Normal response to a Request for Information
`CardPresentRFIresponse`	Response to a Request for Information (Card Present only)
`CardholderNotReplied`	Cardholder was notified but did not reply
`CardholderParticipated`	Compelling evidence that the cardholder participated in the transaction.
`CardholderRenewedMembership`	Cardholder renewed membership after cancellation.
`CarRentalRFIresponse`	Response to a Request for Information (Car Rental)
`CorrectTransactionAmount`	The TID shows that the amount was processed correctly.
`CreditOrCancellationPolicyProperlyDisclosed`	The merchant can substantiate that the credit or cancellation policy was properly disclosed to the cardholder at the point of interaction.
`CreditPreviouslyIssued`	Credit previously issued
`DuplicateChargeback`	Duplicate Chargeback
`GoodsOrServicesProvided`	The goods or services were provided by the merchant or there was a delay in delivery.
`GoodsRepairedOrReplaced`	The merchant documents that the goods were repaired or replaced.
`GoodsWereAsDescribed`	The merchant can proof that the goods were delivered as described.
`GoodsNotReturned`	The cardholder did not return the goods to the merchant.
`IncreasedTransactionAmount`	The increased debit to the account is valid.
`MerchandiseNotCounterfeit`	Merchandise was not counterfeit
`MerchandiseReceived`	Merchandise received by shopper
`NotCancelled`	Documentation showing cardholder did not cancel the transaction
`NotNotified`	Documentation showing acquirer and merchant were not notified of cancellation of membership
`NotRecurring`	Transaction was not a recurring transaction
`PastChargebackTimeLimit`	Past Chargeback Time Limit
`PaymentByOtherMeans`	The merchant can provide an explanation that substantiates the validity of the transaction charged.
`PINTransaction`	PIN was present
`ProofOfCardPresenceAndSignatureWithTerminalReceipt`	Card was present and a signed terminal receipt is available.
`ProofOfCardPresenceAndSignatureWithoutTerminalReceipt`	Card was present and documentation is available to prove this.
`PurchaseProperlyPosted`	The issuer claimed that the transaction was not for an installment billing and transaction was properly identified as an installment transaction in the authorization request.
`RetrievalRequestFulfilled`	The retrieval request has been fulfilled.
`SaleTermsNotMisrepresented`	Terms of sale were not misrepresented.
`ServicesProvidedAfterCancellation`	The merchant has provided services after the cancellation data which have been used by the cardholder.
`ShippedToAVSAdditionalInformation`	Address Verification Service (AVS) Additional Information
`SupplyDefenseMaterial`	Defense Material that remedies the chargeback.
`TransactionNotPOS`	Transactions was not a POS transaction.
`TwoDifferentTIDs`	Two different TIDs with the same card number are present.

Mastercard

defenseReasonCode	Description
`AccountTakeover`	The transaction resulted from an account takeover
`AdditionalInformation`	Additional Information
`AirlineCompellingEvidence`	Non face-to-face Airline Additional Information
`AirlineFlightProvided`	Shopper has or could have used the provided airline ticket
`AirlineRFIresponse`	Response to a Request for Information (Airlines)
`AuthorisedTransaction`	Authorisation was received for the transaction amount or greater from the issuer.
`AutomaticRFIresponse`	Response to a Request for Information (Automatic Response)
`CancellationOrReturns`	The merchandise was never returned or the cancellation was not accepted
`CancellationTermsFailed`	The cardholder failed to meet the cancellation terms of the contract
`CardNotPresentRFIresponse`	Normal response to a Request for Information
`CardPresentRFIresponse`	Response to a Request for Information (Card Present only)
`CarRentalRFIresponse`	Response to a Request for Information (Car Rental)
`ChargebackRemedied`	Chargeback remedied. See corresponding documentation.
`ChipAndPinLiabilityShift`	The transaction was initiated on a POS terminal with PIN path but card was not PIN preferring.
`ChipLiabilityNotApplicable`	Chip Liability not applicable
`ChipLiabilityShift`	The transaction falls under the Chip Liability Shift and occurred on a non-EMV chip card.
`ChipTransactionReportedToSAFE`	Chip Transaction Reported to SAFE
`CompellingEvidence`	Compelling Evidence
`CorrectedMcc`	The MCC was incorrect in the first presentment. With the correct MCC authorisation is not required.
`CorrectedMerchantDetails`	The merchant location/description was incorrect in the first presentment. With the corrected details authorisation is not required.
`CorrectTransactionAmount`	The TID shows that the amount was processed correctly
`CorrectTransactionAmountSms`	The TID shows that the amount was processed correctly
`CorrectTransactionCurrency`	Correct transaction currency provided
`CorrectTransactionDate`	Correct transaction date provided
`CreditOrCancellationPolicyProperlyDisclosed`	The merchant can substantiate that the credit or cancellation policy was properly disclosed to the cardholder at the point of interaction.
`CreditPreviouslyIssued`	Credit previously issued
`CVC2ValidationProgram`	CVC 2 Validation Program (US Region Merchants only)
`DeficiencyCorrected`	Deficiency Corrected
`DisputedSurcharge`	Disputed Surcharge
`DisputedSurchargeIncorrectProratedCalculation`	Disputed Surcharge - Incorrect Pro-rated Calculation
`DuplicateChargeback`	Duplicate Chargeback
`FaceToFace`	No Conflicting Information in Authorization and Clearing Message.
`FaceToFaceConflictingMessages`	Conflicting Information in Authorization and Clearing Message
`GoodsNotReturned`	The cardholder did not return the goods to the merchant.
`GoodsOrServicesProvided`	The goods or services were provided by the merchant or there was a delay in delivery.
`GoodsRepairedOrReplaced`	The merchant documents that the goods were repaired or replaced.
`GoodsWereAsDescribed`	The merchant can proof that the goods were delivered as described
`IdentifiedAddendum`	Addendum transaction is cardholders responsibility
`IllegibleDocumentationReceived`	The provided documentation is illegible to the point where it cannot be established that the chargeback is valid
`IncorrectTransactionDate`	The acquirer must document that the transaction was authorized but was processed with an incorrect transaction date.
`IncreasedTransactionAmount`	The increased debit to the account is valid.
`InvalidARD`	Invalid Acquirer Reference Data on chargeback; documentation was provided or not required
`InvalidChargeback`	The issuers chargeback was invalid
`InvalidChargebackBundling`	CB bundling invalid for this reason code or MCC code
`InvalidChargebackSms`	The issuer's chargeback was invalid for example non-supporting documentation
`InvalidDE72CB`	Invalid member message text (DE 72). Not in format CBMMDDYY ARD XXXXXXXXXXXXXXXXXXXXXXX
`InvalidDE72MultipleTransactions`	Invalid member message text (DE 72). Not in format MULTIPLE TRANSACTIONS NNN.
`InvalidDE72RPCS`	Invalid member message text (DE 72). Not in format RPCS MMDDYY.
`IssuerAuthorisedTransaction`	Online authorized transaction with no valid EMV chip card
`JustifiedDelayedPresentment`	Justified delayed presentment
`LiabilityShiftFullUCAF`	MasterCard SecureCode SL2 (Global Liability Shift)
`LiabilityShiftMerchantUCAF`	MasterCard SecureCode SL1 (Merchant-Only Liability Shift)
`MissingInformation`	Provide missing or illegible information
`MultipleAuthorisations`	Multiple Authorisations were obtained with a authorisation amount greater or equal to the captured amount.
`NoARDprovidedInMessageText`	The issuer did not provide the ARD of the second transaction in the DE 72
`NoAuthorisationRequiredManualImprint`	The card data was captured via a manual imprint
`NoAuthorisationRequiredNotX2X`	Service code on the card was not X2X.
`NoAuthorisationRequiredOffline`	Completed at a point-of-sale (POS) device that did not have both online and magnetic stripe-read capability.
`NonReceiptOfRequiredDocuments`	Issuer did not provide the required documents. This reason can only be used between 9-45 days after the dispute.
`NoShowTransaction`	The transaction was the result of Guaranteed Reservation Service
`NotRecurring`	Transaction was not a recurring transaction.
`NotReportedToSafe`	Issuer did not properly report the transaction to SAFE
`OfflineChipTransactionDE55NotProvided`	Chip transaction that required no authentication and DE 55 was not provided
`OfflineChipTransactionDE55Provided`	Chip transaction with DE55 provided in first presentment.
`OnlineChipTransactionDE55NotProvided`	Chip transaction that was authorized online and DE 55 was not provided
`PartialAuthorisation`	The captured amount was partially authorised. The chargebacked amount is greater than the amount that was not authorised
`PastChargebackTimeLimit`	Past Chargeback Time Limit
`PaymentByOtherMeans`	The merchant can provide an explanation that substantiates the validity of the transaction charged.
`PayPassTransaction`	PayPass transaction below chargeback protection amount
`PINTransaction`	PIN was present
`PosDeviceFailure`	Transaction was under floor limit and there was a POS failure at the time of purchase
`ProofOfCardPresenceAndSignatureChipNoPIN`	Card was present and Chip was used
`ProofOfCardPresenceAndSignatureLossTheftOrDamage`	Card was present and a signed terminal receipt is available. The transaction involves loss, theft, or damage. The merchant should provide the receipt containing specially the items that were additionally billed.
`ProofOfCardPresenceAndSignatureMasterCardCorporateFleetCard`	Card was present and a signature exists for a Corporate Fleet Card transaction but no PIN provided.
`ProofOfCardPresenceAndSignatureNotMasterCardWorldWideNetwork`	Card was present and a signature exists for a transaction that was not processed via the MasterCard Worldwide Network.
`ProofOfCardPresenceAndSignatureWithoutTerminalReceipt`	Card was present and documentation is available to proof this.
`ProofOfCardPresenceAndSignatureWithTerminalReceipt`	Card was present and a signed terminal receipt is available.
`PurchaseProperlyPosted`	The issuer claimed that the transaction was not for an installment billing and transaction was properly identified as an installment transaction in the authorization request.
`QPSTransaction`	For a properly identified QPS transaction equal to or less than the chargeback protection amount.
`RecurringTransactionsCompellingEvidence`	Non face-to-face Recurring Transaction
`RecurringTransactionsCompellingMerchantEvidence`	Non face-to-face Recurring Transaction Compelling Merchant Evidence
`ScanningError`	The provided documentation is incomplete or is about a wrong transaction probably due to a scanning error.
`ServicesProvidedAfterCancellation`	The merchant has provided services after the cancellation data which have been used by the cardholder.
`ShippedToAVS`	Address Verification Service (AVS)
`ShippedToAVSAdditionalInformation`	Address Verification Service (AVS) Additional Information
`SupplyDefenseMaterial`	Defense Material that remedies the chargeback
`SuspiciousTransaction`	The acquirer must document that the issuer was advised that the transaction was suspicious.
`TechnicalFallback`	The transaction was the result of a technical fallback
`TelecomFailure`	Transaction was under floor limit and there was a telecom failure at the time of purchase
`Telex`	The acquirer proves that the card acceptor received authorization for the transaction amount or greater as a result of a telex to the issuer.
`TransactionNotPOS`	Transactions was not a POS transaction
`TwoDifferentTIDsATM`	Two different TIDs with the same card number are present (ATM)
`TwoDifferentTIDsPOS`	Two different TIDs with the same card number are present (POS)
`TwoPINTransactions`	A PIN was present for one or both transactions
`TwoPriorFraudChargebacks`	Two or More Previous Fraud-related Chargebacks
`UnreasonableAmount`	The cardholder agreed to an amount range as reasonable and the transaction amount did not exceed this amount range.

Visa

defenseReasonCode	Description
`AdditionalInformation`	Additional Information
`ATMtransaction`	ATM Transaction
`AuthorisedTransaction`	Authorised Transactions
`AutomaticRFIresponse`	Response to a Request for Information (Automatic Response)
`CardholderNotReplied`	Cardholder was notified but did not reply.
`CardholderParticipated`	Compelling evidence that the cardholder participated in the transaction.
`CardHolderParticipatedBasedOnCVV2`	CardHolderParticipated based on CVV2
`CardholderRenewedMembership`	Cardholder renewed membership after cancellation.
`CardNotOnExceptionFile`	The Account Number was not listed on the Exception File.
`CardNotPresentRFIresponse`	Normal response to a Request for Information
`CardPresentFraud`	Card Present Fraud
`CreditOrCancellationPolicyProperlyDisclosed`	The merchant can substantiate that the credit or cancellation policy was properly disclosed to the cardholder at the point of interaction.
`CreditPreviouslyIssued`	Credit previously issued
`DuplicateChargeback`	Duplicate Chargeback
`EmergencyPaymentAuthorizationService`	The transactions was authorized through the Emergency Payment Authorization Service.
`EMVLiabilityShift`	EMV Liability Shift
`GoodsNotReturned`	The cardholder did not return the goods to the merchant.
`GoodsRepairedOrReplaced`	The merchant documents that the goods were repaired or replaced.
`GoodsWereAsDescribed`	The merchant can proof that the goods were delivered as described.
`InvalidCancellationCode`	Invalid Cancellation Code.
`InvalidChargeback`	The issuers chargeback was invalid for example non-supporting documentation.
`InvalidReasonCodeForMCC`	Invalid Reason Code for MCC
`LiabilityShiftFullUCAF`	Global Liability Shift
`LiabilityShiftMerchantUCAF`	Merchant-Only Liability Shift
`MerchandiseNotCounterfeit`	Merchandise was not counterfeit
`MerchandiseReceived`	Merchandise received by shopper.
`NotCancelled`	Cardholder did not cancel the transaction.
`NotNotified`	Acquirer or merchant not notified of cancellation.
`NotPaidByOtherMeans`	Additional Information
`PastChargebackTimeLimit`	Services provided to shopper.
`PINTransaction`	PIN was present.
`PresentmentWithinTimeLimit`	Transaction was presented within the given time limit.
`PreviousTransactionNotChargebacked`	Previous transaction was not chargebacked.
`PreviousTransactionNotChargebackedARNprovided`	Previous transaction was not chargebacked (ARN present to match)
`ProofOfCardPresenceAndSignatureWithoutTerminalReceipt`	Card was present and documentation is available to proof this.
`RecurringTransactionsCompellingEvidence`	Non face-to-face Recurring Transaction
`RecurringTransactionsCompellingMerchantEvidence`	Non face-to-face Recurring Transaction Compelling Merchant Evidence
`SaleTermsNotMisrepresented`	Terms of sale were not misrepresented.
`ServicesProvided`	Services provided to shopper.
`SupplyDefenseMaterial`	Defense Material that remedies the chargeback.
`TimeshareTransactionCancellationPeriodExpired`	Transaction was not cancelled within 14 calendar days of the contract date or receipt date of the contract or related documents.
`TransactionAuthorisedOnline`	Transaction Authorised Online
`TwoDifferentMagStripeTelCalls`	Proof that time of call for each Magnetic-Stripe Telephone call differs.
`TwoDifferentTIDs`	Two different TIDs with the same card number are present.

defenseDocumentTypeCode

American Express

defenseDocumentTypeCode	Description
`AmexFaxCover`	A cover page that will be sent with each dispute.
`AlternativeDefenseMaterial`	Defense Material
`CreditPreviouslyIssued`	Reference and date of refund
`DateMerchandiseShipped`	Date of merchandise shipment
`DefenseMaterial`	Defense Material that remedies the chargeback.
`DuplicateChargeback`	First chargeback reference number and date of original chargeback.
`GoodsWereAsDescribed`	Proof showing that the goods were delivered as described.
`MerchandiseDescription`	A description of the merchandise or services.
`ProofOfGoodsOrServicesProvided`	Proof showing that the goods or services of the merchant were provided to the cardholder.
`TIDorInvoice`	Copy of the Transaction Identification Document (TID) or invoice

Cielo

defenseDocumentTypeCode	Description
`AcquirerRFItransactionDetails`	Automatically gathered transaction details.
`AlternativeDefenseMaterial`	Defense Material
`CreditPreviouslyIssued`	Data of previously issued credit.
`DefenseMaterial`	Defense Material that remedies the chargeback.
`FlightTicketUsed`	Documentation proving that the airline tickets were used by the cardholder.
`FligthTookPlace`	Documentation proving that the airline rendered the service.
`GoodsNotReturned`	Statement from the merchant stating that the merchant did not receive the goods.
`GoodsRepairedOrReplaced`	Written rebuttal documenting that the goods were repaired or replaced.
`GoodsWereAsDescribed`	Proof showing that the goods were delivered as described.
`MerchandiseDescription`	A description of the merchandise or services.
`PaperAirlineTicket`	Documentation establishing that the cardholder was issued paper airline tickets.
`PastChargebackTimeLimit`	Past Chargeback Time Limit Claim
`ProofOfAbilityToProvideServices`	Proof showing that the merchant is able to provide the services.
`ProofOfGoodsOrServicesProvided`	Proof showing that the goods or services of the merchant were provided to the cardholder.
`TIDorInvoice`	Copy of the Transaction Identification Document (TID) or invoice.

Discover

defenseDocumentTypeCode	Description
`AcquirerRFItransactionDetails`	Automatically gathered transaction details.
`AlternativeDefenseMaterial`	Defense Material
`CreditPreviouslyIssued`	Reference and date of refund.
`DefenseMaterial`	Defense Material that remedies the chargeback.
`DisclosureAtPointOfInteraction`	Rebuttal or proper disclosure given to the cardholder at the point of interaction.
`DuplicateChargeback`	First chargeback reference number and date of original chargeback.
`GoodsNotReturned`	Statement from the merchant stating that the merchant did not receive the goods.
`GoodsRepairedOrReplaced`	Written rebuttal documenting that the goods were repaired or replaced.
`GoodsWereAsDescribed`	Proof showing that the goods were delivered as described.
`InvalidChargeback`	Documentation to support that the chargeback is remedied or invalid.
`MerchandiseDescription`	A description of the merchandise or services.
`OriginalAmount`	The original transaction amount if the disputed transaction represents partial shipment.
`PaymentByOtherMeans`	An appropriate explanation and documentation showing two separate transactions.
`PositiveAVS`	Documentation of positive AVS response X or Y.
`ProofOfAbilityToProvideServices`	Proof showing that the merchant is able to provide the services.
`ProofOfGoodsOrServicesProvided`	Proof showing that the goods or services of the merchant were provided to the cardholder.
`ProofOfRetailSaleRatherThanCredit`	A copy of the TID as proof that the transaction involved a retail sale rather than a credit.
`RetrievalRequestFulfilled`	Automatically generated proof that a retrieval request has been fulfilled.
`ShippedToAVS`	Documentation that shows the merchandise was sent to the AVS-confirmed billing address.
`ShipToAddress`	“Ship to” address (if applicable)
`TIDorInvoice`	Copy of the Transaction Identification Document (TID) or invoice.
`TwoDifferentTIDs`	Copies of two different TIDs.

Mastercard

defenseDocumentTypeCode	Description
`AcquirerMemberMessageText`	DE 72 (Data Record)
`AcquirerRFItransactionDetails`	Automatically gathered transaction details.
`AddendumDocumentation`	Documentation showing that transaction is addendum to previous transaction
`AdditionalTransactions`	Additional transactions connected with the disputed flight
`AlternativeDefenseMaterial`	Defense Material
`ARDnotProvided`	ARD NOT PROVIDED
`ATMSupportingDocuments`	See Appendix A of Chargebacks – Mastercard Europe ATM Transactions
`AuthorisationLog`	Authorization log or documentation showing the authorisation took place.
`AuthorisedTransaction`	TRANS AUTHORIZED MMDDYY NO.NNNNNN
`CancellationNeverAccepted`	Rebuttal stating that the cancellation was never accepted.
`CardholderIdentification`	Identification documentation showing a link to the cardholder.
`CardPresent`	Proof of card presence and cardholder signature.
`ChargebackRemedied`	Documentation showing that chargeback was remedied. Other defenses are not applicable.
`ChipLiabilityNotApplicable`	CHIP LIABILITY NA
`ChipLiabilityShift`	AUTH MMDDYY NNNNNN
`ChipTransactionReportedToSAFE`	Documentation that supports the second presentment from the Acquirer's Loss Data File, the Acquirer Loss Data Report, or the Acquirer Transaction Data Report via Fraud Reporter.
`CompellingEvidence`	COMP EVID
`CorrectedMcc`	MCCNNNN
`CorrectedMerchantDetails`	Correct card acceptor location/description
`CorrectTransactionCurrency`	Documentation proving the correct currency was provided.
`CreditPreviouslyIssued`	Reference and date of refund
`DE55`	DE 55 and related data
`DefenseMaterial`	Defense Material that remedies the chargeback.
`DisclosureAtPointOfInteraction`	Rebuttal or proper disclosure given to the cardholder at the point of interaction.
`DuplicateChargeback`	First chargeback reference number and date of original chargeback.
`FlightManifest`	Flight manifest showing the cardholder's name.
`FlightTicket`	Flight Ticket or boarding pass showing the cardholder's name.
`FlightTicketAtBillingAddress`	Proof of receipt of the flight ticket at the cardholder's billing address.
`FlightTicketUsed`	Documentation proving that the airline tickets were used by the cardholder.
`FligthTookPlace`	Documentation proving that the airline rendered the service.
`FormalAffidavitOfFailure`	Formal affidavit of telecommunication failure or POS device failure from the merchant.
`FrequentFlyer`	Credits of frequent flyer miles for the flight showing connection to the cardholder.
`GoodsNotReturned`	Statement from the merchant stating that the merchant did not receive the goods.
`GoodsRepairedOrReplaced`	Written rebuttal documenting that the goods were repaired or replaced.
`GoodsWereAsDescribed`	Proof showing that the goods were delivered as described.
`IncorrectTransactionDate`	TRANS DATE MMDDYY NOT MMDDYY
`IncreasedTransactionAmount`	Documentation to support that the cardholder is responsible for the disputed amount.
`InvalidChargeback`	Documentation to support that the chargeback is remedied or invalid.
`IssuerAuthorisedTransaction`	INV SERVICE CODE X
`LiabilityShiftFullUCAF`	AUTH MMDDYY/NNNNNN SL 2
`LiabilityShiftMerchantUCAF`	AUTH MMDDYY/NNNNNN SL 1
`MerchandiseDescription`	A description of the merchandise or services
`MerchantProofOfRecurringTransaction`	Merchant Proof of recurring transactions with no previous chargeback
`MPIdata`	MPI request/response messages
`MultipleAuthorisations`	MULTIPLE AUTHORIZATIONS
`NoAuthorisationRequiredNotX2X`	SC not X2X
`NoAuthorisationRequiredOffline`	POS DEVICE NOT ONLINE
`NotX2X`	Proof that the service code was not X2X.
`OfflineChipTransactionDE55NotProvided`	CHIP TRANSACTION
`OfflineChipTransactionDE55Provided`	DE 55 PREVIOUSLY PROVIDED
`OnlineChipTransactionDE55NotProvided`	TRANS AUTHORIZED MMDDYY NNNNNN
`OriginalAmount`	The original transaction amount if the disputed transaction represents partial shipment.
`PaperAirlineTicket`	Documentation establishing that the cardholder was issued paper airline tickets.
`PartialAuthorisation`	$$$$$$ CODE XXXXXX MMDDYY
`PassengerIdentification`	Passenger identification documentation showing a link to the cardholder.
`PaymentByOtherMeans`	An appropriate explanation and documentation showing two separate transactions.
`PayPassTransaction`	PAYPASS NNNNNN MMDDYY
`PINTransaction`	PIN MMDDYY NNNNNN
`PosDeviceFailure`	POS DEVICE FAILURE
`PositiveAVS`	Documentation of positive AVS response X or Y
`PrintedSignedTerminalReceipt`	A printed, signed terminal receipt.
`ProofOfAbilityToProvideServices`	Proof showing that the merchant is able to provide the services
`ProofOfAccountTakeover`	Documentation proving that the transaction resulted from an account takeover
`ProofOfAttendedPOSTerminal`	Documentation that show that the transaction occurred on an attended POS terminal
`ProofOfCardPresenceAndSignatureChipNoPIN`	CHIP TRANSACTION
`ProofOfCardPresenceAndSignatureWithTerminalReceipt`	TRANS AUTHORIZED MMDDYY NO.NNNNNN
`ProofOfGoodsOrServicesProvided`	Proof showing that the goods or services of the merchant were provided to the cardholder.
`ProofOfNoShow`	Documentation showing reservation was made by cardholder.
`ProofOfRecurringTransaction`	Description of goods with evidence of recurring transaction
`ProofOfRetailSaleRatherThanCredit`	A copy of the TID as proof that the transaction involved a retail sale rather than a credit.
`QPSTransaction`	INVALID REASON CODE FOR QPS
`ReasonForReturn`	Put reason in DE72 Data Record
`ShippedToAVS`	Documentation that shows the merchandise was sent to the AVS-confirmed billing address.
`ShipToAddress`	“Ship to” address (if applicable)
`SuspiciousTransaction`	ADVISED SUSPICIOUS MMDDYY
`TechnicalFallback`	TECHNICAL FALLBACK MMDDYY NNNNNN
`TelecomFailure`	TELECOM FAILURE
`Telex`	CALL REFERRAL AUTH MMDDYY NNNNNN
`TIDorInvoice`	Copy of the Transaction Identification Document (TID) or invoice
`TransactionNotPOS`	XXXXXX TRANSACTION
`TwoDifferentTIDs`	Copies of two different TIDs
`TwoPINTransactions`	PIN MMDDYY NNNNNN MMDDYY NNNNNN
`TwoPriorFraudChargebacks`	FNS/NN MMDDYY NN MMDDYY AUTH MMDDYY
`UnreasonableAmount`	Documentation supporting the merchants claim.

Visa

defenseDocumentTypeCode	Description
`AcquirerMemberMessageText`	Acquirer Clearing Message Text
`AcquirerRepresentmentForm`	Acquirer Representment Form
`AcquirerRFItransactionDetails`	Automatically gathered transaction details.
`AlternativeDefenseMaterial`	Defense Material
`AuthorisedTransaction`	Authorised Transactions
`CardholderNotReplied`	A document proving the Cardholder was notified but did not reply
`CardholderRenewedMembership`	Documentation showing cardholder renewed membership after cancellation
`CardPresent`	Proof of card presence and cardholder signature
`ChipLiabilityShift`	Chip Liability Shift
`CompellingEvidence`	COMP EVID
`CreditPreviouslyIssued`	Reference and date of refund
`DateMerchandiseShipped`	Date of merchandise shipment
`DefenseMaterial`	Defense Material that remedies the chargeback.
`DisclosureAtPointOfInteraction`	Rebuttal or proper disclosure given to the cardholder at the point of interaction.
`DuplicateChargeback`	First chargeback reference number and date of original chargeback
`EvidenceOfCardholderParticipation`	Compelling evidence that the cardholder participated in the transaction.
`GoodsNotReturned`	Statement from the merchant stating that the merchant did not receive the goods.
`GoodsRepairedOrReplaced`	Written rebuttal documenting that the goods were repaired or replaced.
`GoodsWereAsDescribed`	Proof showing that the goods were delivered as described.
`InvalidCancellationCode`	Explanation of invalid cancellation code.
`InvalidChargeback`	Documentation to support that the chargeback is remedied or invalid.
`MerchandiseDescription`	A description of the merchandise or services.
`MerchandiseNeverReturned`	Rebuttal stating that the merchandise was never returned
`MerchandiseNotCounterfeit`	Documentation to support the Merchant's claim that the merchandise was not counterfeit
`MerchantProofOfRecurringTransaction`	Merchant Proof of recurring transactions with no previous chargeback.
`MPIdata`	MPI request/response messages
`NotCancelled`	Documentation showing services was not cancelled.
`NotChargebacked`	Documentation showing transaction was not chargebacked.
`NotChargebackedAuto`	Documentation showing transaction was not chargebacked (automatic response).
`NotNotified`	Documentation showing acquirer and merchant were not notified of cancellation of membership.
`PINTransaction`	Proof of PIN transaction
`PresentmentWithinTimeLimit`	CORRECT TRAN DATE MMDDYY
`ProofOfCardPresenceSignatureOrChipPIN`	Proof of card presence and cardholder signature
`ProofOfGoodsOrServicesProvided`	Proof showing that the goods or services of the merchant were provided to the cardholder.
`ProofOfRecurringTransaction`	Proof of recurring transactions with no previous chargeback.
`ReasonForReturn`	Put reason in member message text.
`ReturnedMerchandiseNotReceived`	RETURNED MDSE NOT RECEIVED
`SaleTermsNotMisrepresented`	Documentation to prove that the terms of sale of the merchandise or services were not misrepresented.
`TIDorInvoice`	Copy of the Transaction Identification Document (TID) or invoice.
`TwoDifferentTIDs`	Copies of two different TIDs.