API vs manual
This guide compares chargebacks via API and chargebacks handled manually.
Chargebacks via API
- Automated integration: API chargeback requests involve automated communication between the issuer's systems and the payment network through an API. This integration allows for seamless and programmable interaction, reducing manual intervention.
- Efficiency and speed: API based chargeback requests are typically faster and more efficient than manual processes. They enable real-time or near-real-time communication, contributing to quicker dispute resolution.
- Structured data exchange: the use of APIs facilitates structured data exchange, ensuring that the chargeback request includes all required information in a standardized format. This structured approach enhances accuracy and reduces errors.
Paymentology chargeback APIs
Paymentology chargeback APIs are only applicable for Mastercard programs. These APIs trigger calls to Mastercom. Mastercom API specification and functionality is available here.
| API | Description |
|---|---|
| Acknowledge chargeback | Acknowledges a second presentment. |
| CB image status | Retrieves the processing status of a chargeback. |
| Cancel chargeback | Cancels a chargeback. |
| Chargeback document | Retrieves documents associated to any type of chargeback. |
| Claim detail | Retrieves details of an existing claim, including any cases with which the claim is associated. |
| Create claim V2 | Creates a claim, which is required prior to creating a chargeback. |
| Load data for CB | Obtains information about a potential first chargeback prior to creating the chargeback. |
| Request chargeback V2 | Creates a chargeback (claim must have been created). |
| Transaction search | Finds information about the original transaction. This information may be used in the chargeback process. |
| Update chargeback | Updates an existing chargeback. |
Chargebacks handled manually
- Human intervention: manual chargeback requests involve human-initiated processes where individuals within the issuer's organization manually submit the necessary documentation and information to the payment network to initiate a chargeback.
- Time-consuming: compared to API requests, manual chargeback processes are often more time-consuming due to the manual handling of paperwork, documentation, and communication. This may result in longer resolution times for disputes.
- Potential for errors: manual processes may be more susceptible to errors, such as incomplete or inaccurate information being submitted. This can lead to delays and challenges in the chargeback resolution process.
Updated 7 months ago