> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/integrations/get/currencies.md).

# Currencies

Currencies can be used to differentiate what people can buy with the [top ups](https://claude.ai/event/general/integrations/get/top-ups) you do for them. Here are some examples:

* **EUR**: A real currency where you can buy everything with.
* **Press currency**: The currency you use to top up the wristbands of the press people. This will probably be non-refundable and not allow them to buy merchandising with it.
* **VIP guest currency**: Non refundable, but can buy drinks, food, merchandising, ...
* **Suppliers currency**: The currency you use for your suppliers. They can buy drinks, but no merchandising or food as food is provided for them in the backstage catering tent.
* **Volunteers currency**: This currency could be used for everything as a volunteer has worked to earn this financial reward. This is refundable, but allowing them to spend it on your festival will lower your costs significantly.

### How GET currencies are different

{% hint style="info" %}
Currencies are **not** automatically synchronised from GET to Eventication. Unlike our other top up partners, GET currencies are **created by an event moderator** on Eventication, and the matching setup is configured on the GET side.
{% endhint %}

Because GET currencies are not fetched from their platform, the configuration of each currency — what it can be spent on, whether it's refundable, which products or POS it's valid at, … — has to be **discussed up front between your event and GET**. GET can help you create and configure these currencies on their platform so that the behaviour on the POS matches what you've set up on Eventication.

A good way to approach this:

1. List out the currencies you want to offer at your event.
2. For each currency, decide what people should be able to buy with it, and whether it's refundable.
3. Share this list with your GET contact and align the configuration on both sides.
4. Create the same currencies on Eventication and mark them as "**Use on platform**" so they appear where top ups are performed.

### Choosing a currency

When you top up a person's wallet, you will have to choose a currency. Your event can also nominate a default currency, which will be selected automatically with all new top ups. Moderators can pick another currency if they want.

Our [rewards](https://claude.ai/event/general/rewards) with top ups also require you to choose a currency. All rewards that are marked as given will result in a top up using the selected currency.


---

# 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.eventication.com/event/general/integrations/get/currencies.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.