> For the complete documentation index, see [llms.txt](https://docs.hit.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hit.one/1000x/payouts.md).

# Payouts

When a position on Hit One closes, your USDM is sent back automatically.

There is no claim button.

There is no withdrawal step.

Your payout includes any remaining collateral plus realized profit, minus the close fee on profitable trades.

### What you get back

The formula:

`Payout = collateral + realized PnL − close fee`

The close fee is `5%` of profit.

It applies only on profitable trades.

Losing trades have no close fee.

#### Worked examples

These examples use a `$10` trade amount at `750x` leverage.

After the `1%` open fee, collateral is `$9.90`.

| Outcome | PnL    | Close fee | Payout   |
| ------- | ------ | --------- | -------- |
| Win     | `+$50` | `$2.50`   | `$57.40` |
| Win     | `+$10` | `$0.50`   | `$19.40` |
| Loss    | `−$5`  | `—`       | `$4.90`  |

### Stop loss closes

If a stop loss closes your position, you receive the collateral that remains inside the stop loss buffer.

The exact amount depends on the buffer at your leverage.

For details, see [Stop Losses and Liquidation](/1000x/stop-losses-and-liquidation.md).

You can never receive less than zero.

If the market moves so fast that the loss would exceed your collateral, payout is capped at zero.

You forfeit your collateral.

You never owe additional funds.

### Where the payout goes

Payouts are sent to the same wallet that funded the spin.

That is your Privy embedded wallet on MegaETH.

The token is `USDM`.

You cannot redirect a payout to a different address.

To move `USDM` elsewhere, withdraw or bridge from your wallet after the payout arrives.

### When the payout arrives

Once a position closes, the payout is queued and sent shortly after.

Under normal conditions, `USDM` appears in your wallet within seconds.

Brief delays can happen if:

* The MegaETH network is congested
* Many positions closed at the same moment
* Your wallet UI refreshes slower than the on-chain confirmation

### Refunds

Hit One automatically refunds your trade amount if a spin fails after the deposit is confirmed.

You do not need to do anything.

The refund is queued the same way as a payout.

This covers cases like:

* The market spread was too wide at open
* The exchange could not open the position
* Another server-side failure happened after the deposit

If funds are received but no position is opened, the trade amount is auto-refunded after `24 hours`.

### If a payout is delayed

If a position closed but no payout appears after several minutes:

1. Refresh your wallet view.
2. Check your trade history for payout status.
3. Contact support via the app's Intercom with your trade ID if the trade is closed and nothing arrived.

### What's next

* [How it works](/1000x/how-it-works.md)
* [Stop Losses and Liquidation](/1000x/stop-losses-and-liquidation.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://docs.hit.one/1000x/payouts.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.