Chargebacks
dba.idchargeback.idcase.id for a specific chargeback.idHow to use our Chargeback system
id.Every new case that arrives for a specific chargeback id updates the chargeback information and gets listed in the cases object.IMPORTANT A specific chargeback.idcan have more than one cases associated with it, as new information can arrive.
We suggest the current flow:
1.
chargeback.id has attention=Yes, you can dispute it and upload evidence.2.
chargeback.id, this will list one or more cases associated with the chargeback. Make note of the case.id that has attention=Yes.3.
4.
case.id for a specific chargeback.id5.
6.
chargeback.id| Fields | Description | Type |
|---|---|---|
| id | The unique ID that is assigned by our system to every chargeback | Integer |
| dba | Object | Object |
| dba.id | The ID of the DBA | Integer |
| type | Chargeback or Retrieval | ENUM |
| amount | The amount of the retrieval or chargeback. This is not always equal to the amount of the transaction. | Number |
| card | Object | Integer |
| card.brand | Card Brand | String |
| card.number | Card Number | String |
| date | Object | Object |
| date.posted | The post date as reported by the issuer. | Date |
| date.loaded | The date the retrieval request or chargeback was loaded in the system. | Date |
| date.lastLoaded | The date of the last case loaded in the system for the chargeback. | Date |
| date.disputed | Date when the dispute was submitted. | Date |
| reason | Object | Object |
| reason.code | Chargeback reason code | String |
| reason.description | Chargeback reason description | String |
| fraud | Yes or No | ENUM |
| attention | Yes or No If the merchant's attention is required. | ENUM |
| status | Processed, Won, Lost | ENUM |
Modified at 2025-08-09 05:39:42