Merchant Management API Specification

Get merchant chargebacks by their state. Chargebacks can either be open (actionable), pending (in review), or closed. The date range for the query must be within the last 18 months. If the toDate parameter is not provided, it defaults to the current date.

Get notes related to a Request For Clarity (RFC). An RFC is a way for a bank to obtain more transaction data from the merchant before proceeding with a formal chargeback. The goal is to resolve the issue, prevent an unnecessary dispute, and avoid costly chargeback fees for the merchant.

Add notes to a Request for Clarity (RFC). An RFC is a way for a bank to obtain more transaction data from the merchant before proceeding with a formal chargeback. Adding notes can help provide clarity and potentially resolve the issue. The goal is to prevent an unnecessary dispute and avoid costly chargeback fees for the merchant.

Get RFCs that are in progress. During this time, the involved parties may add notes or documents to the RFC in an effort to resolve the issue before a formal chargeback is initiated. If the RFC is not resolved within the specified timeframe, it may escalate to a chargeback. Merchants should monitor open RFCs closely and provide any requested information promptly to avoid unnecessary chargebacks.

Get closed RFCs associated with a merchant. Closed RFCs are those that have been resolved, either by providing the requested information or by escalating to a formal chargeback if the issue could not be resolved.

Get notes related to a chargeback. Chargeback notes provide additional context and information about the chargeback case, which can be useful for both merchants and banks in understanding the dispute and its resolution. These notes may include details about communications, evidence provided, or any other relevant information pertaining to the chargeback process.

Add notes to a merchant chargeback. Adding notes can help provide additional context or information related to the chargeback, which may assist in its resolution. Notes can include details such as communication with the customer, evidence provided, or any other relevant information. These notes become part of the chargeback record and can be referenced during the dispute resolution process.

Get a document associated with a chargeback. The document could provide supporting information related to the chargeback case. The document data is returned as a Base64 encoded string. You will need to decode the string to retrieve the original document content.

Get a document associated with an RFC. The document could provide supporting information related to the RFC case.

Get the list of documents for a merchant chargeback. These documents may include supporting information related to the chargeback case. If no documents are found, an empty list will be returned.

Attach a file to a merchant chargeback. This document could provide additional information related to the chargeback case. The document should be encoded in Base64 format. Ensure that the document size does not exceed the maximum allowed limit and that the file type is supported.

Get the list of documents for a merchant RFC. These documents may include supporting information related to the RFC case.

Attach a file to a merchant RFC. This document could provide additional information related to the RFC case.

Submit a merchant RFC for review. This action indicates that the merchant has provided all necessary information and is ready for the RFC to be evaluated. Once submitted, the RFC will be reviewed by the appropriate team to determine the next steps. Note that once an RFC is submitted for review, it cannot be modified or withdrawn. Ensure that all required documentation and information are included before submitting.

Accept a merchant chargeback. This action indicates that the merchant agrees with the chargeback and will not contest it further. By accepting the chargeback, the merchant acknowledges the validity of the dispute and agrees to the associated financial implications. Once a chargeback is accepted, it cannot be reversed, and the funds will be adjusted accordingly. Ensure that the decision to accept the chargeback is made after careful consideration of all relevant information and documentation.

Rebut a merchant chargeback. This action indicates that the merchant disputes the chargeback and wishes to contest it further. Provide the reason for the rebuttal in the request body. By rebutting the chargeback, the merchant initiates a review process where additional information and documentation may be required to support their position. Ensure that all relevant evidence is gathered and submitted to strengthen the rebuttal case. Once a chargeback is rebutted, it will be reviewed by the appropriate team to determine the outcome of the dispute.

Get details for a merchant chargeback. This endpoint retrieves comprehensive information about a specific chargeback associated with a merchant. The details provided include transaction information, chargeback reason, amounts involved, and current status of the dispute. This information is crucial for merchants to understand the context of the chargeback and to take appropriate actions if necessary. Ensure that you have the correct merchant ID and chargeback GUID to access the relevant details.

Get details for a merchant RFC. This endpoint retrieves comprehensive information about a specific Request for Chargeback (RFC) associated with a merchant. The details provided include transaction information, RFC reason, amounts involved, and current status of the dispute. This information is crucial for merchants to understand the context of the RFC and to take appropriate actions if necessary. Ensure that you have the correct merchant ID and RFC GUID to access the relevant details.

Submits authorization data, such as a digital signature, for a merchant chargeback. This endpoint allows merchants to provide the necessary authorization information required to process a chargeback. The authorization data should be formatted as a valid JSON string and may include details such as the merchant's digital signature or other relevant authorization credentials. By submitting this information, merchants can ensure that their chargeback cases are properly documented and authorized for further processing. It is important to ensure that the authorization data is accurate and complete to avoid any delays in the chargeback resolution process.