Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving address with credit card #5

Closed
kreativedev opened this issue Mar 11, 2013 · 1 comment
Closed

Saving address with credit card #5

kreativedev opened this issue Mar 11, 2013 · 1 comment

Comments

@kreativedev
Copy link

I just found your code and it looks exactly what I am looking for. I did notice when following your directions to save a credit card for a customer, it looked like the address info on a charge is all blank. Is saving the address info already built in, and I am just not seeing how to go about saving that as well? Or is that something that was on the roadmap to be added in later?

@jeffsmohan
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants