Postal Code should be a numeric input

[tlovett-rmn]

In the US, Postal Codes are purely numeric. The current box allows for text and so the keyboard does not default to a numeric keypad. It also allows does not limit to 5 characters or 5-then-4 characters.

Perhaps this is by design for internationalization, but it would be handy for US-only apps to specify a numeric input be used for Postal Code

[braebot]

Sounds like you're looking for another configuration option to restrict the postal code. I would think we should be more generic, and use regex's for folks to use in different countries. Something like a string extra: EXTRA_VALID_POSTAL_CODE_REGEX. The postal code would only be considered valid if it matches the regex. In your case, you'd want the regex from this SO post.

Would this be satisfactory?

[tlovett-rmn]

I'm less concerned about validating the input -- I can always do that after card.io returns data to me. I'm concerned about the UX that my US users see. I'd like them to get a numeric keypad to enter their zip rather than the default text keyboard since they won't need to enter any letters.

[braebot]

Hmm. You're suggesting that we restrict to numeric input with a boolean, something like EXTRA_POSTAL_CODE_NUMERIC_ONLY. If this extra is true, we only show the numeric input keyboard. Apparently a lot of countries use numeric only postal codes.

[tlovett-rmn]

Yeah, exactly! I think it would be a UX improvement that our users would really appreciate.

[braebot]

Fixed in 5.3.0.