Saving address with credit card about authorizesauce

[jeffsmohan]

Thanks! Part of the design philosophy behind the AuthorizeSauce library is to use Authorize.net as little as possible because their APIs are poorly conceived, poorly documented, and poorly maintained. The point of saving a credit card in their system is mainly to avoid having to prove annoying levels of PCI compliance, but that concern doesn't exist with address information.

So basically, the decision was that you can store the address information on your systems, how you want to, and have total control over it (for example, you can access it without the overhead of an API call) right alongside storing a token to reference the card info when needed.

Is there a use case or reason for needing to store the address info with Authorize.net that I missed?