Release notes

• For cards, when the shopper enters their card number in the Card number field, the length of the card number is no longer restricted based on the Bank Identification Number (BIN).

• For Apple Pay in apps that use server-side rendering: the iframe detection code no longer crashes when rendering. This fixes the known issue from v6.10.0.
• For cards, when you select the icon for an inoput field, the corresponding field now correctly gets the focus state.

• You can now offer Apple Pay on third-party browsers. See offering Apple Pay on the web to learn more.

• For Drop-in, when using Google Pay as an instant payment type, the challengeWindowSize is now handled correctly.
• Fixed Brazilian social security number translation (CPF/CNPJ) for different languages.
• Fixed an issue where the exposed types for Google Pay and Apple Pay were not being found.

• For single branded cards, the error message shown to when there configuration is incorrect is updated.
• Improved the contrast, aria-expand attribute for radio buttons, and SVG alt descriptions to follow a11y guidelines.
• For Google Pay, an error is thrown when the configuration is missing the required merchant ID.

• For Apple Pay in apps that use server-side rendering: the iframe detection code crashes when rendering. Fixed in v6.11.0.

• Supported payment method: PayTo. Payment method type: payto.

• When the shopper selects the Pay button, the Open Invoice and ACH Components become disabled.
• For Boleto: additional properties have been added to the BoletoConfiguration TypeScript interface.
• For cards: the onAutoComplete type has been added to the CustomCardConfiguration type.
• For Google Pay: the challengeWindowSize type has been added to the GooglePayComponent TypeScript interface.

• For Google Pay: when you call reject on the onClick event, an unhandled exception can no longer be triggered.
• For gift cards: when the shopper pays with a second gift card the UI no longer becomes unresponsive.

• Style issues no longer occur due to font scaling, because rem is now used for the font size unit.

• For Trustly, missing translations have been added.

• Added tracking for API errors for internal endpoints for analytics purposes.
• During the process of handling the payment response, Drop-in/Components no longer makes a duplicated internal API request.
• For the Custom Card Component, TypeScript types for configuration parameters are now more explicitly declared.

• For cards, the styling for the confirmation message to remove a stored card no longer causes responsiveness issues.
• For Click to Pay, button elements that appeared as links now appear as buttons.
• For Google Pay, when the value of the GooglePayButton attribute buttonRadius is 0, it no longer fails to be passed to the createButton function.
• The Klarna Component now initializes the Klarna Widget SDK correctly. This fixes the known issue from v6.6.0.
• For Trustly, missing translations have been added.

• The Klarna Component encounters an error when initializing the Klarna Widget SDK. Fixed in v6.7.0.

• For the online banking payment methods in Slovakia and the Czech Republic, bank logo icons now appear in the list of banks.

• For WeChat Pay QR codes, updated the text indicating the time left to pay for the zh-CN locale.
• For ACH Direct Debit, removed the text under the Account holder name field.
• When you set the Country and State fields to required in the payment form, the setting now correctly applies to the fields.
• For donations, the nonprofit logo and description no longer cover the donation banner, and the banner now maintains it's aspect ratio when scaling according to the shopper's screen size.

• For cards, when the card is detected in the Card number field,
• When multiple variants of Klarna are available in the payment methods list, you can now make sure that the payment is made with the correct variant with the new activate() method.
  • For Drop-in: this happens automatically.
  • For Components: you must call active() when the shopper selects a variant of Klarna.

• For cards, when the expiryDate is only one digit, the onBlur validation now gets triggered.

• For PayMe, when the shopper pays, the UI shows instructions to complete the transaction.

  

• For PayNow, when the shopper pays on a tablet or mobile device, the UI now shows instructions to complete the transaction.

  

• When creating a production build, the auto.js code is no longer tree-shaken by bundlers.
• For integrations using the address lookup feature for cards: the State or province field no longer resets when the shopper selects a value for the Country field.
• The Iceland Krona currency (ISK) now correctly uses minor units.
• For UPI, the initial value for isValid is now true only for UPI QR.
• To support earlier iOS versions, the ECMAScript version is now the 2020 version.
• For Payconiq, the UI now includes instructions for the QR code, and an unused button label is now removed.

• For integrations using the address lookup feature for cards: the State or province field no longer resets when the shopper selects a value for the Country field.
• For UPI, the default value for isValid is now true only for UPI QR.

• All action types now trigger the onActionHandled callback.
  • For all action types, except for threeds2, the original action object is passed to the callback.
• For ACH, the shopper can now select the Savings or Checking account type.

• For improved developer experience, we now export the CustomTranslations type.
• document.querySelector is now called only once, instead of three times.

• get-process-message.handler.js no longer causes exceptions. The new optional chaining operator for the postMessage handler function now prevents improperly formed events.
• When you call actions.reject() in the beforeSubmit callback, the UI no longer set the UI in an error state. Previously, it caused a call to handleFailedResult, which caused the onPaymentFailed callback to be called and set the UI in an error state.

• For ACH, the shopper can now select the Savings or Checking account type.

• get-process-message.handler.js no longer causes exceptions. The new optional chaining operator for the postMessage handler function now prevents improperly formed events.

• For Pay by Bank payments in the US, the payment form now shows US bank logos.
• For Click to Pay with Visa, custom timeouts now get reported to the Visa SDK.

• For Click to Pay with Visa, when the shopper selects Enter, the event no longer propagates to other views.

• For Pay by Bank payments in the US, the payment form now shows US bank logos.

• For Click to Pay with Visa, custom timeouts now get reported to the Visa SDK.

• For Drop-in, when loading, payment methods that are not supported are filtered out before the individual payment method Components are created.
• When loading, during the internal setup requests, the browserInfo information is included.

• When you set analytics.enabled = false, only Drop-in/Components analytics are not sent to Adyen.

• When loading, during the internal setup requests, the browserInfo information is included.
• For Drop-in, when loading, payment methods that are not supported are filtered out before the individual payment method Components are created.
• For Apple Pay, the ApplePaySession property is now optional in the Window interface.

• For Apple Pay, ApplePayService no longer causes reliability issues with SonarCloud.
• Projects that use webpack 4 can now directly import styles from the adyen.css file.
• For cards, the Enter key now correctly triggers validation and submission. Previously, a regression issue prevented the actions from being triggered.

• When you set analytics.enabled = false, only Drop-in/Components analytics are not sent to Adyen.

• Removed the unused region role from the payment method item to follow a11y guidelines.

• Fixed validation for Lithuanian postal codes to support inputs with 4 digits, 5 digits, and the LT prefix.

• Removed the unused region role from the payment method item to follow a11y guidelines.

• Fixed validation for Lithuanian postal codes to support inputs with 4 digits, 5 digits, and the LT prefix.

• For ANCV, after the shopper makes a partial payment, the ANCV ID and deducted balance is shown on the screen where they select the payment method for the remaining balance.

• Updated currency information for the following locales:
  • Iceland (ISK)
  • Bulgaria (BGN)

For stored cards, the holder name is now correctly passed when making the payment.

• For ANCV, after the shopper makes a partial payment, the ANCV ID and deducted balance is shown on the screen where they select the payment method for the remaining balance.

For stored cards, the holder name is now correctly passed when making the payment.

• For Riverty, the consent checkbox now includes a link to the Riverty privacy policy.

• For Riverty, the consent checkbox now includes a link to the Riverty privacy policy.

For UPI, the TypeScript type error for formatProps has been fixed.

For PayPal, the bug where the payment didn't get finalized after the PayPal lightbox closed no longer occurs.

General

• Drop-in/Components is no longer supported on Internet Explorer 11.
• If you integrate with npm, we've changed how you import Drop-in/Components to reduce the bundle size.
• If you integrate with embedded scripts, we changed how we expose the AdyenCheckout and Drop-in/Components on the window object.
• We've changed how you create an instance of Drop-in or Component.
• For the onSubmit() event handler, you now need to resolve/reject an actions object to continue or halt the payment flow.
• For the onAdditionalDetails() event handler, you now need to resolve/reject an actions object to continue or halt the payment flow.
• The onPaymentCompleted() event is no longer triggered for failed payments, instead the onPaymentFailed() event is triggered.
• The showPayButton parameter now defaults to true.
• The onValid() event is removed.
• The setStatusAutomatically property is no longer supported. If a payment is successful or if it fails, the component is kept in loading state and merchant must handle it accordingly.
• We've changed how you style Drop-in/Components to give you more fine-grained control by using custom CSS properties. Update your CSS styles accordingly.
• The countryCode property is now mandatory. It must be set directly in the AdyenCheckout configuration object, or in the /sessions request.
• The showFormInstruction property is no longer supported.
• When instantiating AdyenCheckout, you can no longer set the configuration property 'installmentOptions'. It must be set in the Card Component configuration instead.
• You can no longer set the configuration property paymentMethodsConfiguration when initializing AdyenCheckout. Instead, set it in the Drop-in configuration.
• The locale in your global configuration object must follow the xx-YY format, where xx specifies the language, and YY specifies the region. Locales that are not formatted correctly will be ignored and fallback to en-US. See all supported locales on our GitHub.
  Exception: For Arabic, the locale must be set to ar.
• TypeScript types are now imported directly from the root of the package, for example:

  Copy code
  import type { CardConfiguration } from '@adyen/adyen-web';

Payment method specific

Express payment methods

• For Google Pay express, the event handler onPaymentDataChanged now works only when the Component configuration property isExpress is set to true.
• For Apple Pay express, the event handlers onShippingContactSelected and onShippingMethodSelected now work only when the Component configuration property isExpress is set to true.
• For Paypal Express, the onShippingChange() event handler is no longer supported. Migrate to the onShippingAddressChange() and onShippingOptionsChange() event handlers.
• The onShopperDetails() event for PayPal is renamed to onAuthorized() and it must be resolved or rejected to finalize the payment.
• For Google Pay, the isAvailable() method does not return a boolean flag anymore. Instead, the promise is resolved when the payment is available and rejected otherwise.

Card payment methods

• The Card Component configuration property showBrandsUnderCardNumber is no longer supported.
• The challengeWindowSize configuration parameter can now be set in the card object within paymentMethodsConfiguration instead of the threeDS2 object.
• The Custom Card Component is renamed from securedfields to CustomCard and created as:

  Copy code
  new CustomCard()

Other payment methods

• For PayPal, the onCancel() event handler is no longer supported. To detect when the PayPal lightbox is closed, listen to the onError event with error type CANCEL.
• For Klarna, the token property is replaced with the authorization_token from the /payments/details request.
• For Adyen Giving, you now need to integrate with the Giving Campaign Manager Component.
• We no longer support the payment method QiwiWallet.

Partial payments

• The onOrderCreated() event is renamed to onOrderUpdated().

• onPaymentMethodsRequest() is a new event, which is triggered when a partial payment is made and the associated order isn't fully paid. Use the even handler to request payment methods for a new payment.
• onPaymentFailed() is a new event, which is triggered when a payment fails. Previously, this event was part of onPaymentCompleted().
• You can now disable the final animation after a successful or failed payment in Drop-in, by setting disableFinalAnimation to true.
• Shoppers can now confirm the payment by pressing the Enter key. If the payment has a validation issue, an error is shown in the Drop-in/Components interface.
  • You can customize, or prevent, the Enter keypress behavior by implementing an onEnterKeyPressed() event handler on AdyenCheckout.
• Support for six more locales: Catalan (ca-ES), Icelandic (is-IS), Bulgarian (bg-BG), Estonian (et-EE), Latvian (lv-LV) and Lithuanian (lt-lT).
• Support for Apple Pay Order tracking in Drop-in and in the Apple Pay Component.
• Support for tree shaking when integrating through npm.

• onPaymentCompleted() now works for both Sessions and Advanced flow.
• We have replaced input field placeholder texts with permanently visible contextual elements to enhance the accessibility and UX. You can still apply and customize placeholders.
• For Google Pay and Apple Pay, the onAuthorized event is now triggered before the onSubmit event. The onAuthorized event must be resolved in order to proceed with the payment flow.
• We have improved AVS checks for GooglePay and ApplePay by adding the billing address to state.data if available during payment method authorization.
• Drop-in no longer uses radio buttons by default.
• The WeChatPay timer now defaults to 30 minutes.

• For the Card Component, the info event now has the configData object that includes details about the configuration of the Component.
• Google Pay now supports the borderRadius property.

For installments, the text above the radio buttons or dropdown menu now shows correctly.

• For the Sessions flow: when a fatal error occurs while setting up the session, the onError callback now includes the full error object. Previously, it included only a hard-coded error message.

• Support for the UPI Intent flow, where the shopper on a mobile device can choose a UPI app to pay through. They are redirected to and complete the payment on the selected app.

• For Click to Pay, previously used cards now shown above newly created cards.
• For ACH, the showPayButton configuration is no longer ignored.

• The new iDEAL payment flow where the shopper is redirected to the iDEAL payment page to select their bank and authorize the payment.

• For 3D Secure 2, the analytics events now include the following information:
  • subType: the type of event.
  • result: the outcome of the event.
• For Google Pay, when the shopper pays with card, the state.data now includes the origin to trigger the 3D Secure 2 native flow.

• For open invoice payment methods:
  • When the shopper selects and deselects the consent checkbox, the Uncaught TypeError: Cannot use 'in' operator to search for 'errorI18n' in true error no longer occurs.
  • Errors related to the screen reader panel no longer causes issues with the logic of the OpenInvoice Component.
• For ANCV, a new order is no longer created when it is used as the second payment of a partial payment. The custom payButton now submits the correct data.

• When the shopper checks out, the checkoutAttemptIdobject is now always passed in the initial API request.
• For cards, the unencrypted expiry date can now be passed to the onFieldValid callback. To enable this, set exposeExpiryDate to true.

• For the phone number field in the payment form:
  • The Country selector for the phone number field is now called Country/Region.
  • Flag icons are no longer included in the selector.

• For voucher payment methods, the voucher now shows expiration the date and time.
• For wallet payment methods used as express payment methods, the function to submit analytics now works as expected.
• Drop-in no longer fails to render when only express payment methods are available.

Upgrading to this version

Copy code
npm install @adyen/adyen-web@5.63.0

For cards, the shopper can now enter a 19-digit Diners card number.

• For analytics and data tracking, the information collected now includes data about whether wallet payment methods are used as express payment methods.

• For the address fields of the payment form, the forward slash character (/) is now allowed.

• For open invoice payment methods (like Riverty), the SRPanel for screen readers now correctly includes the first name and last name fields in the delivery address.
• For combobox UI elements, when nothing is selected, aria-activedescendant is now null.

• For cards, Boleto, and ACH: when making the /payments request, the billingAddress.firstName and billingAddress.lastName parameters are no longer included.
• For the Sessions flow: when making a zero-auth transaction (amount: 0) the payment details are stored only when the storePaymentMethodMode parameter in the /sessions request is set to do so. This fixes the known issue from v5.59.0.

• For Apple Pay: you no longer get warnings in your integrated development environment (IDE) because of TypeScript type issues.
• For cards: the shopper can now enter a Discover card number with the length of 19 digits.

When making a zero-auth transaction (amount: 0) to store payment details, we now always pass the storePaymentMethod object to our server.

• For the Sessions flow: if your /sessions request included either enableRecurring or enableOneClick, making a zero-auth transaction fails.
• For the Advanced flow: if your /payments request included either enableRecurring or enableOneClick, making a zero-auth transaction fails.

• PayPal Express Checkout is now supported with the Web Component.

• New payment method: Online Banking Finland. Payment method type: ebanking_FI.
• Support for the new Riverty component (riverty) in AT, CH, and DE. This component will replace afterpay_default in the future.
• For Drop-in, when countryCode is set to FI, no payment method is selected by default and all payment methods are collapsed to comply with Finnish regulations.

• Fixed an issue where clicking on Card fields caused console errors for shoppers using an iOS device.

• For Blik, the Drop-in/Component now shows identifiers next to stored payment methods.

• For card, when making a zero-auth transaction:
  • The text on the pay button is now Save details.
  • A checkbox no longer shows.
• For Drop-in, after a zero-auth transaction, the text for the success message is Details saved.

Payment method: PayMe. Payment method type: payme.

• For QR code payment methods, the payment status check now calculates elapsed time more accurately.
• For the custom card integration with encryption, the Component now gives a console warning for an unsupported value in the data-cse attribute.

For QR code payment methods, the payment method logo now loads and shows correctly.

For cards, the startup log includes more detailed information that can be used to debug issues.

Upgrading to this version

Copy code
npm install @adyen/adyen-web@5.55.0--save

• For the card Component: the address lookup feature now includes the new onAddressSelected callback to handle additional information for address completion services that require a second callback, like Google Place Autocomplete API.
• For Click to Pay, if the shopper gives consent, you can now enable the cookie for Mastercard and Visa.

• For Click to Pay, the loading image is now an animated SVG file.

• For Drop-in:
  • Payment methods that are not cards no longer include the fundingSource object with credit or debit.
  • For Klarna B2B, the logo is now correct.
• For redirect payment methods, the browserInfo parameter is now included in the state.data. Previously, some redirect payment methods didn't work on mobile.

• For Riverty, in the space for the consent checkbox:
  • The link for payment conditions now correctly goes to the terms and conditions.
  • For AfterPay, the terms and condition box now shows Riverty as the payment method name. .
    
• For AfterPay B2B, the consent checkbox is now removed.

Types are resolved when using different moduleResolution values within the Typescript config.

Payment methods that show a QR code and redirect button in checkout now show the redirect button before the QR code image.

A Typescript issue with the paymentMethodConfiguration object types.

Payment method variant:

• Klarna B2B (Billie). Payment method type: klarna_b2b.

• For SEPA, accessing component.data, no longer causes a crash. The properties ibanNumber and ownerName are now automatically populated with empty strings.
• For Click to Pay, the button to resend the confirmation code now works.
• The paymentMethodConfiguration typescript definition no longer causes a linter warning.

Adds support for the payment method ANCV.

• Timeouts on SecuredFieldsProvider are now reset after unmounting the Component. This avoids an error when mounting and immediately unmounting.

• An issue removed inline styles from iframe when the nonce attribute was set on the <style> tag. This is now resolved.
• The classes applied to the dateOfBirth field in personalDetails component are now correct.
• The Polish translations for the terms and conditions for Online Banking Poland are fixed.

If Drop-in or Component is inside of an iframe element on your website, you can now configure redirects to be performed on the top level window. To do this, set redirectFromTopWhenInIframe to true.

• Added additional safety checks to validate the user input when shoppers use co-badged cards.

For Bancontact cards, the paymentMethod.type is now bcmc. Previously, it was scheme.

If there's no expiry date included for a stored card, the payment form no longer shows the Expiry date field. Previously, it showed undefined/undefined.

For cards, the storeDetails property is no longer mistakenly set to true in some cases.

An error no longer causes the Postal Code field for some regions to accept zero characters, leading to failed validation.

• If you opt out of sending telemetry data and set analytics.enabled to false, the paymentMethod.checkoutAttemptId is set to do-not-track.
• Internal refactoring for some of the payment form inputs to improve the Typescript type safety.

When a page has more than one Card Component, the cvcPolicy and expiryDatePolicy properties can no longer be overwritten.

• For issuer lists, all logos now load correctly.
• The Refused result code is no longer missing.

• For Trustly, some text that describes payment method is shown above the Continue button.
  

• To follow a11y guidelines, some HTML markup elements changed.

• For the Advanced flow, if the update function changes the available payment methods, the payment method list reloads and shows the new payment methods.
• The aria-labelledby tag is no longer duplicated, so screen readers no longer read the tag twice.
• For Klarna, Drop-in no longer gets stuck in the loading state.

For card payments, if Click to Pay doesn't load after 5 seconds, the card payment form is loaded and shown instead.

• For screen readers:
  • Alt tags for card brand logos can now be read.
  • When a QR code loads, the Scan QR code text can now be read.
  • Refactored screen reader panel and provider type definitions.
• For cards, the securedFields label is now a decorative div element.
• Labels are no longer implicitly associated with the elements they label.

By default, input fields that aren't required now have indicators to show that they aren't required. To turn off the indicators, set showFormInstruction to false.

• More translations for many locales.

• For 3D Secure 2, authentication no longer fails because of threeDSServerTransID validation. Previously, some payments failed authentication because of a false mismatch of the threeDSServerTransID.
• For the Sessions flow, telemetry data now includes payment currency and amount.
• For QR code payment using Drop-in, the screen reader can now read information about payment status.
• The SRPanel for screen readers is no longer duplicated.

• For French meal vouchers, the PIN input field label is now Security code.

• Postal code input fields now includes regex validation that accepts hyphens between the 5th and 6th digits for Brazilian postal codes.

• For gift cards, when you use a custom brand logo, it now shows correctly.
• When using Drop-in in an iframe element, Apple Pay no longer causes Drop-in to crash.

You can now enable suggesting billing addresses when the shopper starts to enter their address in the payment form. Implement the new onAddressLookup function.

Payment method: Cash App Pay. Payment method type: cashapp.

For QR codes, the countdown timer can now be read by screen readers.

For screen readers:

• Drop-down menus options can now be read accurately.
• Payment method names in the Drop-in payment methods list now get read once. Previously, payment method names were read twice.

• For cards, if you set the installmentOptions property in the global configuration object, you now get a warning message.
• For Drop-in, if you set a payment method specific configuration property in the global configuration object, you now get a warning message.
• For Components, if you try to create an unrecognized payment method Component, you now get an error message.

• The SRPanel for screen readers now has the static type of srPanel. Previously the _id property was undefined.
• The CoreOptions object now includes types that were previously missing.
• Screen readers can now read the alt text for brand logos. Previously the aria-hidden attribute prevented this.

• For cards, the onBinLookup event now additionally contains paymentMethodVariant that specifies the card brand variant.
• For SEPA, the owner name and IBAN number fields now include labels to follow a11y guidelines.

• Images no longer fail to load and cause a crash. This fixes the known issue from v5.41.0 to v5.42.1.

On the Safari browser v16.4 or earlier, the payment form no longer shows errors when validating email address. This fixes the known issue from v5.42.0.

• The Custom card, SEPA and Redirect Components receive getImage errors when retrieving brand or validation icons. Fixed in v5.43.0.

• The PayPal component now supports Venmo.

• Client-side email address validation is improved.
• The screen readers now communicate errors regarding client-side email address validation.
• The GetImage property no longer causes a crash of the custom card Component.
• The typing of the BrowserInfo object has been fixed.

• The Custom card, SEPA and Redirect Components receive getImage errors when retrieving brand or validation icons. Fixed in v5.43.0.
• On the Safari browser v16.4 or earlier, the payment form shows errors when validating email addresses. Fixed in v5.42.1.

• The way images and assets are loaded internally. This shouldn't affect the code in your integration.

• The Custom card, SEPA and Redirect Components receive getImage errors when retrieving brand or validation icons. Fixed in v5.43.0.
• On the Safari browser v16.4 or earlier, the payment form shows errors when validating email addresses. Fixed in v5.43.0.

• The preselected number of installments for the installments component now works as expected.
• Decimal places are now shown correctly for all currencies in Chromium-based browsers.
• The Ticket Edenred Component now hides the expiry date field by default.

For online banking payment methods, terms and conditions now show above the Continue button.

In the payment form:

• Address input fields now accept the dash (-) character.
• Labels for input fields are no longer cut off on small screens. For example, the House number label now shows completely on a 320px viewport.

• For Boleto Bancário:
  • When the shopper selects the checkbox to send a copy of the payment form to their email, a validation error no longer occurs.
  • The first name and last name input fields now have more descriptive and accessible error messages.
• For BLIK, the input field for the verification code no longer includes suggested values, because verification codes aren't reusable.

• Apple Pay now supports recurring payments. Use the new recurringPaymentRequest property to accept recurring payments.
• For PayPal, you can now customize the Pay Later message. Set the new enableMessages property to true.

• For cards, the payment form now shows the scheme name Visa instead of the value in the descriptorName field.
• The Fieldset component now uses fieldset and legend elements. Screen readers can now read the relationship between different form controls.
• Brand icons for cards and QR codes now include alt text that corresponds to the brand name.

• For bank payments, the payment button in the payment form now no longer shows when the showPayButton property is set to false.
• For the Advanced flow with cards, the check for the object to show stored payment methods from the /paymentMethods response now correctly checks for storedPaymentMethods. Previously, it checked for storePaymentMethods.
• For Visa, the checkoutOrchestrator property is now named correctly. Previously, it was named checkoutOrchestator.
• For ApplePay:
  • The amount property is no longer passed to UIElement.
  • The configuration property is no longer passed to UIElement.
  • The Wallets configuration no longer uses deprecated values.
• For card payments that go through a successful 3D Secure 2 challenge, onComplete can no longer be mistakenly called more than once.

• For Adyen Giving, you can now add a message above the Donate button. In the DonationComponent configuration, use the new disclaimerMessage prop.
• Apple Pay now supports the eftpos card network.

• Increased contrast ratio for the outline of buttons and, when the payment form has more than 3 supported card brands, for the number that indicates the number of additional supported card brands.
• Error messages that occur in the drop-down list of issuers can now be read by screen readers.
• Accessibility improvements that follow a11y guidelines.

• Shoppers on mobile devices can now select an issuer from the drop-down list of issuers without error. This fixes the known issue from v5.37.0.
• For MB WAY, the payment form no longer shows more than one label for each input field.

This release enhances the accessibility of Web Drop-in and Components:

• We made major improvements related to how errors are handled by screen readers. For more information, see pull request in GitHub.
• We've updated a drop-down box that is used throughout Web Drop-in and Components to better support keyboard and accessible technology user interaction. For more information, see pull request in Github.
• We've improved UI text and translations for credit card payments in over 20 languages. For more information, see pull request in GitHub.

For payment methods that include a list of issuers, shoppers on mobile are not able to select an issuer from the drop-down list. Fixed in v5.38.0.

• You can now pass an ApplePayPaymentAuthorizationResult to the resolve/reject functions, which is automatically passed to the Apple completePayment function, for example:

Copy code
onAuthorized: (resolve, reject, event) => {
   reject({
     errors: [
          new ApplePayError(
            'shippingContactInvalid',
            'locality',
            'Field locality is required'
          ),
        ]
    })
}

By doing so, you can show useful error messages to your shoppers when the payment fails.

• For returning ACH Direct Debit shoppers, we now display the last four numbers of their bank account number for recognition.

• Drop-in and Components no longer have errors related to accessing localStorage when rendered in an <iframe> in a Google Chrome incognito window.

• For debit card payments, shoppers are no longer shown installment options, as installments aren't compatible with debit cards.
• The state of Blik Components can now only be accessed once the component is fully rendered, preventing errors.

• In Card Components and Card Drop-in, you can now add an optional disclaimer. The disclaimer may include a hyperlink, for example to link to your terms and conditions:

Example:

Copy code
disclaimerMessage: {
     message: 'By continuing you accept the %{linkText} of MyStore',
     linkText: 'terms and conditions',
     link: 'https://www.adyen.com'
 }

• You can now set the PayPal intent for an individual payment through the Drop-in or Component configuration. This value overrides the general one retrieved from your Customer Area.
• We now track amount and currency data of payments.

• Payment methods that use QR codes don't automatically redirect shoppers on mobile devices to the QR code's destination anymore. Instead, shoppers are presented an Open app button that redirects them to complete the payment.