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

# Tempo Memos

> Attach a 32-byte on-chain reference, such as an invoice ID, to a TIP-20 transfer on Tempo so the recipient can match the payment without a separate message.

> [!NOTE]
>
> Every Tempo feature in this section is in beta and available through the API only. To get access, contact your Customer Success Manager (CSM).

A memo is a short reference that travels on-chain with a TIP-20 transfer. When you set one, Fireblocks calls the token's `transferWithMemo` function instead of `transfer`. The token then emits a `TransferWithMemo` event that carries the memo alongside the sender, recipient and amount. The recipient, or any system that reads the chain, can match the payment to an invoice, order or customer without a separate message.

## Add a memo

Add `memo` to the destination of a `POST /v1/operations/tempo/transfer` request. The memo must be exactly 32 bytes in UTF-8. Fireblocks rejects any other length with a 400 error. You can't use a memo on a transfer with multiple destinations.

```json POST /v1/operations/tempo/transfer theme={"system"}
{
  "assetId": "PATHUSD_TEMPO_MODERATO_TEST_O46L",
  "amount": "100",
  "source": { "type": "VAULT_ACCOUNT", "id": "5" },
  "destination": {
    "type": "VAULT_ACCOUNT",
    "id": "8",
    "memo": "INV-2026-000123-PAYOUT-BATCH-007"
  },
  "externalTxId": "e1f2a3b4-c5d6-4e7f-9a0b-1c2d3e4f5a6b"
}
```

## Rules

* **It's public.** Anyone can read the memo on a block explorer. Don't put personal data, account numbers or secrets in it.
* **It's stored as raw bytes (`bytes32`).** Explorers and contracts show it as hex. Decode it as UTF-8 to read the text back.
* **TIP-20 tokens only.** Fireblocks rejects a memo on an ERC-20 transfer with a 400 error: "memo is only supported for TIP-20 tokens".
