> ## Documentation Index > Fetch the complete documentation index at: https://docs.business.plvr.io/llms.txt > Use this file to discover all available pages before exploring further. # Cashless festival setup > Set up PLVR Tap end to end: top-up stations, payment methods, personalization questions, vendors and menus, approvals, wristbands and onsite staff. This guide walks through everything a cashless event needs, in the order that avoids rework. Plan to finish it at least a few days before doors open, because vendors need time to build menus and you need time to approve them. > [!NOTE] > > The **PLVR Tap** group and **Personalization Form** only appear in the event menu for events that have PLVR Tap enabled. If you do not see them, your event is not a Tap event. For the big picture first, read [PLVR Tap overview](/tap/introduction). ## Your setup at a glance | Step | Page | Done when | | - | - | - | | 1 | **Top-up Setup** | Every station and payment method exists | | 2 | **Personalization Form** | You have chosen what attendees are asked | | 3 | **Vendor Setup** | Vendors, sales locations, items and login codes exist | | 4 | **Approvals** | No submissions are left pending | | 5 | **Onsite Staff** | Every team member has a login code | | 6 | **Onsite Operations > Wristbands** | Spare wristbands are added | ## 1. Create top-up stations and payment methods Open **PLVR Tap > Top-up Setup**. **1. Add your stations** On **Top-up Stations**, select **Add Top-up Station** for every place where staff will add money to wallets. A mid-size festival might have **Main Entrance**, **VIP Area** and **Campsite**. Use the **Description** for instructions such as "next to the first aid tent". **2. Add payment methods** On **Onsite Payment Methods**, use **Quick add** for **Cash**, **Card**, **QR Payment**, **Bank Transfer** or **Other**, or add a **Custom Payment Method** such as Apple Pay. Only add the ones your team will actually accept. > [!WARNING] > > Payment methods here are for reporting only. They do not take payment. Your staff must take the money with your own cash box or card terminal. See [Top-up setup](/tap/top-up-setup). ## 2. Choose what attendees are asked Open **Personalization Form**. Attendees answer these questions when they personalize or claim a ticket, before a wristband is bound to it. * Use **Quick add** for standard questions such as **Phone Number** or **Date of Birth**, or write a **Custom question**. * Mark a question **Required** only if you really need it. * Drag rows to set the order, and set unwanted questions to **Inactive**. This is separate from the checkout [Registration form](/events/registration-form). See [Personalization form](/tap/personalization-form). ## 3. Create vendors Open **PLVR Tap > Vendor Setup**. Each stall, bar or merchandise stand is a vendor. **1. Add the vendor** Select **Add Vendor**, enter the **Name** (for example "Noodle Bar"), and keep **Status** as **Active**. An optional **Note** is internal only. **2. Add sales locations** Open the vendor and go to **Sales Locations**. Add each place the vendor sells from, such as "Main Stage Stall" and "Campsite Cart". **3. Add items** On **Items**, create categories if you want them, then use **Add Item**. Each item needs at least one sales location, a name and a price above zero. You can also leave this to the vendor, who submits items for your approval. **4. Generate login codes** On **Login Codes**, choose how many codes the vendor needs, add a **Note** such as "Alex - Vendor Manager", and select **Generate Codes**. Give the codes to the vendor. > [!TIP] > > Create one login code per person on shift, and use the **Note** to record who has which. When someone leaves the stall, set their code to **Inactive**. See [Vendors](/tap/vendors). ## 4. Approve what vendors submit When a vendor adds or changes an item or category, it waits for you. Nothing goes live on the menu until you approve it. 1. Open **Approvals**. A badge in the event menu shows when submissions are waiting. 2. Check each **Review Details**. For edits, compare **Current** with **Requested**. 3. Select **Approve**, or **Reject** with a clear **Rejection Reason**, which the vendor sees. 4. For many at once, tick the rows and use **Approve Selected** or **Reject Selected**. > [!WARNING] > > Do not wait until doors open. A vendor whose menu is still pending cannot sell it. Aim for an empty Pending list the day before. See [Approvals](/tap/approvals). ## 5. Create login codes for your team Open **Onsite Staff** and select **Add Staff**. * For the top-up team, choose the **Top-up staff** role, then pick their **Top-up Station**. Create a separate batch for each station. * For other roles, pick from the **Role** list. Each role shows a short description of what it is for. * To create codes for named people in one go, use **CSV Import** with the template, or **Manual Creation** with a **Note** like "Alex - Main Gate". * Set a code to **Inactive** when a shift ends. See [Onsite staff](/onsite/onsite-staff). ## 6. Add wristbands Open **Onsite Operations > Wristbands** and select **+ Add wristbands**. Enter or scan one wristband per line, add a **Note** about which box they came from, and select **Add**. You can add up to 200 at a time. > [!TIP] > > Read each result line. A band shown as newly registered when you expected an existing one usually means a mistyped ID. See [Wristbands](/onsite/wristbands). ## 7. Run a dress rehearsal > [!TIP] > > Every vendor shows **Active** with the right number of **Sales Locations**, **Items** and **Login Codes**. > [!TIP] > > In **Onsite Staff**, each Top-up staff code shows the right station under its role. > [!TIP] > > A test attendee can be found in **Search**, has a wristband bound (check the **Wristbands** list), and shows the expected balance after a top-up. > [!TIP] > > The test top-up and test purchase appear in **Cashless Activity**. ## Next steps > **[Event day runbook](/guides/event-day-runbook)** > > Run the day with Onsite Operations. > **[After the event](/guides/after-the-event)** > > Reconcile spending and settle with vendors. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.