For our software's other Payment Gateway integrations, to update a card number or billing address, the user simply deletes the stored token and sends a new authorization or capture transaction. A new token is then generated and returned.
It seems that Authorize.net is matching to the existing customer profile based on the card number, and returning the same token number as before.
If we want to update the billing address without changing the card number, the new billing address is not being saved to the customer profile through our regular call. AVS settings then prevent the new transaction from going through.
Is there a specific call that should be made when updating the billing address on an existing customer profile, without changing other information?
Thanks in advance!
(This is driving one customer nuts, since relaxing their AVS settings is not an option, and unfortunately there do not seem to be not different AVS settings for a known good card simply changing its billing address -- the card address is validated as if it were a fresh card -- if anyone has a workaround idea on the AVS side, that would be great also.)
