Update dependency com.adyen.checkout:cse to v4.13.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.adyen.checkout:cse	4.1.0 -> 4.13.6

---

Release Notes

Adyen/adyen-android (com.adyen.checkout:cse)

v4.13.6

Compare Source

Fixed

• On Android API versions 21 to 25, the NoSuchMethodError no longer occurs during the 3D Secure 2 challenge flow.

Changed

• Dependency versions:

  Name	Version
  Adyen 3DS2	2.2.19

v4.13.5

Compare Source

Changed

• Dependency versions:

  Name	Version
  Adyen 3DS2	2.2.17

v4.13.4

Compare Source

Note

If you are using WeChat Pay please update to this version or migrate to 5.x.x to make sure WeChat Pay will work for all Android versions.

Fixed

• WeChatPay now works correctly on Android 11 and later. This fixes a known issue from previous 4.x.x versions.

Changed

• Dependency versions:

  Name	Version
  WeChat Pay	6.8.0

v4.13.3

Compare Source

Fixed

• Fixed Cash App payments being refused because of missing customerId during /payments/details call.

v4.13.2

Compare Source

Changed

• Updated device information collection during the 3D Secure 2 device fingerprinting process.

v4.13.1

Compare Source

Fixed

• For cards that require the shopper to input their address:
  • When internet connection is lost while loading, it no longer crashes. Instead an error is returned.
  • The Country dropdown menu to select no longer displays no options. Previously, an error sometimes caused the menu to have no options, so the transaction couldn't be submitted.

v4.13.0

Compare Source

New

• For 3D Secure 2 transactions, when a challenge is unsuccessful because of error or timeout, the details are propagated in an object instead of returning an error. You can make a /payments/details request from your server to submit these details.

Changed

• 3D Secure 2 SDK version: v2.2.15.
• compileSdkVersion and targetSdkVersion: 33.

Fixed

• For cards, when a detected card brand doesn't require a security code (CVC), the CVC field on the payment form no longer shows a validation error.
• For dual-branded cards, if the shopper doesn't select a detected brand, the paymentMethod object no longer contains a brand when submitting the payment.
• After the AwaitComponent handles an action, it no longer causes a crash when resuming your app from the background.

v4.12.1

Compare Source

Fixed

• For 3D Secure 2, consecutive payments no longer fail. Previously, if the challenge failed, retrying the payment failed in some cases.

v4.12.0

Compare Source

New

• Payment method: Cash App Pay.

Fixed

• For Google Pay, serializing the shipping address parameters no longer causes an error.
• For WeChat Pay on Android 11, an API restriction no longer causes an error.

Removed

• For 3D Secure 2, the threeDSRequestorAppURL will not have a default value anymore. You can set it manually using:

Adyen3DS2Configuration.Builder(locale, environment, clientKey)
    .setThreeDSRequestorURL("https://{your app.com}/adyen3ds2")
    .build()

v4.11.0

Compare Source

New

• For BLIK, one-click is now supported.
• For 3D Secure 2, the threeDSRequestorAppURL can now be overridden from the configuration so that you can now use the Android App Link format (HTTP).

Adyen3DS2Configuration.Builder(locale, environment, clientKey)
    .setThreeDSRequestorURL("https://{your app.com}/adyen3ds2")
    .build()

⚠️Because of recent updates to the 3D Secure protocol, we strongly recommend that you provide the threeDSRequestorAppURL parameter as an Android App Link instead of custom link. This requires your app to handle the provided Android App Link. More details on how to handle Android App Link can be found on docs page.

Fixed

• For BCMC, errors are now correctly highlighted.

v4.10.0

Compare Source

New

• The CardComponentState.binValue now reports 8 digit bins in case of card numbers with 16 or more digits.
• The new CardBrand class can be used to define unknown card brands. This can be used along with CardType.
• When adding new card brands through CardConfiguration, you can now use the new CardBrandto add brands that are not already defined in CardType.
  For example:

CardConfiguration.Builder([SHOPPER_LOCALE], [ENVIRONMENT], [CLIENT_KEY])
.setSupportedCardTypes(CardBrand(txVariant = "[CARD_BRAND1]"), CardBrand(txVariant = "[CARD_BRAND2]"))
.build()

Changed

• Upgraded the 3D Secure 2 SDK version to v2.2.11.
• Upgraded compileSdkVersion and targetSdkVersion to 32.
• Upgraded Kotlin version to 1.6.21.
• Upgraded Kotlin coroutines version to 1.6.1.
• Upgraded Fragment version to 1.5.5.
• Upgraded AppCompat version to 1.5.1.

Fixed

• For cards, you can now add unknown card types that aren't defined in CardType. Previously,
  CardType.UNKNOWN was not working correctly.
• There is no longer a conflict with the 3D Secure 2 SDK that causes a runtime exception. This fixes the known issue in v4.9.0.

Deprecated

• The CardType.UNKNOWN property. Use CardBrand(txVariant = "[CARD_BRAND]") instead.
• The CardType.setTxVariant() method. No longer needed as it was used with CardType.UNKNOWN.

v4.9.1

Compare Source

Fixed

• For cards, when the shopper enters a card number and a dual branded card is detected, a brand is no longer selected by default.
• Drop-in no longer crashes when navigating back after the shopper removes all stored payment methods.

v4.9.0

Compare Source

Added

• For cards, in AddressConfiguration.PostalCode mode, you can now specify if the postal code field required.
• For BCMC, you can now specify if the card holder 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.

Changed

• 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.
• For cards, if you currently set the postal code input field in the AddressConfiguration as .setAddressConfiguration(AddressConfiguration.PostalCode), you must update it to .setAddressConfiguration(AddressConfiguration.PostalCode()).

Fixed

• 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.

Known issue

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

v4.8.0

Compare Source

Added

• Online Banking Poland Component.

Changed

• Update 3DS2 SDK version to 2.2.8.

Fixed

• Gracefully terminate drop in without crashing when coming back from a redirect after drop-in was closed.
• Updating 3DS2 SDK version fixed a crash on Android 13.

v4.7.1

Compare Source

Fixed

• For BACS Direct Debit, an error message appears under the payment agreement text if the shopper selects the Continue button without selecting the toggles to agree.

v4.7.0

Compare Source

Added

• Support for the new Asia Pacific South East (APSE) and India live environments. Use these environments with the corresponding APSE or India location-based live endpoints.

Fixed

• For BACS Direct Debit, the payment agreement text in the payment form now includes the amount. Previously, it always showed the default above amount instead of the amount.

v4.6.1

Compare Source

Fixed

• Not being able to import some standalone modules because of ui-core accidentally having a dependency to a style in card.

v4.6.0

Compare Source

Added

• Full billing address form in the card component. Use CardConfiguration.Builder.setAddressConfiguration to enable and configure.

Deprecated

• Environment.LIVE. Replace with one of our explicit live environments, same one as your back end. You can find that value in your Customer Area.
• CardConfiguration.Builder.setAddressVisibility. Replace with CardConfiguration.Builder.setAddressConfiguration.

Fixed

• Soft keyboard navigation (next) not working in some cases in card component.
• Localization issues with standalone components and custom locales.
• Crash in GooglePay availability check.
• Proguard rules. If you had to manually set any Proguard rules related to Drop-in or Components you can remove them.
• Minor visual issues with removing stored payment methods.

v4.5.0

Compare Source

Added

• Gift Card flow in Drop-in.
• New required Gift Card related methods in DropInService:
  • checkBalance to make the /paymentMethods/balance API call and sendBalanceResult to return the result.
  • createOrder to make the /orders API call and sendOrderResult to return the result.
  • cancelOrder to make the /orders/cancel API call. Result can be returned with sendResult.
• DropInServiceResult.Update required for the Gift Card flow. Updates drop-in with a new list of payment methods and optionally an order.
• Gift Card Component.
• RTL support.
• Arabic string resource translations.
• Pass a custom Bundle to DropInService using DropInConfiguration.Builder.setAdditionalDataForDropInService. Retrieve this bundle by calling DropInService.getAdditionalData.
• The default Google Pay environment will automatically follow the Adyen environment even when calling GooglePayConfiguration.Builder.setEnvironment separately. You can still call GooglePayConfiguration.Builder.setGooglePayEnvironment to override this default behaviour.
• Ability to remove stored payment methods. Override DropInService.removeStoredPaymentMethod and use sendRecurringResult to return the result.

Changed

• Updated Adyen 3DS2 SDK version to 2.2.6.

Fixed

• Redirects in Android 11. Privacy changes for package visibility in Android 11 requires a fix for handling redirects using Custom Tabs.
• Crash when the provided shopper Locale doesn't have an ISO3Country.
• Crash in the Component screen when resuming drop-in after the activity has been destroyed in the background.
• CVC and expiry date fields in Card Component not being validated when empty.
• Various missing translations.

Removed

• Drop-in being dismissed when tapping anywhere outside of the bottom sheet.

v4.4.0

Compare Source

Added

• BACS Direct Debit Component.

Fixed

• Google Pay Environment being set incorrectly to WalletConstants.ENVIRONMENT_PRODUCTION.

Deprecated

• DropInServiceResult.Action(actionJSON: String) is deprecated in favor of DropInServiceResult.Action(action: com.adyen.checkout.components.model.payments.response.Action). Use com.adyen.checkout.components.model.payments.response.Action.SERIALIZER to serialize your JSON response string.

v4.3.0

Compare Source

WARNING

Make sure you explicitly set your LIVE environment on release builds when initializing Drop-in; DropInConfiguration is now initialized with Environment.TEST by default instead of Environment.EUROPE.

Deprecated

• saveState and restoreState methods in action components. We rely on SavedStateHandle in all components and providers so these methods can be safely removed now.
• requiresConfiguration method in action component providers. All components require configurations therefore this method will always return true.

Added

• Card component shows a more specific error message when the user enters a card belonging to an unsupported brand.
• DropInConfiguration.Builder.setSkipListWhenSinglePaymentMethod to allow skipping payment methods screen when single payment method exists. This only applies to payment methods that require a component (user input). Redirect payment methods, SDK payment methods, and so on will not be skipped.
• Provide fundingSource when present in payment methods response.
• Support for installments in card component.
• Environment.LIVE, identical to the Environment.EUROPE.

Changed

• Update 3DS2 SDK to version 2.2.5.

Fixed

• Use ApplicationInfo.FLAG_DEBUGGABLE instead of BuildConfig.DEBUG to figure out whether it's a debug or release build.
• NoClassDefFoundError crash with Card component, if 3DS2 is not included in the project.
• Handle Google Pay cancellation and failure callbacks on initialisation.

v4.2.0

Compare Source

Added

• Dual-branded card flow: shoppers can now select their card's brand when two brands are detected.
• Ability to store BCMC cards.
• Support for new Activity Result API.
• Ability to stop observing components.
• 3DS2 SDK version in CardComponent's output.
• Read list of supported card networks for Google Pay from the payment methods API response.

Fixed

• Crash caused by having stored payment methods none of which is Ecommerce.
• Google Pay Component will not include TotalPrice in its output, if TotalPriceStatus is set to NOT_CURRENTLY_KNOWN.
• Issue in Drop-in when multiple payment methods have the same type.
• Missing default BCMC configuration in Drop-in.

v4.1.1

Compare Source

Fixed

• Address Visibility in Card Component configuration not being reflected on UI.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.