Validate and execute one or more fund transfers. The request body accepts an array of transfer items, supporting both internal transfers (between accounts on the same connection) and external transfers (to a counterparty via ACH, wire, SWIFT, SEPA, etc.). All items in a single request share a batchId and optional executionDate. Each item must provide either destinationAccountId (internal) or counterparty (external). The required counterparty fields depend on the rail:
name, accountNumber, routingNumbername, accountNumber or iban, swiftBic, bankCountry, and typically addressname, iban, optionally swiftBicUse the Idempotency-Key header to safely retry requests without creating duplicate transfers.
OAuth 2.0 Client Credentials issuing JWT Bearer access tokens.
Client-generated idempotency key to prevent duplicate transfer creation.
One or more transfer items to execute.
1Scheduled execution date for all items. If omitted, transfers execute as soon as possible.
Opaque client-defined metadata attached to all created transfers.