Skip to main content
Four resources cover everything that moves money in or out of an account. Deposits, payouts, and returns exist in both APIs; counterparties are specific to the 2026-05-01 API; the 2023-01-01 API takes the destination inline on the payout.

Deposits

Incoming transfers credited to one of your accounts. A deposit appears once the funds are final and has one status, settled.

Payouts

Outgoing transfers from an account to a bank account or wallet. A payout moves initiatedsubmittedsent, or ends failed or returned (2026-05-01 statuses).

Counterparties

The bank account or wallet on the other side of a payment, saved once and referenced by counterparty_id. Every payout targets one. Deposits carry one where the rail delivers the sender’s account details; ACH does not share the originator’s account number, so inbound ACH deposits have none.

Returns

A deposit sent back to its sender. An outbound payment with the same lifecycle as a payout, linked to the deposit it undoes; the deposit stays settled.

Where to find them

Every completed movement also lands as a booked transaction on the account, and each state change fires a webhook.

Rails

The rail is how the money travels. It follows from the currency and the counterparty’s financial address; for USD you choose it on the payout. Each page covers timing, limits, and return behavior.

ACH

USD, batch-based, same-day or next-day. Returns within the network windows.

Fedwire

USD, real-time and final. No return procedure on the network.

SWIFT

International USD over the correspondent network. Returns can arrive net of fees.

SEPA

EUR, standard and instant.

Faster Payments

GBP, near-instant.

Blockchain

Stablecoins to and from linked wallets on supported chains.
Test any of these without moving real money: see Sandbox Mode and the Simulations walkthrough.