Chargeback

Understand the status and reason fields returned in the chargeback object and how to interpret them in your integration.

Understand how to interpret the information returned in the chargeback field when a charge enters a chargeback process.

The chargeback object helps your integration identify the current status of the dispute and the reason provided for it. Use this information to track disputed charges, update internal support flows, and guide reconciliation processes.

Relevant fields

Field	Type	Description
`chargeback.status`	`string`	Indicates the current stage of the chargeback. This is the main field for deciding how your integration should handle the disputed charge.
`chargeback.reason`	`string`	Indicates the reason for the chargeback. Use this field to classify the operational scenario and direct internal analysis.

Chargeback status

The chargeback.status field can return the following values:

Value	Description
`REQUESTED`	Chargeback requested.
`IN_DISPUTE`	Chargeback in dispute.
`DISPUTE_LOST`	Dispute lost.
`REVERSED`	Chargeback reversed.
`DONE`	Chargeback process completed.

Chargeback reasons

The chargeback.reason field can return the following values:

Value	Description
`ABSENCE_OF_PRINT`	Absence of print.
`ABSENT_CARD_FRAUD`	Fraud in card-not-present environment.
`CARD_ACTIVATED_PHONE_TRANSACTION`	Card-activated phone transaction.
`CARD_FRAUD`	Fraud in card-present environment.
`CARD_RECOVERY_BULLETIN`	Card recovery bulletin.
`COMMERCIAL_DISAGREEMENT`	Commercial disagreement.
`COPY_NOT_RECEIVED`	Copy not received.
`CREDIT_OR_DEBIT_PRESENTATION_ERROR`	Credit / debit presentation error.
`DIFFERENT_PAY_METHOD`	Payment by other means.
`FRAUD`	Without cardholder authorization.
`INCORRECT_TRANSACTION_VALUE`	Transaction amount differs.
`INVALID_CURRENCY`	Invalid currency.
`INVALID_DATA`	Invalid data.
`LATE_PRESENTATION`	Late presentation.
`LOCAL_REGULATORY_OR_LEGAL_DISPUTE`	Local regulatory / legal dispute.
`MULTIPLE_ROCS`	Multiple ROCs.
`ORIGINAL_CREDIT_TRANSACTION_NOT_ACCEPTED`	Original credit transaction not accepted.
`OTHER_ABSENT_CARD_FRAUD`	Other fraud - Absent card.
`PROCESS_ERROR`	Processing error.
`RECEIVED_COPY_ILLEGIBLE_OR_INCOMPLETE`	Copy received illegible / incomplete.
`RECURRENCE_CANCELED`	Recurrence canceled.
`REQUIRED_AUTHORIZATION_NOT_GRANTED`	Required authorization not granted.
`RIGHT_OF_FULL_RECOURSE_FOR_FRAUD`	Right of full recourse for fraud.
`SALE_CANCELED`	Merchandise / services canceled.
`SERVICE_DISAGREEMENT_OR_DEFECTIVE_PRODUCT`	Defective or disagreed merchandise / service.
`SERVICE_NOT_RECEIVED`	Merchandise / services not received.
`SPLIT_SALE`	Split sale.
`TRANSFERS_OF_DIVERSE_RESPONSIBILITIES`	Transfer of diverse responsibilities.
`UNQUALIFIED_CAR_RENTAL_DEBIT`	Unqualified car rental debit.
`USA_CARDHOLDER_DISPUTE`	USA cardholder dispute.
`VISA_FRAUD_MONITORING_PROGRAM`	Visa fraud monitoring program.
`WARNING_BULLETIN_FILE`	Warning bulletin file.

Integration behavior

Check whether the chargeback object was returned in the charge.
Read chargeback.status to identify the current stage of the chargeback.
Read chargeback.reason to understand the reason provided.
Update your internal controls using the exact values returned by the API.

Simplified example of a response with chargeback:

{
  "chargeback": {
    "status": "IN_DISPUTE",
    "reason": "COMMERCIAL_DISAGREEMENT"
  }
}

In this example, the charge has a chargeback in dispute (IN_DISPUTE) caused by a commercial disagreement (COMMERCIAL_DISAGREEMENT).

Important notes

Compare status and reason values exactly as returned by the API — do not add spaces, change casing, or translate enums in code.
Use chargeback.status to track the chargeback progress. Use chargeback.reason only to classify the dispute reason.
Handle unmapped values safely, keeping the original value in logs or internal records for later analysis.
Pay close attention to charges with reasons related to fraud, commercial disagreement, service not received, or incorrect amount, as these scenarios typically require operational review.

For more information about Chargeback, click here.