> For the complete documentation index, see [llms.txt](https://doc.relopay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.relopay.io/relopay-usage-terms/rates-for-virtual-cards.md).

# Rates for Virtual Cards

Below is an overview of the main fees associated with using your virtual card. This includes card issuance, transaction fees and other service-related charges.

We aim to keep our fee structure transparent and easy to understand. In most cases, the final amount already includes all applicable fees.

**Key points:**

* Top-up and transaction fees are calculated in cryptocurrency (USDT)
* Conversion fees apply when cryptocurrency is converted to fiat at the time of purchase
* Final amounts may vary slightly depending on the current exchange rate and blockchain network conditions
* No hidden fees — inactivity, annual service, and card cancellation are free

| Fee Type                     | Rate  |
| ---------------------------- | ----- |
| **Card Issuance**            | 3 USD |
| **Transaction Fee**          | $0.2  |
| **Declined Transaction Fee** | $0.5  |
| **Annual Fee**               | Free  |
| **Inactivity Fee**           | Free  |
| **Card Cancellation Fee**    | Free  |


---

# 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://doc.relopay.io/relopay-usage-terms/rates-for-virtual-cards.md?ask=<question>&goal=<user_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.
