1. Chargebacks
  • Developer Docs Ecuador 🇪🇨
  • Online Payments
    • Release Notes
    • Card Payments
      • Request a card token
      • Make a charge or deferred charge
      • Refund a transaction
      • Void a transaction
      • Request deferred options
      • Validate OTP
      • Bin Info V2
      • Bin Info
    • One Click and Scheduled Payments
      • Request a recurring charge token
      • Create a recurring charge
      • Update recurring charge card data
      • Make an One-click payment
      • Cancel a recurring charge
      • Update a recurring charge
      • Add a temporary charge or discount
      • Get recurring charge Info
    • Chargebacks
      • Query chargebacks
        POST
      • Request chargeback export
        POST
    • Subscription Transactions
      • Get subscription transactions
    • Transfer in
      • Request a Transfer In token
      • Init Transaction
      • Get Status
    • Cash in
      • Request a cash in token
      • Init Transaction
      • Update a cash in transaction
      • Transaction Status
      • Delete a cash in transaction
    • Smartlinks
      • Create a Smartlink
      • Update a Smartlink
      • Get a Smartlink
      • Delete a smartlink
    • Analytics
      • Get transactions list v1
      • Get transactions list v2
    • Status
      • Get gateway status
      • Get platform status
    • Commissions
      • Get Commission Configuration
    • Payment Credentials
      • Create a credential
      • Search credentials
      • Activate or deactivate
      • Delete credential
      • Update credential
      • Regenerate a credential
      • Advanced search
    • Payment Button
      • Create a payment button
    • Settlement
      • Query settlement
  • Appian - Submerchant Register
    • Submerchant Validation in Batch
    • Query submerchant status by requestId/submerchantId
    • Get submerchantIds
    • Get credentials for submerchants
  • Schemas
    • threeDomainSecure
    • webhooks
    • Card-old
    • Channel
    • Amount-cash-in
    • ChargebackListResponse
    • StatusComponent
    • SettlementDateRangeRequest
    • SubscriptionTransactionsResponse
    • Card
    • currency
    • networkToken
    • ChargebackItem
    • ErrorResponse
    • SettlementTicketRequest
    • SubscriptionTransaction
    • Subscription
    • Amount
    • ErrorResponse400
    • SettlementResponse
    • extraTaxes
    • Country
    • ErrorResponse401
    • SettlementRecord
    • Language
    • Deferred
    • ErrorResponse403
    • Metadata
    • payment_method
    • ErrorResponse500
    • ContactDetails
    • documentType
    • orderDetails
    • Shipping Address
    • Billing-Address
    • payment_submethod
    • SubscriptionUpdate
    • product
    • SubscriptionAdjustmentRequest
    • threeDomainSecure
    • webhooks
    • headers
    • webhooksChargeback
    • citMit
    • network
    • binInfo
    • messageFields
    • UnexpectedErrorResponse
    • ExternalReferenceId
    • transactionType
BienvenidaPerú 🇵🇪México 🇲🇽Ecuador 🇪🇨
Colombia 🇨🇴Chile 🇨🇱
BienvenidaPerú 🇵🇪México 🇲🇽Ecuador 🇪🇨
Colombia 🇨🇴Chile 🇨🇱
  1. Chargebacks

Request chargeback export

POST
/data/v1/chargebacks/export
Initiates the asynchronous generation of a chargeback export file.
Upon receiving the request, the system immediately returns a 200 OK response with a unique id. Once the file has been generated and stored, Kushki sends a POST notification to each URL configured in the webhooks array, including the download link and its expiration timestamp.
The request body follows the same structure as POST /data/v1/chargebacks/search, with the addition of the webhooks field.
Note: The download URL is an S3 pre-signed URL valid for 4 hours from the moment of generation. Check expiration_timestamp in the webhook notification before attempting the download.

Webhook security#

To verify that a notification was sent by Kushki and not a third party, validate the following headers included in every webhook call:
HeaderDescription
X-Kushki-IdUnix timestamp (13 digits, milliseconds) of when the notification was sent.
X-Kushki-SignatureHMAC SHA256 signature of private-merchant-id|request|X-Kushki-Id. The signing secret is the merchant's own private-merchant-id.
To validate the signature on your side, compute:
HMAC-SHA256({private-merchant-id}, "{private-merchant-id}|{request}|{X-Kushki-Id}")
And compare the result with the value received in X-Kushki-Signature. If they match, the notification is authentic.

Request

Authorization
API Key
Add parameter in header
private-merchant-id
Example:
private-merchant-id: ********************
or
Header Params

Body Params application/jsonRequired

Examples

Responses

🟢200
application/json
Request accepted. The export has been queued for processing. A webhook notification will be sent to each configured URL when the file is ready for download. Use the returned id to track or report any issues with this request to Kushki support.
Bodyapplication/json

🟠400
🟠401
🟠403
🔴500
Request Request Example
Shell
JavaScript
Java
Swift
cURL
curl --location 'https://api-uat.kushkipagos.com/data/v1/chargebacks/export' \
--header 'private-merchant-id: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
    "filters": {
        "time": {
            "request_date": {
                "from": "2026-01-15",
                "to": "2026-03-15"
            }
        }
    },
    "webhooks": [
        "https://merchant.example.com/webhooks/chargebacks"
    ]
}'
Response Response Example
200 - default
{
    "id": "1339b164-9298-4ea1-a52a-a9c053879194"
}
Modified at 2026-07-22 20:52:01
Previous
Query chargebacks
Next
Subscription Transactions
Built with