BLUF: Shamefully still a problem in 2023, HOWEVER the workaround using "123 Main St" as your billing address still works.
SO.. as a software developer I can deduce the likely causes for this error, AND recognize that it should have been fixed by the dev or QA teams 2 years ago. Good grief. Since it only happens to some customers, there are several possibilities: (a) the nature of some street addresses causes an issue (fails some pattern match or there is a length issue - either way that would be very poor design), (b) an old verification database is being used that does not recognize some newer street addresses as valid (also very poor system design if that's the case - should not be using a static address verification source), or (c) "123 Main St" is a testing value left in the system that bypasses the address verification altogether (the root cause is then still unknown, but the workaround works).
