In Transit Fund Transaction
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Response
Non-empty if the request failed
Non-empty if the request failed
Bearer authentication of the form Bearer <token>, where token is your auth token.
Non-empty if the request failed
Non-empty if the request failed
Available to: Organization administrators
Environments: Live
Rate Limit: No endpoint-specific limit
Record a wire deposit that has been initiated but hasn’t settled yet. This creates a fund transaction with status InTransit and can make the incoming funds tradable right away, so your customer doesn’t have to wait for the wire to clear before trading.
When the transaction is recorded, the deposit amount is credited to the account’s tradable cash balance up to your organization’s remaining funds-in-transit cap. In-transit funds are tradable but not withdrawable. If your organization has no cap configured, the transaction is recorded without a tradable credit.
Field Details
Only wire deposits are supported — fundPaymentType must be WTR, and fundAmount must be greater than zero.
The transactionIdentifier is required and must be unique per account. It acts as an idempotency key: submitting the same identifier again returns the existing transaction with a "Duplicate transaction identifier" error instead of creating a second record.
The fundCurrencyId must correspond to one of the supported currencies: USD, EUR, AUD, GBP, or CAD. Currency IDs are environment-specific — use the /currency/list endpoint to retrieve valid IDs.
The fee fields (feePaymentType, feeAmount, feeCurrencyId, feeDescription) are optional and are recorded on the transaction if provided.
Common Failure Scenarios
fundPaymentType is any value other than WTRtransactionIdentifier matches an existing transaction on the accountError Messages
Related Endpoints
submitFundTransaction to submit standard deposit and withdrawal requests.