> For the complete documentation index, see [llms.txt](https://support-143.gitbook.io/movez-gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-143.gitbook.io/movez-gitbook/movez-introduces-membership-cards.md).

# MoveZ Introduces Membership Cards

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAFRNFVfxBtxifLFR6Pg%2Fuploads%2F9uezwLQtkN01d7BnkA40%2FIMG_4161.MP4?alt=media&token=b94add78-7e9b-4b23-9d2c-9dc22a3456f7>" %}
MoveZ Membership cards video.
{% endembed %}

## The Membership Cards

*These cards summarise the account information such as holder's name, token amount, wallet address, expiration date, and tier.*

The system was designed to benefit both, current users as well as incentivises new users to join in on the fun. So how does it all work?

* User downloads/opens the MoveZ app.&#x20;
* 5 days free trial starts. New joiners can activates the app. (on the back-end tokens are pre-approved for free) as a one time requirement and gets to enjoy the app for free for 5 days. For existing users, once signed in they need to click on the card and they too get to experience the upgrade for 5 days for free. No tokens required.&#x20;
* Re-activate membership. After the 5 trial days are up, users can re-activate their membership for another 5 days using the $BURNZ accumulated during the trial period.&#x20;

*<mark style="color:orange;">Please note: there will be enough tokens available to accumulate over the 5 days trial period to enable membership renewal for another 5 days.</mark>*&#x20;

After the trial period ends users are provided with two options:&#x20;

**Option 1:** select a membership plan anything from 5 days to 90 days. The more days you add the lower the cost and the higher the rewards ratio.&#x20;

**Option 2:** upgrade to a tier payable with $BURNZ tokens. **A higher tier ensures high rewards can be claimed.** To upgrade tier or purchase the first tier, users will be required to top up their account with $MOVEZ tokens. This can can easily be done within the app, with the click of a button. Fiat payment solution will be available in the future. Once users topped up their account with $MOVEZ, they are then able to choose their tier and only able to select that tier if there is enough balance. Otherwise the user will be prompted to top up to secure the tier of preference. Once the tier has beens selected the $MOVEZ tokens will automatically be staked so the user can enjoy access to the app. The staked tokens will be shown on the card as 'locked' tokens.&#x20;

In the manner above, users are able to upgrade or downgrade their tiers with one-click and all from within the app. Existing users will still be able to benefit from these changes as they will receive automatic 20X-30X booster on their current earnings!&#x20;

*To learn more about how to boost your earning click here:* [*Booster NFT mint guide*](/movez-gitbook/booster-nft-mint-guide.md)*.*


---

# 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://support-143.gitbook.io/movez-gitbook/movez-introduces-membership-cards.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.
