> For the complete documentation index, see [llms.txt](https://docs.polystream.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polystream.xyz/polystream/crypto-fiat-ramp.md).
# Crypto-Fiat Ramp
Polystream integrates a seamless crypto-to-fiat on/off ramp solution, allowing users to easily convert between traditional currencies and cryptocurrencies directly within the application.
### Architecture
Architecture diagram
The crypto-fiat on/off ramp solution in the Polystream frontend uses three main components:
1. **Privy Authentication**: Handles user identity and wallet management
2. **Transak Integration**: Provides the fiat-to-crypto conversion services
3. **Native UI Integration**: Creates a seamless user experience within the app
---
# 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://docs.polystream.xyz/polystream/crypto-fiat-ramp.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.
