Getting started
This guide walks you through setting up a FluxStore store from a fresh sign-up to taking your first payment. You’ll create the store, add packages, connect your Minecraft server, and turn on a payment provider.
Most server owners finish in 30 to 60 minutes, depending on how many packages they’re migrating in.
Before you begin
You’ll need three things to follow this guide end to end:
- A FluxStore account. Sign up free at fluxstore.net using email or SSO (Discord, Google, GitHub, Microsoft, or Minecraft).
- A Minecraft server (Java Edition) with console access. Bukkit, Spigot, Paper, and Velocity are all supported.
- A Stripe or PayPal account for accepting payments. You can defer this if you want to build the storefront first.
Your store stays in test mode until you connect a payment provider. Build out the catalogue, customise the theme, and invite teammates without anything going live.
The five steps
The setup flow is the same for every store. Each step links to a focused guide if you want the detail.
1. Create your account
Sign up with email or SSO. We strongly recommend turning on two-factor authentication immediately. You can do that under Dashboard > Account > Security with any TOTP app.
See Account Management.
2. Create your store
From the dashboard, create a new store. You’ll be asked for a name and an IP. The name is what shows on the storefront and in customer emails. The IP is shown to customers as the connection address.
You get a free *.fluxstore.net subdomain for every store, and you can connect a custom domain later. By default the storefront is served on the Clean template; you can switch templates later without losing any of your packages or settings.
See Creating a Store.
3. Add packages
Packages are what customers actually buy. They can grant any commands you like (ranks, kits, cosmetics, currency, anything). FluxStore supports four package types out of the box:
- Standard. A one-time purchase that runs a list of commands.
- Timed. Same as standard, but with an expiry date that fires a removal command.
- Tiered. Customers buy “up” from a lower tier and pay only the difference.
- Cumulative. A package the same player can buy multiple times.
Group your packages into categories to control the storefront layout. Drag and drop to reorder. You can also flag packages with Pay what you want pricing or restrict them to specific servers in your network.
See Packages and Categories.
4. Connect your Minecraft server
Install the FluxStore plugin on your server. The plugin connects to FluxStore over a persistent WebSocket connection, so commands fire the moment a payment is confirmed.
You’ll add the server in the dashboard, copy the server token it generates, and paste that into the plugin’s config. The plugin reconnects automatically if your server restarts, and any commands that fired while you were offline queue up and deliver when the connection is back.
See Server Setup and Plugin Installation.
If you run a multi-server network, repeat this step for each server. You can scope packages to specific servers, or run a command on every connected server with Global Commands.
5. Turn on payments
Connect Stripe or PayPal under Dashboard > Payments. FluxStore takes no platform fees on either provider, so the only deduction is whatever your provider charges (typically 1.5% to 3% plus a fixed fee per transaction).
If you want to support multiple currencies, configure them under Dashboard > Settings > Currencies. Customers will see prices in their local currency at checkout, with live exchange rates.
See Stripe Setup and PayPal Setup.
Test a real purchase before you announce the store to your community. Run one transaction on yourself for the smallest package to confirm the full payment-to-command flow works end to end.
After your store is live
Once you’re taking payments, the day-to-day work shifts from setup to running the store. The most useful next steps:
- Customise the storefront. Pick a template, tune the theme tokens, or build a fully custom layout with Liquid. See Customisation.
- Run promotions. Coupons, scheduled sales, and gift cards live under Dashboard > Sales. See Coupons.
- Set up Discord. Auto-assign roles when customers purchase, and pipe purchase notifications into a Discord channel. See Discord.
- Invite your team. Add staff with scoped permissions across 29 dashboard areas. See Team Management. (Pro)
- Build on the API. A REST API for headless storefronts and webhook notifications for real-time integrations. See the Management API. (Pro)
Stuck?
If something doesn’t behave the way this guide describes, Plugin Troubleshooting covers the most common server-side issues. For everything else, contact support from inside the dashboard and we’ll dig in.