Skip to content

4.0.0

Choose a tag to compare

View all tags
@luiscosta luiscosta released this 03 Jun 15:37
· 4 commits to master since this release
4.0.0
57fa4e1

🎉🍾 Goodbye mobileToken – welcome transactionId!

Today, we are introducing a new transaction model that organizes all actions related to a single payment, including failed and successful attempts and refunds, under a single transactionId.

These new Transactions API v2 flows allow us to eliminate the mobileToken🥲 and finally unify our web and mobile APIs.

This release is the first version of Mobile SDK 4, built on a new architecture. It currently supports the following payment methods:

  • Credit and debit cards
  • Apple Pay
  • Google Pay
  • PayPal
  • PostFinance Pay
  • Twint

We are working toward full feature parity with the 3.x SDK line, with additional payment methods and features planned for upcoming releases. At the same time, we remain fully committed to supporting the 3.x SDK.

⚠️ Migration Required

Mobile SDK 4 requires a backend integration based on Transactions API v2 and replaces mobileToken with transactionId.

→ See the Migration Guide for upgrade instructions.

New

mobileToken replaced by transactionId

  • The /v2/transactions init request is now identical for web and SDK integrations
  • Transaction status is now available through the Transactions API during mobile payments

Multiple attempts

  • If multiple payment methods are available, the SDK allows users to retry with another method after an error instead of terminating the payment flow

Consistent webhook handling

  • Webhooks are now sent consistently across payments, registrations and authentications
  • A webhook is triggered on success, error, cancellation, when the user abandons the process, and when the SDK is not even started (timeout)

Integrated 3DS SDK

  • Native 3-D Secure screens and seamless app switching to and from banking apps
  • More frictionless flows
  • Frictionless flows now occur without UI flicker
  • Improved soft-decline handling

Auto-authorize support

  • Added a new SDK option: autoAuthorize
  • Automatically progresses the transaction after authentication/user confirmation, without requiring the user to reopen the merchant app

Important: Make sure you understand this feature before enabling it, see What’s new in Mobile SDK 4.

Security and anti-fraud

  • Several improvements to enhance security and reduce fraud

UI refresh

  • Modernized UI aligned with current platform design guidelines
  • Improved saved method selection
  • Improved accessibility

Under-the-hood improvements

  • Replaced legacy architecture and components
  • More stable payment flows involving third-party apps
Assets 2
Loading