Skip to main content

Version History

The clientVersion field in the session determines which server-side features are available for the session. Use the latest version for access to all features.

The clientVersion value follows semantic versioning (MAJOR.MINOR.PATCH) and is distinct from this guide's "v1" designation, though the two now align: version 1.0 is the first clientVersion release under the v1 API design described in Migrating to v1.

For information on how versioning works, see Versioning.

Client Version Changelog

1.0 (Latest)

  • New SDK entry point: VAS.UnifiedCheckout(session) replaces new Accept(session).unifiedPayments()
  • New checkout lifecycle methods: checkout.mount(target) replaces up.show(options); checkout.unmount() (reversible) and checkout.destroy() (permanent) replace up.hide() and up.dispose()
  • Automatic transaction completion with the autoProcessing option, in addition to manual completion with checkout.complete(token)
  • Full event system added at both the client and checkout level
  • Session creation endpoint changed from /up/v1/capture-contexts to /uc/v1/sessions
  • consumerAuthentication field changed from a boolean to an enum (3DS, NONE, PASSKEY)
  • This is a major version release with breaking changes. See Migrating to v1 for full migration guidance.

0.35

  • Added PASSKEY as a consumerAuthentication option, ahead of the v1 enum conversion
  • Formalized clientVersion pinning support (major and major.minor pinning) in preparation for the v1.0 release
  • Final minor release before the v1.0 major version

0.34

  • Iframes replace pop-ups for payment method flows, reducing browser blocking and improving mobile experience
  • Additional Bank Identification Number (BIN) range for Jaywan cards

0.33

  • Mobile number as identity for Click to Pay accounts
  • Japanese translation updates
  • User experience (UX) captures billing and shipping information when not included in the session

0.32

  • Korea Cyber Payments (KCP) and UATP added to allowedCardNetworks
  • Konbini post-pay reference payment method
  • Radio button UI for Cartes Bancaires dual-branded cards

0.31

  • orderInformation data object and pass-through fields in session
  • tokenCreate field in completeMandate for Token Management Service (TMS) token creation
  • Payer Authentication pass-through fields (challenge codes, data only)
  • Jaywan card network support
  • Multiple detected card types in payment details response
  • Bancontact, DragonPay, MyBank, and Tink Pay By Bank support

0.30

  • iDEAL, Multibanco, and Przelewy24 (P24) support
  • Payer Authentication for Google Pay and Click to Pay
  • Pakistan locales (en_PK, ur_PK)
  • Updated look and feel aligned with EMVCo best practices

0.28

  • Payer Authentication for manual card entry (American Express, Cartes Bancaires, China UnionPay, Discover, ELO, JCB, Mastercard, Visa)
  • Afterpay as allowedPaymentType
  • PayPak as allowedCardNetwork
  • Click to Pay auto-enrollment in supported markets
  • Removal of confirmation screen for specific use cases
  • Static button for Click to Pay

0.26

  • Click to Pay auto-lookup with email
  • cardDetails field in transient token response
  • cardholderAuthenticationStatus field in transient token response
  • Complete mandate support

0.25

  • Skip verification next time option in Click to Pay flow
  • Cadastro de Pessoas Fisicas (CPF) support for Brazil

0.24

  • Combo card support (Brazil)
  • Eight-digit BIN support
  • Card save feature (requestSaveCard)

0.23

  • Additional card networks: Carnet, Cartes Bancaires, China UnionPay (with CVV), eftpos, ELO, J.Crew, mada, Meeza
  • Ordering controls for allowedPaymentTypes button display
  • De-coupling of PANENTRY from other payment types

Last published: September 29, 2026