Stellar

MPCVault supports XLM transfers, issued assets, trustlines, and custom Classic and Soroban transactions on Stellar Mainnet. Stellar wallets use networkType: "NETWORK_TYPE_STELLAR". Examples use API client signing.

Signing request types

Payload	Use
`stellarSendNative`	Transfer XLM or activate a new account; `value` is a decimal string in XLM.
`stellarSendAsset`	Issued-asset payment; `amount` is a decimal string in asset units.
`stellarChangeTrust`	Create an asset trustline.
`stellarSendCustom`	Custom Classic or Soroban transaction; `txBase64` is a base64 XDR envelope.

MPCVault builds transactions for the structured payment and trustline requests. For stellarSendCustom, the application supplies an assembled XDR envelope with its sequence, fees, and any required Soroban resource data and authorizations. MPCVault signs and broadcasts the transaction (broadcastTx defaults to true). To sign transactions you build yourself or messages you format yourself, use raw signing.

Tutorials

Tutorial	Implementation
Classic	Create and activate a wallet, add a trustline, receive USDC, then send it with a memo.
Soroban	Build and simulate an `invokeHostFunction` transaction, then submit its XDR for MPCVault signing and broadcast.

Memos

Stellar supports four memo types.

Memo type	Common use	Format
Text	Payment reference	Up to 28 UTF-8 bytes
ID	Exchange deposits	Unsigned 64-bit integer
Hash	External record reference	64 hex characters
Return Hash	Refund reference	64 hex characters

API support

Custom XDR: All four memo types.
Structured API: Text only. Other types are not yet supported.

Confirm a transaction

Query the txHash returned by MPCVault with a Stellar Mainnet RPC provider. This applies to Classic and Soroban transactions.

curl -X POST '<STELLAR_MAINNET_RPC_URL>' \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getTransaction",
    "params": {"hash": "<TRANSACTION_HASH>"}
  }'

Use txHash as <TRANSACTION_HASH>. The RPC response reports execution in result.status:

Status	Interpretation
`SUCCESS`	The transaction executed successfully on-chain.
`FAILED`	The transaction was included but failed; inspect `resultXdr` for the failure.
`NOT_FOUND`	The transaction is not in the provider’s retained history yet, or is outside its history window. Poll with an interval and timeout.

GetBalance queries a wallet’s current XLM or issued-asset balance. It does not identify which deposit changed the balance.

Getting Started

Wallets

Signing Requests

Batch Payments

Deposit & Sweep

TRON Watch Address

Signing request types

Tutorials

Memos

Confirm a transaction

​Signing request types

​Tutorials

​Memos

​Confirm a transaction

Signing request types

Tutorials

Memos

Confirm a transaction