Release notes

• New supported payment methods: Affirm, OXXO.
• The Card Component now has support for:
  • Korean card payments through KCP.
  • Brazillian card payments that require the social security number.
  • UK addresses.
• Shoppers can now add vouchers to Apple Wallet.
• Get the last 4 digits of the entered card number using didSubmit(lastFour:component:).

• If a shopper enters card data and then closes the payment screen, the component now clears the values for improved security.
• The Card Component now runs validation on optional CVC fields if the shopper enters a value.
• Disabled Luhn checks for private label cards (also known as white label cards), because the check fails even if the card number is valid.
• The card number field now has a numeric keypad for input.
• The Boleto Component has improved validation for social security numbers.
• There are smoother transitions between Drop-in screens.
• Redesigned the Drop-in UI for iPad so that it is responsive to screen size and feels native to the iPad.
• Redesigned the UI for voucher payment methods to make it easy for shoppers to find the call to action.
• Added a README.md file for the demo projects.
• Updated the 3D Secure SDK to v2.2.3.
• Moved the networking layer into a separate framework as a dependency.

• You can now use CocoaPods on M1 Mac devices.
• Fixed a bug where card brand logos were not showing up if the shopper deleted the initial card number and entred a value again.
• Single digit house numbers no longer fail validation.

• The Card Component now has support for:
  • Korean card payments through KCP.
  • Brazillian card payments that require the social security number.
  • The postal code input field.
• On Drop-in, you can now take shoppers to the list of all available payment methods instead of only showing their stored cards. To do this, call DropInConfiguration.Builder.showPreselectedStoredPaymentMethod(false).
• Support for Android 12.

• Configuration objects now do runtime validation to make sure your client key matches the environment it is being used on.
• Disabled Luhn checks for private label cards (also known as white label cards), because the check fails even if the card number is valid.
• Updated the 3D Secure SDK to v2.2.4.

• The focus no longer automatically switches to the next input field after the card number has been filled in.

• Fixed an issue where card brand logos weren't loading if there were multiple logos of the same type, for example when the shopper had multiple stored cards of the same brand.
• If the Android operating system stops your app before the payment flow is completed, this no longer causes Drop-in to fail.

For Boleto Bancário, the state.data is missing the billingAddress.country, causing the payment to fail. This issue is fixed in Web Components 4.2.2.

• We added new Apple Pay button types. For a full list of supported Apple Pay button types, refer to Button configuration.
• For Google Pay, you can now use the buttonSizeMode and buttonLocale configuration properties. For more information, refer to Button options.
• Stored cards can now be configured separately from other cards, by including a storedCard object in the paymentMethodsConfiguration object.

The placeholder values for card fields are now only read from translation fields. Configuring placeholder values inside the Card Component is no longer supported.

• We added a missing CSS file export in the npm package.
• We fixed an issue where the promise dependency could be missing when using the ES format bundle.
• When pasting a dual-branded card number over a previously entered card number, the detected card brand is now being rendered correctly.
• When paying in IQR (Iraqi Dinar), the amount on the Pay button is now rendered correctly.