> 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/planning/members/top-up-integration.md).

# Top-up integration

Top-ups for your visitors made easy

If you have a [top-up integration](https://docs.eventication.com/event/general/integrations.md), use this page to top-up your visitor.

### Status

Here you can see the synchronization status of your visitor. A green badge will be shown if the visitor is synced to the top-up service.

<figure><img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fa2rQPYl7Uc9iMiGpsE1l%2FSCR-20250603-nqro.png?alt=media&amp;token=fc224c6c-7512-4ab3-9bee-27da899276c9" alt="" width="134"><figcaption></figcaption></figure>

### Top-ups

This is a list of top-ups your visitor has already received with the status.

{% hint style="info" %}
A top-up can have different statuses:

* **Pending**: The top-up has been created and will be synced to the service soon (under a minute for most integrations).
* **Success**
* **Failed**: Something went wrong. Check the logs for more details
* **Revoked**: The top-up has been revoked (pulled back).
* **Awaiting payment method**: The user might now have been synced yet, or no payment method is attached. Check your top-up service for more details.
  {% endhint %}

Here you will also see if a top-up came from a [top-up reward](https://docs.eventication.com/event/general/rewards/top-up-rewards.md), or is a one-time top-up.

Click the <img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-5de07eebe72670821ca764c9583a69a6e3734703%2Fplus%20new.jpg?alt=media" alt="" data-size="line"> button to create a new top-up for this visitor.


---

# 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/planning/members/top-up-integration.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.
