You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
isPotenitallyValid should be false when Cardholder name begins with a number. Just like when '0' is entered into the credit card field. The field has no potential to be valid from this point so isPotenitallyValid should be set to false.
The text was updated successfully, but these errors were encountered:
👋 @cmacdonnacha thanks for reaching out. You raise an interesting use case that we need to carefully consider. Although I can see us changing this behavior, we have to do a little research to make sure that cardholders can't actually set their names to include numbers. Additionally, this could be a breaking change to what we deem "potentially valid" and not necessarily a fix in buggy behavior. I've updated the labels on this issue so that we take this feedback into consideration for the next major version,
General information
Issue description
isPotenitallyValid
should befalse
when Cardholder name begins with a number. Just like when '0' is entered into the credit card field. The field has no potential to be valid from this point soisPotenitallyValid
should be set tofalse
.The text was updated successfully, but these errors were encountered: