Skip to main content
Move money instantly between two of your wallets. For the transfer lifecycle, read the Transfer object. Before you start, connect Natural to your agent or create an API key. See Start here. Setup takes a couple of minutes; the MCP path needs no API key.
If an MCP host is operating Natural for you, use the MCP example. The linked API reference has per-language samples and a playground.
Amounts are integer US cents: 50000 is $500.00.

Move funds

A transfer (trf_*) moves money between two wallets (wal_*) in the same party, landing in the same call; read status on the response. Create one with POST /transfers/internal. Internal transfers need more than one wallet on the party; see Create and manage wallets. An agent can move money into the Vault but not out of it.
When an agent (agt_*) creates, cancels, fulfills, or declines a payment, payment request, transfer, payment intent, refund, or voice session, it authenticates with its own credential (an agent key or an agent-scoped OAuth grant) and names the run with the X-Instance-ID header. Without it the call returns 400 missingInstanceId. Reads don’t need it.
The response carries the transfer (trf_*) and its status:
A transfer moves CREATED to PROCESSING to COMPLETED. It can pause at IN_REVIEW during an approval hold. It ends at FAILED, RETURNED, CANCELED, or APPROVAL_DENIED.