Releases: Adyen/adyen-ios
5.9.0
New
-
The new iDEAL payment flow where the shopper is redirected to the iDEAL payment page to select their bank and authorize the payment. See: iDEAL Component Integration
-
When shoppers select the prefix picker in the phone number input field, they can now search through the prefix list using their ISO code, prefix, or country/region name.
Known issue
iDEAL does not work in the test environment if your test Adyen merchant account is not configured to use the new payment flow.
You must first contact our Support Team to configure your test merchant account.
4.13.0
New
- The new iDEAL payment flow where the shopper is redirected to the iDEAL payment page to select their bank and authorize the payment.
Known issue
iDEAL does not work in the test environment if your test Adyen merchant account is not configured to use the new payment flow.
You must first contact our Support Team to configure your test merchant account.
5.8.0
New
- Support for Twint SDK integration through the
TwintComponent
module.
Changed
- Flag icons are removed from the UI.
- The text Country is now replaced with Country/Region.
Fixed
- Fixed an issue that incorrectly cancelled successful redirect payments in some cases.
5.7.1
4.12.1
5.7.0
New
-
The
PrivacyInfo.xcprivacy
lists all the data collected by Drop-In and Components. -
In the country/region picker for the payment form, you can now choose if the images of flags are shown using
showCountryFlags
.Components
let cardConfiguration = CardComponent.Configuration() cardConfiguration.style.addressStyle.showCountryFlags = true/false let cardComponent = CardComponent(paymentMethod: paymentMethod, context: context, configuration: cardConfiguration)
Drop-In
var style = DropInComponent.Style() style.formComponent.addressStyle.showCountryFlags = cardSettings.showsCountryFlags let dropInConfiguration = DropInComponent.Configuration(style: style) let dropInComponent = DropInComponent(paymentMethods: paymentMethods, context: context, configuration: dropInConfiguration)
Changed
- 3D Secure 2 SDK version: 2.4.1
Fixed
- When
clientKey
is invalid or mismatched with the environment,PublicKeyProvider
now returns a corresponding error message.
4.12.0
4.11.2
Fixes
- For stored card payments using Drop-in, the pay button is now enabled correctly when entering the security code with the Traditional Chinese Cantonese keyboard.
5.6.0
Improved
- For all payment methods that include input fields for the shopper's address, the address input fields are now on a separate screen. This declutters the payment screen to improve user experience.
Changed
- Custom conformances to
PaymentMethod
andStoredPaymentMethod
are now required to beEncodable
.
Fixed
- For Apple Pay, when the
allowOnboarding
property ofApplePayConfiguration.init
is set to true, the onboarding check now runs correctly. - In landscape mode, the search bar height no longer expands and obstructs other visual elements like the issuer list on the screen.
- For stored card payments using Drop-in, the pay button is now enabled correctly when entering the security code with the Traditional Chinese Cantonese keyboard.
5.5.0
New
-
When you offer installment payments, you can now show the number of installments and the amount of each installment in the picker. For example, 3x $20.
- For Sessions flow, when you make a
/sessions
request, includeshowInstallmentAmount
:
true andinstallmentOptions
.
We use these values to show installment options in the picker. - For Advanced flow, in the
InstallmentConfiguration
object, setshowInstallmentAmount
to true when you initialize it.
- For Sessions flow, when you make a
-
Support for library evolution
Changed
For cards, the address lookup feature now supports a 2-step lookup process (for example, used by the Google Maps API):
- First, it allows providing suggested addresses (that might be incomplete)
- Then, optionally, it allows making another API request to complete the suggestions.
You must change the callback as follows:
5.4.1 or earlier | 5.5.0 |
---|---|
.lookup(LookupProvider) | .lookup(AddressLookupProvider) |
Fixed
-
When the shopper's phone number is included in the
shopperInformation
object, the pre-filled phone number prefix on the payment form automatically updates to match the correct country code. -
Drop-in now updates the payment method list after the shopper applies a gift card, in case the available payment methods change because of the updated payment amount.
-
When you define custom localizations in your app bundle using Localizable.strings, they are now applied correctly.
-
The Bizum payment method is no longer shown as an available payment method.