Notas de versión
Historial completo
1.
2.
3.
Tipos de cambios
Última versión
1.18.3 - 2026-06-04
fullResponse v3 — Crear un cargo recurrente
"fullResponse": "v3". Esta versión amplía el objeto details de la respuesta con datos adicionales de la suscripción, incluido validationTicketNumber — el número de ticket del cargo de validación que se ejecuta al crear la suscripción.v3, el endpoint Get recurring charge info también devuelve validationTicketNumber en su respuesta.⚠️ Estabilidad de la respuesta V3: la respuesta v3puede incluir campos nuevos o deprecados sin aviso previo. Maneja siempre con tolerancia los campos inesperados o ausentes.
Notas de versión anteriores
1.18.1 - 2026-04-28
🔖 Reembolsos parciales para Ecuador
⚠️ Limitaciones importantes: Only one (1) partial refund is allowed per transaction. Subsequent refund requests on the same transaction will be rejected. Partial voids are not supported. Void operations must be applied to the full transaction amount. The time window to request a partial refund varies by processor, ranging from 30 days up to 6 months after the original transaction date. Requests submitted outside this window will be declined.
1.18.0 - 2026-04-17
🔖 Endpoint de estado de la plataforma
🔖 Endpoint de transacciones de suscripción
start, end y size para limitar los resultados a un periodo de facturación concreto.🔖 Endpoint de consulta de liquidación
startDate, endDate, page y limit para limitar los resultados a un periodo concreto. Se requiere autenticación con la cabecera private-merchant-id.1.17.2 - 2026-04-07
🔖 Nuevos campos del dispositivo POS en 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.Estos campos solo se devuelven en transacciones presenciales si se enviaron en la petición original.
1.17.1 - 2026-03-31
🔖 Identificador de transacción (TID) en la API de pagos
"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.transactionIdentifiersolo está presente en la respuesta cuandofranchiseTransactionCodese incluyó en el arraycapabilitiesde la petición.
1.17.0 - 2026-03-20
Novedades
🔄 Query Chargebacks
POST /data/v1/chargebacks/search — Devuelve una lista paginada de los chargebacks asociados al comercio autenticado.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 — Inicia la generación asíncrona de un archivo de exportación de chargebacks.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.1.16.7 - 2025-12-12
Actualizaciones
🧾 💳 Card token requests / Token for subscriptions enpoints
mvv : The 10-digit Merchant Verification Value assigned by Visa.1.16.5 - 2025-10-27
1.16.1 - 2025-09-01
Idempotencia ya disponible en 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.Dónde funciona
1.15.7 - 2025-05-19
Compatibilidad con suscripciones externas en Ecuador
externalSubscriptionId field is now available in Ecuador for the aggregator model. When this field is included, transactions are marked as third-party initiated recurring payments. Click here for more information.Cambios en el endpoint get transaction list V2
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
Nueva opción de autenticación 3DS 100 % API
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
Nueva versión: Get Transactions List v2 🚀
Novedades
✅ 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
El external reference ID ya se admite en pagos con tarjeta y anulaciones
externalReferenceId in the services: Make a charge or deferred charge, Void a transaction, and Refund a transaction. 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.El objeto metadata ya se admite en anulaciones y reembolsos.
1.15.2 - 2024-11-14
1.14.1 - 2024-02-29
Nueva categoría ERRORS
ERRORS. Error catalog is now Kushki API errors and ISO error catalog is now ISO errors.Presentamos el nuevo formato para los cambios en la documentación
Added -> NEWChanged -> IMPROVEMENTSFixed -> FIXspecificationVersion actualizado para los motores de autenticación 3D Secure externos
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.El menú lateral se reorganizó por categorías para navegar mejor
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-09-11 15:43:39