> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/monetization/test-purchases.md).

# Test purchases without spending Silicon

You can price an item and buy it in the editor without spending real money. The store detects where the game is running and switches payment mode. There is nothing to configure.

The store is already in the project, and the item already has an effect. Those steps are on [Add the store to your game](https://studio-docs.sandbox.game/monetization/add-the-store.md), [Create and manage items](https://studio-docs.sandbox.game/monetization/create-and-manage-items.md), and [Connect items to gameplay](https://studio-docs.sandbox.game/monetization/connect-items-to-gameplay.md).

| Where the game runs          | Who sees draft items | Payments                      |
| ---------------------------- | -------------------- | ----------------------------- |
| In the editor, played by you | You, the owner       | Sandbox. You are not charged. |
| A published game             | No one               | Real money.                   |

## Step 1: Leave the item as a draft at its Silicon price

In `Store Manager`, set the Silicon price you intend to charge. Leave the item as a draft.

Players never see a draft. You are the only one who can buy it, and only in the editor.

## Step 2: Open the store in Play mode

Enter Play mode. Press `B` to open the store.

## Step 3: Top up with sandbox Silicon

Select `Get Silicon`. Sandbox checkout opens without leaving the game. Choose a pack and finish the checkout.

You are not charged. Your Silicon balance in the store goes up.

## Step 4: Buy the item

Buy the item in one click. Your Silicon balance goes down, and the item appears in `Inventory`.

A free item is claimed. The Silicon balance stays the same, and the item still appears in `Inventory`.

## Step 5: Use a temporary item

Use the item in play. The effect happens, and the store removes one from `Inventory`.

Skip this step for a permanent item. It takes effect when it is bought.

## Step 6: Start Play mode again

Exit Play mode, then enter it again.

A permanent item is still owned, and its effect is applied. A player who owns the flaming sword should start this session with it equipped.

## Step 7: Sign out and open the store

Sign out. Enter Play mode and press `B`.

`Shop` can still be browsed. Buying or claiming opens the sign-in popup. The game stays where it was.

## What You've Done

You have bought the draft with sandbox Silicon and checked the effect, a new play session, and the signed-out store. Publish the game, then publish the item, on [Publish, take down, and delete items](https://studio-docs.sandbox.game/monetization/publish-take-down-and-delete-items.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://studio-docs.sandbox.game/monetization/test-purchases.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.
