> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usexfg.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Send and Receive XFG: A Step-by-Step Guide

> Complete walkthrough of sending XFG to another address, attaching payment IDs, and confirming receipt with simplewallet or the Fuego TUI.

Fuego (XFG) transactions are sent and received using `simplewallet`, the command-line wallet included with the node suite. Every Fuego address starts with the prefix `fire`, derived from the network's Base58 prefix. The process takes only a few commands: open your wallet, verify your balance, and broadcast the transfer. This guide walks you through each step.

<Steps>
  <Step title="Open your wallet">
    Launch `simplewallet` and point it at your wallet key file. If `fuegod` is running on the same machine you can omit the daemon flags; otherwise add `--daemon-host` and `--daemon-port`.

    ```bash theme={null}
    ./simplewallet --wallet-file wallet.keys
    ```

    Enter your password when prompted. The wallet will sync with the daemon and display your current block height before dropping you into the interactive console.
  </Step>

  <Step title="Check your balance">
    At the `[wallet]` prompt, run:

    ```
    balance
    ```

    The output shows your **available balance** (spendable now) and any **locked balance** (outputs waiting to mature). You need sufficient available balance to cover the amount plus the minimum fee of 0.008 XFG.
  </Step>

  <Step title="Get the recipient's address">
    Ask the recipient for their Fuego address. All valid addresses begin with `fire` and are roughly 97 characters long. You can display your own address at any time with:

    ```
    address
    ```

    Example address format:

    ```
    fireXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    ```
  </Step>

  <Step title="Send the transfer">
    Use the `transfer` command with the recipient address and amount:

    ```
    transfer <recipient_address> <amount>
    ```

    For example, to send 10 XFG:

    ```
    transfer fireXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 10
    ```

    The wallet displays the transaction fee (0.008 XFG, applied automatically) and asks you to confirm before broadcasting. The mixin is set to the network minimum of 2 automatically.
  </Step>

  <Step title="Confirm the transfer">
    Once the transaction is broadcast, verify it was sent:

    ```
    list_transfers
    ```

    This prints a table of all outgoing and incoming transactions, including hash, amount, fee, and block height. Look for your transaction with a status of **spent** or **confirmed**.

    <Note>
      After a transaction is included in a block, your newly received outputs are locked for **10 blocks** (`CRYPTONOTE_DEFAULT_TX_SPENDABLE_AGE = 10`) before they can be spent. At the 480-second block target, that is roughly 80 minutes. The locked amount will appear in your balance but will not be available to send until those blocks pass.
    </Note>
  </Step>
</Steps>

## Using payment IDs

Payment IDs let merchants and exchanges correlate a specific deposit to a customer or order. You can attach a payment ID to any transfer using the `-p` flag:

```
transfer <recipient_address> <amount> -p <payment_id>
```

A payment ID is a 64-character hexadecimal string, for example:

```
transfer fireXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 5 -p a1b2c3d4e5f60718a1b2c3d4e5f60718a1b2c3d4e5f60718a1b2c3d4e5f60718
```

## Integrated addresses

An integrated address encodes both the recipient's address and a payment ID into a single string, making it impossible for the sender to forget to include the payment ID. Generate one from inside `simplewallet`:

```
create_integrated <payment_id>
```

The resulting integrated address can be shared with payers exactly like a regular address. When you receive a payment to an integrated address, `list_transfers` will show the embedded payment ID alongside the transaction.