> For the complete documentation index, see [llms.txt](https://docs.wirexpaychain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wirexpaychain.com/wirex-pay/evolution-of-crypto-debit-cards/1st-generation-reloadable-prepaid-cards.md).

# 1st Generation: Reloadable Prepaid Cards

The first generation of crypto debit cards emerges as a simple and practical way for users to spend their cryptocurrencies. These cards are essentially fiat prepaid cards that can be topped up with digital assets. Here’s how they function:

* Custodial Control: Users convert their cryptocurrencies into fiat currencies through a custodial provider.
* Pre-Funded Accounts: Fiat funds are then deposited into a pre-funded account linked to the card.
* Usage: The card can be used for transactions just like any other prepaid card, with funds preloaded and ready to spend.

While these cards provide a straightforward way to use crypto for everyday purchases, they require users to trust a central entity to manage and hold their funds. This custodial setup poses inherent risks and limits the appeal to users who prefer control over their assets.


---

# 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://docs.wirexpaychain.com/wirex-pay/evolution-of-crypto-debit-cards/1st-generation-reloadable-prepaid-cards.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.