Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Upped SF version to 3.2.8 - where, inbuilt check for wrong number in single-branded card, is removed.
This check was failing to recognise new BCMC bins and throwing an error which then prevented
/binLookup
from working.So in the case of single-branded card components i.e. a card component hard typed to only accept a single brand e.g. 'bcmc' - securedFields now no longer try to detect what brand the shopper is actually typing to see if it is correct or not; instead relying on binLookup to do this
Tested scenarios
All test still pass.
sf v3.2.8 is available on Test & Live
New bcmc bins are recognised
Typin a non-bcmc card into a bcmc card component gives the expected "unsupported card" error
Fixed issue: COWEB-869