> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/products/cash/direct-pay.md). # Direct Pay mode How your card spends from your stablecoin and Liquid vault balances, and how to set which one pays first. Your card spending works through one of two modes: Direct Pay mode and Borrow mode. In Direct Pay mode, each purchase is settled from the balances already in your account, with no loan involved. In Borrow mode, the card borrows against your assets rather than spending them directly. For details on the borrowing option, see [Borrow](/etherfi/products/borrow.md). ## What your card can spend Direct Pay draws on two kinds of balance: * **Stablecoins:** USDC, USDT, EURC and frxUSD * **Liquid vault balances:** Liquid USD, Liquid RWA, Liquid Reserve and Liquid EUR When spend is drawn from your Liquid vault balance, the card pays directly from your vault. There is no need to withdraw first. ## Choosing which balance pays first In **Set Spend Priority**, select the asset you want the card to use first. Every purchase will draw on that balance before any other. If it can't cover a purchase, the card pays from another balance that can. ## If you have an open loan A portion of your balances may be reserved to back an open loan. The card can only spend what isn't backing that loan, so the amount available from a given asset may be lower than its total balance. --- # 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://etherfi.gitbook.io/etherfi/products/cash/direct-pay.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.