Address Validation Status Not Accurate

[nschiffelbein]

It appears that Taxify is returning a range of statuses for address validity, one I'm receiving is: "ValidatedWithStreetLevelNormalization". However, the library is showing this as "NotValidated". It also appears that Taxify may have a bug in their system because validating a validated address returns a "NotValidated" response. Perhaps storing the raw status returned and using is_valid to determine if it is good or not would allow for more fine grained control over what is and is not valid.

[TonyDeStefano]

Thanks for letting us know. I have scoured Taxify's documentation and couldn't find any other possible return statuses. So I sent them a support request asking for a complete list. I do like your idea about storing the raw response and will implement that shortly. And once I get a list from Taxify, I'll add those options to the project as well. Thanks!

[nschiffelbein]

Excellent, I have an email into my account rep and another contact there asking about the double address validation bug. I'll let you know what I find out.

[TonyDeStefano]

Awesome, thanks! In the meantime, I just released version 1.0.1 which now stores the raw response from the address verification check. Feel free to update your project and see if that works better for you.

[nschiffelbein]

I received a response from one of my contacts at Taxify. It seems they have a bit of a gap in their address validation statuses. The current statuses are:

-Validated
-StreetLevelOverride
-CompleteOverride
-ValidatedWithStreetLevelNormalization
And if none of those apply we will return
-NotValidated

Taxify caches address validation requests for 60 seconds, and if you hit the cache the "NotValidated" status is returned every time rather than the original status. I have gone over the trouble with this with my contact since you can't reasonable decide if an address is genuinely bad or simply cached and not being re-checked. He is working with a developer there to put forward a proposal for a new invalid type status or some equivalent to indicate that you are genuinely getting a response vs. your request being skipped due to caching. He couldn't make any promises since they have to get the product managers buy in so I'll keep you posted.

[TonyDeStefano]

Thanks! This is the list I got from them last week:

Invalid Shipping, Invalid Billing AddressStatus Responses

• Null
• AddressOutOfRange
• ComponentMismatch
• NoStreetData
• UnknownStreet
• ZipCodeDoesNotExist
• ZipCodeDoesNotMatchCityState

Invalid Shipping, Valid Billing AddressStatus Responses

• NonDeliverableAddress

Valid Shipping, Valid Billing AddressStatus Responses

• AddressSuggested
• MultipleMatches
• Validated

Funny that it's completely different than your list and they also doesn't include NotValidated.

`¯_(ツ)_/¯``

I plan to integrate this stuff into the package when I get some time this week. If you are in a super hurry, feel free to fork it and do a pull request. I'm a tad behind on some other projects right now :)