Skip to main content

Client Version History

This table lists client versions and the features included in each version:

Client VersionFeatures
0.23Accepts these card networks in the allowedCardNetworks field for manual card entry: Carnet, Cartes Bancaires, China UnionPay with card verification value (CVV), EFTPOS, ELO, mada, and Meeza.<br>Ordering controls for the allowedPaymentTypes button.<br>De-coupling of PANENTRY from other payment types in the allowedPaymentTypes field.
0.24Support for enabling combo cards in the capture context.<br>Support for eight-digit bank identification numbers (BINs).<br>Support for enabling card save in the capture context.
0.25Addition of Skip Verification next time in the Click to Pay payment flow.<br>Support for Cadastro de Pessoas Física (CPF) in the capture context.
0.26Support for auto-lookup in Click to Pay when an email is included in the capture context.<br>Inclusion of the cardDetails field object in the transient token response.
0.28Support for PayPak as an allowedCardNetwork.<br>Auto-enrollment for Click to Pay in supported markets.<br>Removal of the confirm or continue screen for specific use cases.<br>Static button for Click to Pay flows.
0.30Support for Pakistan locales (en_PK and ur_PK).<br>New look and feel of Unified Checkout in line with EMVCo best practices.
0.31Addition of the data object of the orderInformation field object and pass-through fields.<br>Support for Jaywan as an allowedCardNetwork.<br>Updated the payment details response to return detected card types. Multiple card types are shown when more than one card type is detected.
0.32Support for Korea Cyber Payments (KCP) and UATP in the allowedCardNetwork field.<br>A radio button in the UI for Cartes Bancaires dual-branded cards.
0.33Support for Mobile as Identity Click to Pay lookup.
0.34Additional BIN range for Jaywan card types.
1.0Configure payment options.<br>Configure customer data and payment flow.

Last published: September 29, 2026