Foxy Forum Status

We're no longer responding to questions via our forum, but we will keep it up for historical reasons. If you can't find the answer you're looking for, please visit our knowledge base or contact us. If there's enough interest in the future, we may bring the forum back.

How do customers update info previously saved through the Foxy Checkout page?

carlos123carlos123 Member
in Help edited January 2014
I have been looking and Googling and looking some more and while I have found some snippets of documentation that sort of talk about this topic...there is nothing that sets things out in a crystal clear fashion so...I am asking.


It is my understanding (please correct me if I am wrong) that the Guest and Account terminology on the Foxy Checkout page has absolutely not one thing to do with PayPal Guest and Account anything. My client (whose store uses Foxy) has been under the impression for a long time that the Guest and Account under the email address had everything to do with PayPal and was quite surprised to hear from me that it had nothing to do with PayPal (suggestion: you may want to clarify that somewhere in your documentation as it even had me confused for a while).

It is also my understanding (and again please correct me were that is wrong) that a Guest checkout is one and the same as checking out without saving any of the info entered into the Foxy Checkout page.

That an Account checkout is one and the same as saving the info entered into the Foxy Checkout page for future use by the customer.

Now to my (and my client's) question....

How does a customer update their saved Foxy Account information?

My guess is that they simply checkout as an Account holder and that whatever information had previously been saved by Foxy for that account is overwritten by any new information entered this time around. client tried to change an address that way and could not save his changed info in that manner.

Some of your documentation says...
If the cart parameter is set to updateinfo, the cart will immediately redirect to the checkout in “updateinfo” mode. Simply put, this will process an empty transaction, thus allowing the customer to update their password, address(es), or payment info. This updated information will be sent in a transaction datafeed, but the payment gateway will not be contacted during this checkout. (

...which implies that updating is a factor of how the Cart is called.

The store uses version 0.7.2.

Any input on this would be appreciated.


  • winstonwinston FoxyCart Team
    Hey @carlos123

    A couple of points:

    1) There is no correlation between paypal accounts and Foxycart accounts. You are correct on that point. You can use our SSO functionality ( ) to create accounts for your website and Foxycart at the same time, but that still will not relate in any way to Paypal. I don't think you have any need for SSO, but I just wanted to clarify.

    2) To update the cart, you'd need to send the user to a link like which will immediately take them to a blank checkout where they can login and update their information.

    The customer is also free to override any saved information, it is merely a convenience to help them checker faster!

    Hope that helps!
  • Excellent response Winston! Thanks.

    So am I correct in understanding that the only purpose for a customer entering a password under their email address is either to create a Foxy account on the fly (if they don't have one) OR retrieve their previously entered info from the FIRST time they checked out and created their account on the fly?

    I mean if they can't update the info that is saved through the checkout page (when going through a normal checkout) then it is only the info they entered during the first checkout they created an account through (assuming no updates have occurred through the URL you mentioned since then).



  • fc_adamfc_adam FoxyCart Team

    The first part of our checkout page has some nice logic in there. So first off, you can set it (via the admin) to only allow guest or account checkouts, or allow both but default to one or the other. If you allow account based checkouts, then after a customer enters their email address, we check the database to see if that email address has an account already created for that store. If it does, then we display a message saying that we've found their account, and provide a password field for them to complete the login and load in all of their previously entered saved information. If that email address hasn't checked out before, and the customer has selected to create an account, we display 2 password fields for them to create a new password.

    Any time that a customer logs in to a previously saved account (whether as part of a purchase action, or using the updateinfo action you mentioned earlier), any information they change on the checkout will be saved as their new information. So if they change their address, when they login again, the checkout will be preloaded with that new address.
  • Thanks for the additional feedback Adam but if I may ask...

    If changed customer info is saved both through a cart update URL call AND when they login through the checkout page by entering a previously used email address and password...what is the purpose of having an update of information through a cart update URL call as a path to update info?

    Would it not be easier to simply direct people to update their saved info by logging in through the checkout page and change their info in connection with a purchase?

    Hmm...well I can think of one possible use for the URL path to update...if they needed to update without making a purchase I suppose.

  • fc_adamfc_adam FoxyCart Team

    That's exactly it - people aren't always needing to purchase a product. You don't have to use the updateinfo approach, but if someone does have the desire to update their address info without purchasing, that's the way to do it.
  • Though this is an older thread, it has helped me with a client who asked how they can update their saved data without having to make a purchase.

    However, I have two questions:

    - how can they remove/delete their records?
    - If Foxy keeps their full payment/card details, can you point towards a statement that shows how Foxy protects data, as a third party payment processor? This would be helpful for crafting our GDPR statement.
  • fc_marijafc_marija FoxyCart Team
    Hello @simonclay -

    You can read about our security and PCI-compliance here:

    Other information:

    With regard to the customer removing their details:
    If a customer has saved details, there is currently not a way from them to remove the information themselves. If you are comfortable using our API ( you can remove saved credit card details using the save_cc parameter by setting it to 0.

    Another option would be to overwrite the card number with a test number (for example, 4111111111111111) using our legacy API, which is a bit easier, but still requires some technical knowledge. You can submit the requests via curl in your computer's terminal. We have some details on how to do it on our wiki here:

    You'll want to see this section: "How to change a customer's email address:" If you need to, you'll get the customer_id using the email, then change the email address and credit card number (cc_number=4111111111111111) to remove the account or just the credit card number to keep the account and just have the test card attached.

    You can get the API key (store secret) from the "advanced" settings in the Foxy administration. Here's a link:

    One of those scripts is good to have on hand, but if you're unable to do that, we can remove payment data for you. You can just request it through our helpdesk (
Sign In or Register to comment.