> For the complete documentation index, see [llms.txt](https://docs.reveel.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveel.id/use-cases/embedded-wallets.md). # Embedded Wallets Reveel Pay(ID) API for Embedded Wallets #### Summary Integrate Pay(ID) directly into embedded wallets to enable seamless cross-chain stablecoin transfers within the wallet UI. #### Who It's For * Embedded wallet providers * Consumer or app-native wallets * Developers building wallet SDKs for games or apps #### Problem Users must bridge assets or manually switch networks to send funds — creating friction, loss of funds, or dropped transactions. #### How Pay(ID) Solves It By linking the embedded wallet to a user's Pay(ID), all cross-chain routing and settlement is handled via Reveel’s API. Users can send any stablecoin to any recipient without leaving the wallet interface. #### Implementation Outline * Register a Pay(ID) for each wallet user * Set the embedded wallet as the primary settlement wallet * Integrate Pay(ID) resolution + send flow via Reveel API #### Outcome / Benefits * Simplified UX = higher conversion and retention * Embedded wallet becomes the user’s default stablecoin wallet * Increases TVL and user activity --- # 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.reveel.id/use-cases/embedded-wallets.md?ask=&goal= ``` `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.