> For the complete documentation index, see [llms.txt](https://developer.paywall.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving.md).

# Card Saving

- [1. New Card](https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving/1.-new-card.md): It is recommended to perform the process of adding a new card only through your servers (Back-End). Direct access from your applications (End Users) is not recommended.
- [2. New Card / Tokenization](https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving/2.-new-card-tokenization.md): You can store the tokenized card information obtained via the client on your servers, along with the relevant user details.
- [3. Saved Cards](https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving/3.-saved-cards.md): It is recommended to retrieve stored card data only through your servers (Back-End). Direct access from your applications (End User) is not recomme
- [4. Delete Card](https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving/4.-delete-card.md): It is recommended to perform the deletion of a stored card only through your servers (Back-End). Direct access from your applications (End User) is not recommended.
- [5. Update Card](https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving/5.-update-card.md): It is recommended to perform stored card update operations only through your servers (Back-End). Direct access from your applications (End User) is not recommended.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.paywall.one/payment-orchestration-integration-document/card-storage-service/card-saving.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.