Release Notes
Release notes
1.
2.
3.
Types of changes
Latest
1.18.3 - 2026-06-04
fullResponse v3 — Create a recurring charge
"fullResponse": "v3". This version extends the details object in the response with additional subscription data, including validationTicketNumber — the ticket number of the validation charge executed at subscription creation.v3, the Get recurring charge info endpoint also returns validationTicketNumber in its response.⚠️ V3 response stability: The v3response may include new or deprecated fields without prior notice. Always handle unexpected or missing fields gracefully.
Previous release notes
1.18.0 - 2026-04-17
🔖 Platform Status Endpoint
🔖 Subscription Transactions Endpoint
start, end, and size query parameters to scope results to a specific billing period.🔖 Settlement Query Endpoint
startDate, endDate, page, and limit body parameters to scope results to a specific period. Authentication via the private-merchant-id header is required.1.17.2 - 2026-04-07
🔖 New POS Device Fields in Get Transaction List V2
pos_details:pos_user: Device operator username.pos_friendly_name: Friendly display name of the terminal.pos_serial: Device serial number.pos_type: Physical device type. Possible values: COUNTERTOP, MPOS, SMARTPOS, SELF_SERVICE, OTHER.pos_connectivity: Network connectivity type. Possible values: GPRS, WIFI, ETHERNET, DIAL_UP, OTHER.These fields are only returned in card present transactions if they were sent in the original request.
1.17.1 - 2026-03-31
🔖 Transaction Identifier (TID) in Payments API
"franchiseTransactionCode" in the new capabilities array in your charge or preAuth request.capabilities is not sent, transactionIdentifier is not returned in the response — the feature is fully opt-in.charge, tokenlessCharge, preAuth, tokenlessPreAuth.network.transactionIdentifieris only present in the response whenfranchiseTransactionCodewas included in the request'scapabilitiesarray.
What's new
🔄 Query Chargebacks
POST /data/v1/chargebacks/search — Returns a paginated list of chargebacks associated with the authenticated merchant.transaction_date or request_date (up to a 3-month window; only one date filter can be sent at a time).chargeback_status, country_name, chargeback_type, and chargeback_ticket_code.fields parameter.deadline_representation_date — calculated as request_date + 15 calendar days.deadline_resolution_date — calculated as request_date + 120 calendar days.risk_level — urgency indicator (HIGH, MEDIUM, LOW) based on days remaining until the representation deadline.📤 Request Chargeback Export
POST /data/v1/chargebacks/export — Initiates the asynchronous generation of a chargeback export file.fields as the search endpoint.POST notification to each configured URL with the S3 download link.file_url — pre-signed S3 URL to download the export file.expiration_timestamp — Unix timestamp (13 digits) indicating when the URL expires.request — the original request body sent to the export endpoint (excluding webhooks).private-merchant-id header. Applies to all countries and covers both card present and card not present transactions.Updates
💳 Card Charge V2 / Tokenless Charge / Pre-authorization V2 / Tokenless Pre-authorization
network ObjectReturns the franchise
scheme and the transactionIdentifier.transactionMode is set to initialRecurrence.messageFields ObjectSpecific fields are now returned within
messageFields depending on the card brand when the initialRecurrence condition is met:f62.f2 (derived from field 62, subfield 2).f63 and f15.f63.💳 [Preauth for COF]
1.
initialRecurrenceReference field in the preauth v1 endpoint, which allows linking a subsequent fund reservation (subsequentRecurrence) with its initial transaction.Updates
🧾 💳 Card token requests / Tokenless charge/ Pre-authorization without token / Token for subscriptions enpoints
mvv : The 10-digit Merchant Verification Value assigned by Visa.1.16.6 - 2025-11-05
Updates
💳 Card token requests / Tokenless charge/ Pre-authorization without token / Token for subscriptions
originalTransactionID : The unique identifier of the original transaction, used exclusively in external subscription flows where Kushki processes on-demand charges and tokenization is handled externally.externalSubscriptionID field is present.💳 Card token requests / Tokenless charge/ Pre-authorization without token / Token for subscriptions
card.cryptogram — Cryptographic value associated with network tokens.isNetworkToken (boolean) — Indicates whether the card number provided is a network token.networkToken (object) — Contains additional information required for network token transactions (e.g., deviceType, requestorId, source, walletId, authenticationLevel).1.16.5 - 2025-10-27
🚀 New Installment Type Available in Chile: "Cuotas Comercio" 🇨🇱
creditType with the value 03 within the deferred object.New Response Fields for Merchant Installments (Cuotas Comercio)
| Field | Type | Description |
|---|---|---|
transaction_sub_type | string | Subtype for merchant installment transactions. Possible values: installment → current installment being charged, principal → total financed amount. Applies only to Chile. |
principal_amount | number | Total financed amount under a merchant installment plan. Applies only to Chile in transactions of type installment. |
installment_count | string | Sequence number of the installment being collected. To see the total number of installments, refer to number_of_months. Applies only to Chile. |
principal_ticket_code | string | Ticket number of the principal transaction associated with a merchant installment. Used to link each installment charge back to the original financed transaction. Applies only to Chile. |
1.16.2 - 2025-09-23
Card Payouts now available in Chile 🇨🇱!
1.16.1 - 2025-09-01
Idempotency now available in Online Payments
Idempotency-Key header to help you safely retry requests without the risk of processing the same transaction twice. This is especially useful in cases of timeouts, network issues, or client retries.Where it works
1.15.7 - 2025-05-19
Changes to the get transaction list V2 endpoint
bin_card,last_four_digits.external_reference_id. Available only for card transactions. This is a unique transaction ID generated by the merchant. Click here for further information.1.15.6 - 2025-04-16
New 3DS 100% API Authentication Option
iframe is now supported for the authValidation parameter in the token request of the 3DS 100% API authentication flow.iframe, merchants can embed the authentication experience directly into their website or app, avoiding redirections. It is the merchant's responsibility to listen for iframe events to determine the result of the authentication and trigger the appropriate actions./chargebacks) has also been removed from the public API documentation.1.15.4 - 2025-02-05
New Release: Get Transactions List v2 🚀
What's New?
✅ Enhanced Filtering – Allows filtering by pay-ins and pay-outs for more granular insights.
✅ Optimized Pagination – Returns transactions in descending order, displaying the most recent ones first.
1.15.3 - 2025-02-07
External reference ID now supported in card payments and voids
externalReferenceId in the services: Make a charge or deferred charge, Create payment (tokenless), Void a transaction, Refund a transaction, Authorize payments, Preauthorization (tokenless),and Capture an authorized payment. This will be also returned in the responses of those endpoints, even if the transaction is declined.externalReferenceId has been include in the response of the get transaction list service v1.Metadata object now supported in voids and refunds.
1.15.2 - 2024-11-14
1.15.0 - 2024-05-02
Tokenless operations
CIT,MIT and MAC codes for Kushki Acquirer
citMit.s84, within the messageFields object of the single charge or pre-authorization responses.New parameter added Transaction ARN
transaction_arn has been added to the response in the get transaction list service. Only applies to the Kushki Acquirer model and it may take 1 business day to be reflected.1.14.1 - 2024-02-29
New ERRORS category
ERRORS. Error catalog is now Kushki API errors and ISO error catalog is now ISO errors.Presenting the new format for changes in documentation
Added -> NEWChanged -> IMPROVEMENTSFixed -> FIXUpdated specificationVersion for external 3D Secure authentication engines
threeDomainSecure schema description about 3D Secure version 1 support.Important notice about support for version 1 of 3D Secure!
NOTE: 3DS version 1 will no longer be supported after October 2022. Merchants will need to migrate to version 2 of the protocol to avoid any impact on their transactions.
Important notice about support for version 1 of 3D Secure!
NOTE: Support for 3D Secure 1.0.2 and related technology ended in October 2022. Merchants will need to migrate to version 2 of the protocol to avoid any impact on their transactions.
specificationVersion field in the same model. Now, the allowed values are 2.0.0 and 2.2.0.{
"title": "threeDomainSecure",
"type": "object",
"properties": {
"specificationVersion": {
"description": "3DS protocol version to implement\n\n**NOTE: 3DS version 1 will no longer be supported after October 2022. Merchants will need to migrate to version 2 of the protocol to avoid any impact on their transactions.**",
"type": "string",
"enum": [
"1.0.2",
"2.0.0"
],
"minLength": 5,
"maxLength": 5,
"pattern": "[1-2].[0-9].[0-9]"
}
},
"required": [ "specificationVersion"]
}{
"title": "threeDomainSecure",
"type": "object",
"properties": {
"specificationVersion": {
"description": "3DS protocol version to implement\n\n**NOTE: Support for 3D Secure 1.0.2 and related technology ended in October 2022. Merchants will need to migrate to version 2 of the protocol to avoid any impact on their transactions.**",
"type": "string",
"enum": [
"2.0.0",
"2.2.0"
],
"minLength": 5,
"maxLength": 5,
"pattern": "[1-2].[0-9].[0-9]"
}
},
"required": [ "specificationVersion"]
}1.0.2 of specificationVersion has been deprecated and replaced by version 2.2.0. All references to the previous version in the documentation have been updated.The side menu has been restructured by categories for better navigation
1.14.0 - 2024-01-29
binCard property to binInfo schema.url field in response type 200 for a required 3D Secure authentication.authValidation and callbackUrl fields in the request for 3D Secure authentication.GL - K322 - Autenticación fallida - Sin validación de seguridad of type 400 in the response for a failed 3D Secure authenticationamount, binInfo, created, merchantId, requestAmount, transactionStatus, transactionType properties in 400 type responses.isoErrorCode within details object for declined transactions in Kushki acquiring model.isoErrorCode within details object for declined transactions in Kushki acquiring model.CARD ASYNC - Authorize payments, CARD ASYNC - Capture payments, ASYNC CARD RECURRING CHARGES - Authorize payments and ASYNC CARD RECURRING CHARGES - Capture an authorized payment services in the services by country table.isoErrorCode within details object for declined transactions in Kushki acquiring model.isoErrorCode field.CARD - Void a transaction endpoint to add information about partial voids.CARD - Refund a transaction endpoint to add information about partial refunds.Modified at 2026-07-27 21:48:22