Release Notes#
Discover the latest feature releases, product improvements, and bug fixes for Kushki Card Present — Mexico 🇲🇽.1.
MAJOR — incompatible API changes
2.
MINOR — new backward-compatible functionality
3.
PATCH — backward-compatible bug fixes
IMPROVEMENTS — changes to existing functionality
DEPRECATED — features soon to be removed
REMOVED — removed features
SECURITY — security vulnerabilities
Latest#
1.4.0 — 2026-09-02#
🔖 Fraud Alerts Endpoint#
A new endpoint is now available to query the fraud alert records that VISA and Mastercard make available to Kushki, without waiting for a file to be delivered manually over SFTP.The Query fraud alerts endpoint returns the records of both card network fraud reporting programs — TC40 (VISA) and SAFE (Mastercard). It covers card-present transactions processed through API Raw as well as card-not-present transactions, and it is the same endpoint documented under Online Payments.It supports two query modes: by date range, using from and to with optional brand, country, fraud_type and merchant_id filters, or by transaction identifier, using transaction_arn or transaction_reference. Results are paginated with page and limit.Authentication is at customer level: send your customer private credential in the Private-merchant-id header, and use the merchant_id field to scope the query to specific branches.⚠️ Availability: this report is only available for transactions made with VISA and MASTERCARD cards, and only for Kushki's acquiring.
⛔ Domestic transactions: this report is not available for domestic transactions processed through PROSA.
ℹ️ Date range limit: queries are limited to a maximum of 12 months from the current date, and from and to must use the exact format YYYY-MM-DDThh:mm:ss.
Previous release notes#
1.3.0 — 2026-03-20#
⚖️ Chargebacks API#
Introducing the Chargebacks API — query chargeback information directly via API and request asynchronous exports.POST /data/v1/chargebacks/search — Paginated list of chargebacks with filters by date, status, and type.
POST /data/v1/chargebacks/export — Initiates asynchronous export; Kushki POSTs the download link to your webhook URL when ready.
1.2.1 — 2025-04-02#
Cardless reversals 🇲🇽 (Beta)#
Added support for performing same-day reversals without requiring the physical card.Use client_transaction_id from the original transaction.
Must be requested on the same day, before 22:00 México local time.
Reversal is always for the full transaction amount.
1.2.0 — 2025-02-27#
🇲🇽 MSI (Meses Sin Intereses) — Card Present#
MSI for Card Present is currently in Beta phase for Mexico. Contact the Kushki team to enable this feature.
credit_type: "03" and graceMonths: "00" in the deferred object."deferred": {
"months": "6",
"credit_type": "03",
"graceMonths": "00"
}
Added GET /deferred/v2/bin/{bin} — returns MSI type "03" in the response for eligible BINs.
Cardless operations in Beta for México: omit_card: true supported for captures, reauthorizations, voids, and refunds.
1.1.1 — 2024-11-14#
Updated transaction status for voids and refunds.
1.0.4 — 2024-10-02#
ticket_number added in responses#
ticket_number is now included in all approved transaction responses:Single payments — charges and MSI deferred charges
Two-step payments — preauthorizations, captures, reauthorizations
Voids & Refunds — voids, reverses, and refunds
Query Transactions — transaction search results
1.0.1 — 2024-02-15#
Cardless operations (Beta)#
Added omit_card field for card-free operations across all endpoints.
Added metadata field to attach additional information to any request.
New request examples: GL - Cardless Reauthorization, GL - Cardless Capture, GL - Cardless Void, GL - Cardless Refund.
Updated descriptions for reversal, reauthorization, capture, and void sections.
1.0.0 — 2024-01-18#
🇲🇽 Card Present API for Mexico — General Availability#
Launching the Card Present raw API for Mexico with the following supported operations:Single charge (ICC, MCR, NFC)
MSI deferred charge — Meses Sin Intereses
Pre-authorization and capture
BIN lookup and MSI deferred options
Got a suggestion on this documentation? Contact us.
