Are you looking for test card numbers?

Would you like to contact support?

Secured Fields release notes

Learn about the changes and improvements to our Secured Fields JavaScript library.

Secured Fields Component replaces all older versions of Secured Fields (versions 1.x.x). To get the latest functionality, we recommend to use Secured Field Components.

Older versions will still be supported, but newer functionality will be released on Secured Fields Component. If you are currently using an older version of Secured Fields, see the documentation here.

Secured Fields 1.5.2 (March 18, 2019)

This release includes:

  • Fixes for issues with device fingerprinting: for when there are multiple cards configured in Secured Fields and for the errors generated when initialising Secured Fields the second time.
  • Fix for the missing 4-digit placeholder when using American Express saved card details. 
  • Support for propagating the last 4 digits of a card number in the endDigits property of  onFieldValid  callback object.

Secured Fields 1.5.1 (January 28, 2019)

This release includes:

  • Fix for an issue in iOS Safari where the numerical keyboard won't retract.
  • Fix that allows setting a blank placeholder.

Secured Fields 1.5.0 (January 7, 2019)

This release includes the fix that allows shoppers with Kaspersky Internet Security and SafeMoney enabled in their browsers to proceed with entering their card details in the input fields.

We added an iframe that will trigger Kaspersky Internet Security to prompt shoppers to authorize loading iframes from Adyen. If the shopper allows iframes to load or the shopper does not have Kaspersky installed, the normal iframe will be loaded.

Secured Fields 1.3.4 (December 3, 2018)

This release includes:

  • Support for device fingerprinting within Secured Fields resulting to improved performance compared to the CSE implementation.
  • Improved tabbing navigation on Firefox.
  • New aria-placeholder  and aria-label attributes.
  • Fix to now allow deleting spaces between card numbers.
  • Additional supported card types for onBrand callback: naranja, cabal, shopping, argencard, troy, forbrugsforeningen

Secured Fields 1.3.3 (October 15, 2018)

This release includes:

  • A bug fix to prevent the error message briefly shown on iOS Safari when typing a 13-digit Visa number.
  • Support for styling validated fields.

Secured Fields 1.3.2 (October 8, 2018)

This release includes new error handling when a shopper types a wrong card number into a single branded card field. For example, SF will generate an error after typing 7 digits Visa number into a BCMC field.

Secured Fields 1.3.1 (October 1, 2018)

This release includes the new Secured Fields callbacks callback and showWarnings property in the configuration object.

Secured Fields 1.3.0

This release includes: 


  • Support for dynamically setting CVC placeholder length based on card brand.


  • A bug fix for iOS Safari blur event that was not firing and was causing card validation errors for BCMC.


  • Changes in property names for onFieldValid callback object.

  • Improved formatting of card numbers for single branded cards.

Secured Fields 1.2.1

This release includes the fix for issues on blur and focus events on iOS Safari causing unexpected behavior in input fields.

Secured Fields 1.2.0

This release includes: 


  • Support for allowedDOMAccess property in the configuration object.

  • Support for 19-digit Visa numbers. 
  • Replaced data-hosted-id with data-cse attributes.


  • Support for placeholder styling on IE and Firefox. 
  • Downgraded postMessage event origin mismatch messages from error to warning. 
  • New properties on onFieldValid and onFocus callback objects.

Secured Fields 1.1.4

If you're using version 1.1.4 of Secured Fields, we recommend migrating to the latest version. See Migrating to Secured Fields 1.3.0 or later.

This release includes improved expiry date validation and sending the resulting error message to the onError callback.