> 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/weezpay/top-ups.md). # Top Ups Top up an EventPay wallet from Eventication ### Understanding Top Ups In the realm of event management and engagement, the WeezPay platform emerges as a tool designed to make top up transactions faster and easier. It's accessible via the Eventication website, which allows moderators to add funds to wallets of their visitors with no effort. ### Features * **Instant**: It's *really* quick. Once a moderator completes a top-up transaction on the Eventication website, the funds are immediately available in the WeezPay wallet, ready to be used for drinks or other things. * **Regulated by moderators**: WeezPay top-ups offer a level of control to event organizers that is both practical and necessary. Events can predetermine the maximum amount allowed for a single top-up, a feature that aids in budget control and prevents excessive spending or plain typo's. * **Permissions**: The system grants moderators the capability to determine who can perform top-ups. By selectively using these permissions, organizers can secure the transaction process and minimize the risk of unauthorized financial activities. We don't want that. ### Experience For moderators this means they do not need to have many different devices with them for their ability to top up certain wallets. Just use Eventication, which is available on all smartphones. Easy peasy lemon squeezy 🤗 ## Export A CSV of all top-ups with a lot of information can be exported. --- # 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.eventication.com/event/general/integrations/weezpay/top-ups.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.