> For the complete documentation index, see [llms.txt](https://fantasy-scripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fantasy-scripts.gitbook.io/docs/coin-shop-system.md). # Coin Shop System {% embed url="" %} **A complete in-game premium shop system for FiveM servers featuring a modern dark-themed visual interface, dual currency economy, Tebex monetization integration, multi-stage VIP subscriptions, and a fully configurable product catalog covering vehicles, weapons, items, and player customizations.**\ \ **This script provides everything needed to run a polished server store without touching a database or writing a single line of code. Compatible with ESX, QBCore, and QBox frameworks with automatic detection and seamless integration.** **Features:** **Multi-Framework Support**\ \- Auto-detects and integrates with ESX, QBCore, and QBox\ \- Shared bridge layer normalizes framework calls into a single API **Dual Currency Economy**\ \- Coins (premium currency via Tebex)\ \- Playpoints (earned through playtime)\ \- Both usable in the same shop\ \ **Modern NUI Shop Interface**\ \- React/TypeScript-based UI\ \- Clean card layout with category filtering\ \- Live stats and instant purchase feedback\ \- No restart required for product updates\ \ **Tebex Integration**\ \- Purchases handled externally via Tebex\ \- Players redeem transactions in-game using transaction IDs\ \- Keeps payment flow secure and external\ \ **VIP Subscription System**\ \- Three tiers: Silver, Gold, Diamond\ \- Monthly coin rewards\ \- Store discounts (5–20%)\ \- Linked to Tebex products with automatic renewal\ \ **Vehicle Shop with Test Drive**\ \- Display vehicle stats (speed, acceleration, braking)\ \- Test drive system with routing bucket isolation\ \- Configurable timer and return system\ \ **Weapon Shop**\ \- Supports GTA and custom weapons\ \- Displays stats (damage, fire rate, accuracy, range)\ \- Built-in database with fallback support\ \ **Item Shop**\ \- Sell consumables and server items\ \- Works with ox\_inventory, qs-inventory, or framework inventory\ \ **Packs and Bundles**\ \- Combine multiple items into one purchase\ \- Supports vehicles, weapons, items, and currency\ \- Ideal for starter packs and promotions\ \ **Player Customization Store**\ \- Name changes\ \- License plate changes\ \- Phone number changes\ \- Full database synchronization\ \ **Playtime Rewards**\ \- Automatically reward Playpoints over time\ \- Configurable intervals\ \ **Currency Conversion**\ \- Convert Coins to Playpoints and vice versa\ \- Configurable exchange rates\ \- Minimum limits supported\ \ **Redeem Code System**\ \- Admin-generated one-time codes\ \- Redeemable in-game\ \- Supports Coins or Playpoints rewards\ \ **Discord Logging**\ \- Logs all transactions to webhook\ \- Includes purchases, conversions, VIP claims\ \- Custom embed styling supported --- # 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://fantasy-scripts.gitbook.io/docs/coin-shop-system.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.