Release notes

• For cards, in AddressConfiguration.PostalCode mode, you can now specify if the postal code field required.
• For BCMC, you can now specify if the cardholder name field is required.
• After the card brand is detected and the shopper enters the full card number in the card number input field, focus automatically moves to the next input field.

• Upgraded the 3D Secure 2 SDK version to v2.2.10. This causes a known issue.
• For a card number to be valid, its minimum required length is now 12 digits. Previously, the minimum was 8 digits.

• Configuration changes no longer dismiss Drop-in. Previously, some configuration changes dismissed Drop-in.
• Drop-in can now be initialized with only stored payment methods. Previously, no payment methods were shown if only stored payment methods were available.

For cards, if you currently use AddressConfiguration.PostalCode mode, you must update it for 4.9.0:

If your project uses Google play-services-location library version 20.0.0 or earlier, it causes a runtime exception because of an incompatibility with the 3D Secure 2 SDK. You must upgrade the library to version 21.0.0 or later to avoid the runtime exception.

The finalizeIfNeeded(with: Bool) method. Use finalizeIfNeeded(with success: Bool, completion: (() -> Void)?) instead.

Successful Apple Pay payments are now finalized with finalizeIfNeeded(with success: Bool, completion: (() -> Void)?), which increases conversion rates.

• We added several accessibility improvements for Drop-in and Components.
• For payment methods with multiple payment method variants, such as Klarna or Dragonpay, we fixed an issue where the Component could be created with incorrect payment method data. This issue only occurred when using Components, not when using Drop-in.

For Pix, you can configure the Drop-in or the Component to collect shopper's name and the CPF/CNPJ (a unique identifier similar to a social security number), by including personalDetailsRequired.