Sending payments

Outbound money gets the most protection on the platform — every send routes through your policy engine and approval chains before anything moves.

One-time and recurring sends

New Payment sends to a vendor, a contractor, or any address — pick the wallet to pay from, the asset, and the recipient (free-form or from your Vendors directory / address book). Recurring schedules the same payment on a cycle — rent, retainers, payroll-like runs.

The controls that apply

• Approval chains — a $10k payout can require the same 2-of-3 sign-off your treasury uses; pending sends sit on the Approvals page until approved and signed.
• First-time recipient warning — when you pay an address your organization has never paid before, Pay says so before you confirm. Most payment fraud is a lookalike address; this makes "we've paid this vendor 14 times" versus "never seen this address" explicit.
• Whitelists — a policy can restrict outbound payments to address-book entries only.