Skip to main content
A counterparty is a named destination or source for money movement: a saved recipient record your entity must have on file before initiating a payout. Counterparties are scoped to a specific entity via entity_id and can be either individuals or businesses. Payment details (bank account numbers, routing info) are attached separately and linked to a counterparty.

​
Counterparty types

A counterparty is individual or business. The profile object required to create one differs by type: Every counterparty also has a relationship to the sending entity, which describes why your platform pays or receives from them: vendor, supplier, customer, or employee. This is required for both types and has no effect on routing. It exists for your own reporting and reconciliation.
nickname defaults to first_name + last_name for individuals or legal_name for businesses if you don’t set one explicitly.
See Create a counterparty for the full request schema and worked examples for both types.

​
The counterparty object

See The Counterparty object for the full field-by-field schema.
Counterparties are reusable. Create one per recipient and reference its id for every future transfer instead of recreating it each time. A single counterparty can hold multiple payment details, for example several bank accounts and stablecoin wallets, so you can route to whichever one fits the transfer.

​
What’s next

Send a payout

Initiate a transfer to a counterparty using their saved payment details.

Counterparties API reference

Full endpoint documentation for creating and managing counterparties.