Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$upgrader is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 67 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$updateer is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 68 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$admin is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 69 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$acf is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 70 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$query is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 71 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$screens is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 73 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$features is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 79 Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Core::$integrations is deprecated in /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 83 Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::hasChildren($allow_links = true) should either be compatible with RecursiveDirectoryIterator::hasChildren(bool $allowLinks = false): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 57 Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::rewind() should either be compatible with FilesystemIterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 35 Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::next() should either be compatible with DirectoryIterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 42 Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 47 Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 37 Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 41 Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 37 Deprecated: Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/wp-content/plugins/all-in-one-wp-migration-master/lib/vendor/servmask/filter/class-ai1wm-recursive-newline-filter.php on line 28 Deprecated: Calling get_class() without arguments is deprecated in /var/www/html/wp-content/plugins/wordfence/lib/wfScanMonitor.php on line 123 Deprecated: Calling get_class() without arguments is deprecated in /var/www/html/wp-content/plugins/wordfence/lib/wfScanMonitor.php on line 124 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php:67) in /usr/src/wordpress/wp-content/themes/rooster-cms/inc/rooster-caching.php on line 4 Warning: session_cache_limiter(): Session cache limiter cannot be changed after headers have already been sent (sent from /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php on line 67) in /usr/src/wordpress/wp-content/themes/rooster-cms/inc/rooster-caching.php on line 5 Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html/wp-content/plugins/multiple-domain/MultipleDomain.php on line 497 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/advanced-custom-fields-component_field/src/Core.php:67) in /usr/src/wordpress/wp-content/themes/rooster-cms/inc/wordpress-hooks.php on line 8 Deprecated: Using null as an array offset is deprecated, use an empty string instead in /var/www/html/wp-includes/class-wp-theme-json.php on line 2397 Contactless Payments & Avoiding Declines | NatWest Rooster Money

With app version 7.3.0 and up, parents and kids can now reset their card contactless in app to avoid payment failures due to Strong Customer Authentication!

What are SCA Declines?

Like all payment service providers, NatWest Rooster Money is required to be compliant with Strong Customer Authentication (SCA) regulations. SCA regulations require your child to periodically validate their identity when making purchases by using their PIN. Your child will be asked for their PIN after 5 consecutive contactless transactions, or when they’ve spent £135 cumulatively without the use of Chip & PIN. Whichever comes first! This is exempt in situations where a PIN cannot be used (e.g. public transport) and your child should not be declined for SCA. 

You can find out more about SCA and how it works here.

How you can better manage SCA with your child

Reset Contactless

The only way to satisfy SCA is to do periodic identity checks – so we know fraudsters aren’t using your child’s card without your knowledge! Therefore, instead of entering their PIN at checkout, you and your child have the option to reset the SCA “counter” directly via the app. 

Every time contactless is reset, your child will be able to make 5 consecutive or up to £135 in contactless transactions before they’ll be asked for their PIN, or until contactless is reset on the app again.

You an find the option to Reset Contactless by following these steps:

  • Tap “Card” under your child’s name on the family dashboard
  • Tap “Reset Contactless”
  • Tap the button to confirm your child has their card
  • Your child’s contactless has now been reset

Note: before you can Reset Contactless, you will be asked to verify your device through steps shared in the app.

We'll keep you posted

If you have push notifications enabled for Rooster Money, we’ll let you and your child know when they’ve hit 5 contactless payments in a row, and when their next payment would require a PIN. Tapping on the notification will take you to the Reset Contactless screen so you can quickly and easily reset it there. You can click here to find out how to enable notifications.

Help your child set a memorable card PIN

On the occasion your child is asked for their PIN at checkout, all they have to do is enter their PIN number and the transaction should go through. They can view their PIN anytime by going to their Card Settings and by tapping “View Pin”. If your child hasn’t done so already, they can change their PIN to a memorable one by going to an ATM and selecting ‘Card services’ which gives an option to change the PIN. Learn more about managing your Rooster Card PIN here.

If you have any questions about Strong Customer Authentication or Reset Contactless, please get in touch with the team via the Contact Us button in the app or via hello@admin.test.rooster.money.

Make sure you've updated to at least app version 7.3.0 to access these changes:

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.