> 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/2nd-generation-wallet-linked-debit-cards.md).

# 2nd Generation: Wallet-Linked Debit Cards

The second generation of crypto cards introduces more advanced functionalities by directly linking debit cards to users’ crypto wallets. This approach provides greater flexibility and real-time access to digital assets. Here’s how these cards operate:

* Direct Wallet Connection: The card links directly to the user’s crypto wallet, allowing the user to select which assets to spend.
* Real-Time Conversion: When a transaction is initiated, the system checks and debits the crypto balance in real-time, converting it to fiat at the moment of purchase.
* Authorization and Spending: Transactions are authorized once the conversion is complete, making these cards more dynamic and versatile.

These cards, often offered by regulated fintech companies like Wirex and Revolut, reduce the need for pre-funding and provide more control over spending. However, they still involve some level of custodial risk, as the funds are held by the card issuer until the point of transaction.


---

# 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/2nd-generation-wallet-linked-debit-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.