> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/reference/stacks.js/stacks-transactions/builders/makestxtokentransfer.md).

# makeSTXTokenTransfer

Constructs and signs a STX token transfer transaction. This is the primary function for sending STX from one address to another. For multi-sig transactions, all signer keys are provided and the transaction is signed automatically.

If you need to sign the transaction separately (e.g. with a hardware wallet), use `makeUnsignedSTXTokenTransfer` instead.

***

### Usage

```ts
import { makeSTXTokenTransfer } from '@stacks/transactions';

const transaction = await makeSTXTokenTransfer({
  recipient: 'ST1SJ3DTE5DN7X54YDH5D64R3BCB6A2AG2ZQ8YPD5',
  amount: 1000000n, // in microSTX (1 STX = 1,000,000 microSTX)
  senderKey: 'b244296d5907de9864c0b0d51f98a13c52890be0404e83f273144004b81874603',
  memo: 'test transfer',
  network: 'testnet',
  fee: 200n,
  nonce: 0n,
});

const serializedTx = transaction.serialize();
```

#### Notes

* The `amount` is denominated in **microSTX** (1 STX = 1,000,000 microSTX).
* If `fee` is omitted, the fee is estimated automatically via the network.
* If `nonce` is omitted, the nonce is fetched automatically from the network.
* For multi-sig transfers, provide `signerKeys`, `publicKeys`, and `numSignatures` instead of `senderKey`.
* The `memo` field is optional and limited to 34 bytes.

[**Reference Link**](https://github.com/stx-labs/stacks.js/tree/main/packages/transactions/src/builders.ts#L206)

***

### Signature

```ts
function makeSTXTokenTransfer(
  txOptions: SignedTokenTransferOptions | SignedMultiSigTokenTransferOptions
): Promise<StacksTransactionWire>
```

***

### Returns

`Promise<StacksTransactionWire>`

A promise that resolves to a signed `StacksTransactionWire` object, ready to be broadcast.

***

### Parameters

#### txOptions (required)

* **Type**: `SignedTokenTransferOptions | SignedMultiSigTokenTransferOptions`

```ts
// Single-sig options
interface SignedTokenTransferOptions extends TokenTransferOptions {
  senderKey: PrivateKey;
}

// Multi-sig options
type SignedMultiSigTokenTransferOptions = TokenTransferOptions & {
  publicKeys: PublicKey[];
  numSignatures: number;
  signerKeys: PrivateKey[];
  address?: string;
};

// Shared base options
type TokenTransferOptions = {
  /** The recipient address (STX address or contract ID) */
  recipient: string | PrincipalCV;
  /** Amount to transfer in microSTX */
  amount: IntegerType;
  /** Optional memo string (max 34 bytes) */
  memo?: string;
  /** Post conditions for the transaction */
  postConditions?: PostCondition[];
  /** Post condition mode (Allow or Deny) */
  postConditionMode?: PostConditionMode;
  /** Whether the transaction is sponsored */
  sponsored?: boolean;
  /** Transaction fee in microSTX */
  fee?: IntegerType;
  /** Transaction nonce */
  nonce?: IntegerType;
} & NetworkClientParam;
```

For single-sig, provide `senderKey`. For multi-sig, provide `publicKeys`, `numSignatures`, and `signerKeys`.


---

# 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://docs.stacks.co/reference/stacks.js/stacks-transactions/builders/makestxtokentransfer.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.