Every Tempo feature in this section is in beta and available through the API only. To get access, contact your Customer Success Manager (CSM).
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
Addmemo 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.
POST /v1/operations/tempo/transfer
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”.