> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/adobe-commerce-extension/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/adobe-commerce-extension/adobe-commerce-extension-3.1.3/configure-the-digital-river-extension/shopper-experience/saving-payment-methods.md).
# Saving payment methods
Learn how shoppers can save their payment methods.
Shoppers can save their payment methods to their account during checkout or through their store account.
## Checkout
To save a credit card during checkout, select the check box named **Yes, please** **save this account and payment information for future purchases**.
## My Account
To save a credit card to the shopper's account:
1. Sign in to **My Account**, select **Stored Payment Methods**, click **Add New Payment**.\
2. Enter the billing address information and click **Continue**.\
3. Enter the credit card information.\
4. Select the **Yes, please save this account and payment information for future purchases**, and click **Add New Payment Method**.
## Using a stored payment method
To use a stored payment method during checkout, select the radio button next to the payment method you want to use and click **Use Stored Payment**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digitalriver.com/adobe-commerce-extension/adobe-commerce-extension-3.1.3/configure-the-digital-river-extension/shopper-experience/saving-payment-methods.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
