Releases: Adyen/adyen-ios
Releases · Adyen/adyen-ios
4.7.3
Important
This release is not compatible with Xcode 15
Please consider updating to 4.11.1 or newer
Improved
- Upgraded the 3D Secure 2 SDK version to 2.2.6.
- The errors for invalid form fields are now read out by screen readers.
- Prevent conflicts with the host application bundle by specifying the bundle when initializing any internal SDK.
Fixed
- Fixed a bug country picker was being displayed briefly after selecting Pay.
4.7.2
4.7.1
Important
This release is not compatible with Xcode 15
Please consider updating to 4.11.1 or newer
Fixed
- You can now use more than one client key for your integration, for example, if you need different credentials for some merchant accounts.
- Fixed the known issue from v4.5.0 where Cartes Bancaires did not work on Apple Pay.
4.7.0
Important
This release is not compatible with Xcode 15
Please consider updating to 4.11.1 or newer
What's Changed
New
- New supported payment method: ACH Direct Debit.
- You can now encrypt the bank details (account number, routing number) if using the
BankDetailsEncryptor
with an API-only integration. This is required for ACH. - For the Card Component, you can configure the countries in the billing address drop-down menu using
billingAddressCountryCodes
.
Changed
- Moved the WeChat binary from the
AdyenWeChatPay
module to an external repository. If you're using WeChat Pay with Carthage, addAdyenWeChatPayInternal
to your project. If you're using WeChat Pay with CocoaPods and Swift Package Manager, the change happens automatically as part of the update.
Improved
- For the Card Component, the focus moves to the next field when the entered card number reaches the expected length.
- If testing Apple Pay using the Simulator, you get an
invalidToken
error. The error description now explains that you must use a device instead. - We improved the app-to-app redirect detection by increasing the delay for the
BrowserComponent
. - Update the WeChat Pay Component to use WeChat SDK 1.9.2.
Fixed
- Apple Pay Component no longer calls
didFail
for a successful payment. This used to happen if you didn't dismiss the Apple Pay view immediately after callingfinalizeIfNeeded(with: success)
. - Text fields, except the card number and CVC, now allow the system default input options.
4.6.1
4.6.0
4.5.0
Important
This release is not compatible with Xcode 15
Please consider updating to 4.11.1 or newer
New
- On Drop-in, the allowsSkippingPaymentList flag lets you skip the screen with the list of payment methods, if there is only one payment method available to the shopper. For example, if card is the only available payment method, the shopper will be taken directly to the card details input screen.
- On Drop-in, you can now customize the screen with the Apple Pay button using
DropInComponent.Style.applePay
.
Improved
We've added support for the following card networks in Apple Pay:
- MADA (mada) in the Middle East.
- Cartes Bancaires (cartesBancaires) in France.
See the networks we currently support.
Fixed
- Card brand detection for dual-branded cards is now based on the first 11 digits of the card number.
3.9.1
Fixed
- The encrypted token returned by
CardEncryptor.Card.encryptedToToken()
now also encodes thegenerationDate
timestamp.
4.4.0
Important
This release is not compatible with Xcode 15
Please consider updating to 4.11.1 or newer
New
- You can now pre-fill shopper information for card payments. You can pre-fill the cardholder name, billing address, postal code and social security number, by injecting it when creating the component.
- For dual-branded cards issued in Europe, the Card Component now renders both brands, and allows the cardholder to choose the brand they want to pay with.
- On Drop-in, you can now allow shoppers to remove stored cards. Implement
StoredPaymentMethodsDelegate
and set
DropInComponent.Configuration.paymentMethodsList.allowDisablingStoredPaymentMethods
totrue
. - For the Card Component UI, once the card brand is detected, the supported card brand logos become more transparent to make them less prominent.
Fixed
- Shoppers can no longer enter invalid characters in the checkout form.
- Fixed an issue with the Drop-in slide-in animation.
3.9.0
New
- You can now use
CardEncryptor.Card.encryptedToToken()
to encrypt all card details as a single token.
Improved
- Upgraded the 3D Secure 2 SDK version to v2.2.4..
- The
CardDetails
object now contains the version of the 3D Secure SDK inthreeDS2SDKVersion
.