5.20.1

Fixed

• For Drop-in analytics: when only one payment method is available and renders directly on the screen, the render analytics event is now sent. #2251

4.16.0

Changed

• Updated 3D Secure 2 SDK to version 2.4.3
  • Fixed a bug where an object was prematurely released, which could cause the transaction to fail.

5.20.0

Changed

• Updated 3D Secure 2 SDK to version 2.4.3

  • Fixed a bug where an object was prematurely released, which could cause the transaction to fail.

• Improved the user experience for the UPI component:

  • The QR code flow has been removed. The shopper can pay the following ways:
    • Intent flow: the shopper pays with an installed UPI app.
    • Collect flow: the shopper enters their UPI ID.

• Added new instructions labels for better clarity across all UPI payment flows.

• Minor changes in design to improve the user experience.

Fixed

• On iOS 17, fixed a bug that caused a crash when present(viewController:) was called multiple times in short timespan from a SwiftUI view. This fixes issue #2182 (contributor: @MatthiasFriese ).

5.19.2

Fixed

• The amount displayed on the Apple Pay payment sheet is now correctly updated after a partial payment.
• For cards: in the payment form, the UI to select a card brand for a co-badged card now appears only if the following brands are available:
  • Cartes Bancaires (cartebancaire)
  • Bancontact card (bcmc)
  • Dankort (dankort)

5.19.1

Changed

• Small UI improvements for co-badged cards brand selection.

5.19.0

Fixed

• For cards, enhanced the accessibility labels so that the screen reader provides more context on the expiry date and security code fields. #2149

5.18.1

Fixed

• Improved card brand display for co-badged cards: When shoppers use a co-badged card, the UI now displays the local brand name (e.g., "Bancontact card"). If a local brand name is not available, the generic brand type (e.g., "BCMC") will be used as a fallback. This provides a clearer and more familiar experience for shoppers.

5.18.0

New

• For cards: when the shopper enters the details for a co-badged card in the payment form, they can now select the card brand they want to pay with.

• When you are using an enforced locale, you can now add new localizations or override strings.

Fixed

• For the BCMC Component: when you specify custom localization parameters, the Component now correctly uses them.

5.17.0

New

• Payment method: PayTo, with support for recurring payments.

Changed

• Updated AdyenNetworking to v3.0.1
• Updated adyen-wechatpay-ios to 2.2.0

Fixed

For the card component:

• Updated the separator layout to to be centered in the container view.
• The security code and card number logo edges are now aligned with the input field edges.

5.16.0

Changed

• Add support for distinguishing between regular and native redirects to improve handling of failed native redirect flows.
• For native 3D Secure 2, when a shopper cancels the payment during the payment flow, the didProvide(...) delegate method is now triggered. What this means for your integration depends on whether you already make a /payments/details call to handle 3D Secure 2 errors:
  • If yes, you do not need to make any changes to your integration.
  • If not, update your integration to make a /payments/details request to get the details of the canceled transaction.