Skip to main content
GET
Get Chargeback Actions

How answering works

  1. Call this endpoint for the chargeback.
  2. Pick an action (accept, contest or partial_accept) and one of its conditions: the situation that applies, such as product_delivered.
  3. Send that condition’s fields to Respond to Chargeback, each as fields[<name>].
The same response shape is used for every payment, but the conditions on offer depend on what the payment’s gateway supports. Some payments offer no partial_accept, and the fields of a condition can differ between payments. Read the conditions from here for each chargeback instead of hard-coding them. actions is empty, and can_respond is false, once the chargeback has been answered or closed.
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