Skip to main content
On this page

The maintained iOS repository and podspec are currently tagged v2.12.6. Pin a release in production and review the upstream artifact before every upgrade. This page summarizes integration-impacting changes verified against repository commit 96501079d01ce15ecaf43d486dd0b2e8c86ab8df; it is not a substitute for the complete repository release history.

Upgrade flow#

01 · inventory
Record the current pin
Capture package source, CocoaPods subspecs, entitlements, fraud frameworks, callbacks, and presentation modes.
02 · resolve
Upgrade dependencies
Change one pin, resolve packages or pods, and inspect the resolved graph and privacy manifests.
03 · exercise
Test on real devices
Cover widgets, wallets, fraud providers, redirects, 3DS, APMs, lifecycle transitions, and accessibility.
04 · release
Monitor outcomes
Compare crashes, callback coverage, provider initialization, and backend payment results with the previous pin.

Notable release lines#

v2.12.x · Modular fraud providers and APM hardeningCurrent verified line
  • v2.12.6 adds Mercado Pago native fraud-fingerprint support and a dedicated CocoaPods subspec.
  • Earlier v2.12.x work modularized supported fraud providers, added runtime dependency handling, and included privacy-manifest updates for applicable vendor frameworks.
  • v2.12.4 adds explicit handling for an APM reference that cannot be generated or displayed.
  • v2.12.2 adds Elements lifecycle events, domain configuration, and consistent userInfo forwarding.

Re-test every enabled fraud provider with the exact subspec and application configuration. Missing runtime frameworks can appear as empty device data rather than a compile failure.

v2.11.x · Native wallet and presentation workWallet and widget lifecycle

This line introduced and refined native wallet availability and launch behavior, Apple Pay configuration, widget auto-resize work, completion dispatch on the main thread, and safer controller dismissal.

Verify entitlements, merchant identifiers, supported networks, physical-device availability, cancellation, background/foreground behavior, and backend reconciliation.

v2.4.0 · Response and presentation changesBreaking payload types
  • Typed response data such as ElementsResponseData, CheckoutResponseData, CardBinMetadata, and InstallmentMetadata changed to [String: Any] payloads.
  • PaymentsError became the public error type.
  • Deprecated presentInModal and showCloseButton parameters were removed from older Checkout and Elements entry points.

Prefer the current controller and presentation APIs in the iOS guide, and avoid strict whole-dictionary equality for additive event data.

v2.0.0 · Public symbol migrationMajor migration

The major line renamed callback, response, and event symbols, including Callbacks to CheckoutCallbacks and CheckoutEventType to CheckoutEvent. Compile all integrations and analytics adapters after updating imports.

Compatibility matrix#

SurfaceUpgrade check
Dependency managerExact SPM version or CocoaPods version and required subspecs resolve reproducibly
Apple toolchainApp deployment target, Xcode, Swift, linker settings, and privacy manifests
PresentationUIKit and SwiftUI ownership, modal and embedded modes, auto-resize, keyboard, and dismissal
External actions3DS, ASWebAuthenticationSession or approved browser flow, deep links, cancellation, and return
Native walletsEntitlements, merchant ID, physical-device capability, networks, tokenization, and cancellation
Fraud providersRequired vendor framework, initialization timing, timeout, missing data, and privacy declarations
CallbacksMain-thread UI work, dedicated handlers, additive event data, and unknown-event fallback

Regression checklist#

  • Clean install and upgrade from the currently deployed pin using the production dependency manager.
  • Debug and archive builds on the oldest and newest supported OS versions.
  • Payment Widget, Elements, Voucher, and Next Action in every supported presentation mode.
  • Rotation, Dynamic Type, VoiceOver, keyboard, sheet dismissal, background/foreground, and memory release.
  • Apple Pay availability and payment authorization on physical devices.
  • Every enabled native fraud provider with permitted data and failure handling.
  • Backend retrieval or verified webhook confirmation after every client outcome.