Custodial wallets support transferring assets using the /transfer endpoint — the same interface used by non-custodial wallets. This provides a simple, chain-agnostic way to move funds without needing to encode raw transaction data.
All transactions from custodial wallets are executed server-side.
Initiate a transfer
For custodial wallets, only assets that are supported by the custodian can be transferred.Supported assets: OUSD, USDC, USDB, and EURCSupported chains: Tempo, Base, and Solana
Like non-custodial wallets, custodial wallets with an owner or additional_signers require an
authorization signature for transaction
requests.
Usage
Make a POST request to /v1/wallets/{wallet_id}/transfer with the source asset, amount, chain, and destination address:
The ID of the custodial wallet to send the transfer from.
object
required
The source asset, amount, and chain for the transfer.
Hide properties
string
required
The asset to transfer (e.g. "ousd", "usdc", "usdb", "eurc").
string
required
The amount to transfer as a decimal string in standard units (e.g. "10.0" for 10 OUSD). No
need to convert to smallest units.
'tempo' | 'base' | 'solana'
required
The chain to transfer from (e.g. "tempo" or "solana").
object
required
The destination for the transfer.
Hide properties
string
required
The recipient wallet address. Use a hex address for EVM chains and a base58 address for
Solana.
object
Additional options for custodial transfers.
Show properties
object
required
Payment initiation context. This should be provided depending on SCA requirements for
the custodial wallet. This context is passed to Bridge. Learn more about
Strong Customer Authentication
(SCA).
Hide properties
string
required
How the payment was initiated. Use p2p_mobile_payment for peer-to-peer transfers initiated
on a mobile device; other_mobile_payment for non-P2P mobile-initiated payments (e.g. a
merchant payment via a mobile app); other for payments not relying on a mobile device.
string
required
Whether the payment was made remotely or in person. Use remote for payments initiated
from a distance (mobile app, online banking, or e-commerce checkout); non_remote for
payments made in person (physical card, payment terminal, or contactless tap).
object
required
Payment initiation attestations for a transfer.
Hide properties
object
required
Strong Customer Authentication attestation for a transfer.
Hide properties
string
required
Whether Strong Customer Authentication (SCA) was applied or which regulatory
exemption or non-applicability reason covers this payment.
Outcome
Description
sca_used
The user authenticated with SCA.
payment_to_self
Payer and payee are the same person (remote only).
trusted_beneficiaries
Payee is on the user’s pre-approved list.
recurring_transaction
Amount and payee match a previously SCA-authorized recurring series.
contactless_low_value
Contactless card payment below the low-value threshold (non-remote only).
unattended_terminal_for_transport
Automated terminal for transport fares or parking (non-remote only).
low_value
Remote payment below the low-value threshold (remote only).
secure_corporate_payment
Dedicated corporate payment process with controls equivalent to SCA (remote only).
transaction_risk_analysis
PSP has performed real-time risk analysis and the transaction falls within permitted thresholds (remote only).
merchant_initiated_transaction
Payment triggered by the merchant without the payer present, on a pre-authorized mandate (remote only).
not_applicable
This flow requires initiation context but SCA and SCA exemptions do not apply.
other
Another recognized exemption not listed above.
object[]
Authentication factor metadata. Optional when outcome is sca_used; if provided,
it must contain at least two entries from different category values (e.g. one
possession factor and one knowledge factor). Omit this field for any other outcome.
Show properties
string
required
The type of authentication factor used: knowledge (something
only the user knows, e.g. a PIN or password), possession (something only the
user has, e.g. a phone receiving an OTP or a hardware token), or inherence
(something the user is, e.g. a fingerprint or face scan). When outcome is
sca_used, the two factors in auth_factors must belong to two different categories.
string
required
The ISO 8601 timestamp when this factor was authenticated.
string
required
Your internal identifier for this authentication event (e.g. a session ID,
transaction ID, or audit log reference). Used for reconciliation.
Returns
The response is a wallet action object with type: "transfer":
string
The wallet action ID. Use this to poll for status updates via GET /v1/wallets/{wallet_id} /actions/{action_id}.
string
The action status: pending, succeeded, rejected, or failed.
'transfer'
The action type.
string
The asset being transferred.
string
The amount being transferred in standard units.
string
The source chain.
string
The recipient address.
Next steps
Transfer lifecycle
Learn about the transfer lifecycle for custodial wallets
Sending USDC recipe
Learn how to format and encode ERC-20 token transfers
Authorization controls
Configure policies and multi-party approvals for custodial wallets
Transfer webhooks
Monitor transfer status and lifecycle events
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.