Skip to main content
GET
Get Chargeback Actions
The request and response are the same whatever X-API-Version you send. v1, v2 and v3 integrations share these chargeback endpoints.

How answering works

  1. Call this endpoint for the chargeback.
  2. Pick an action (accept, contest or partial_accept) and one of its conditions.
  3. Send that condition’s fields to Respond to Chargeback, each as fields[<name>].
Every chargeback on your payments can be answered here, whichever payment gateway the payment went through. The response shape is always the same, but what is on offer depends on the payment. You will see one of two sets:
  • Accept, or contest with evidence. accept has a single accepted condition that takes nothing. contest has a single contested condition: your remarks (required) and any of the evidence documents, all optional, with min_documents: 1. Attach whichever documents back your case, and at least one.
  • Detailed conditions. Each condition describes the situation that applies, such as product_delivered or already_refunded, and takes its own text fields, true/false fields and documents. partial_accept may be offered too.
Read the conditions from here for each chargeback instead of hard-coding them. actions is empty, and can_respond is false, while your answer is under review or once the chargeback is closed. If EximPe sends the chargeback back to you for more information, its status becomes INSUFFICIENT_DOCUMENT and its actions are offered again.
403 means the chargeback can’t be answered through EximPe yet because its gateway credentials are not set up for your account. Contact EximPe support; retrying won’t change it.

Authorizations

X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Path Parameters

chargeback_id
string
required

EximPe chargeback ID, e.g. CB6358819770.

Response

OK

success
boolean
message
string
data
object