All fund movements into or out of a Bridge wallet can be done through orchestration APIs. You can build flexible payment workflows to and from your Bridge wallet using any of the following APIs:
Transfers - Move money to and from a Bridge wallet. You can specify a Bridge wallet as a source or destination for a transfer.
Liquidation Address - Auto forward funds sent to a crypto address directly to your Bridge wallet. To do so, you can specify a Bridge wallet as the destination for the liquidation address.
Some Bridge Wallets require payment initiation data when they are used as a transfer source. Fetch the wallet before creating the transfer. If the wallet response includes initiation_required: true, include an initiation object in the Create Transfer request. If the field is omitted, do not include initiation.Send initiation only in the Create Transfer request. Bridge accepts it for compliance checks, but the field is not included in Create Transfer, Get Transfer, or List Transfers responses.
When attestations.sca.outcome is sca_used, auth_factors is optional. If you include auth_factors, send at least two factor objects from different categories. Each factor must include category, authenticated_at, and reference.Use the same initiation payload when retrying a Create Transfer request with the same idempotency key.
Use the Bridge Wallet history endpoint to retrieve deposits, direct deposits, withdrawals, returns, and undeliverables for a wallet in one consistent activity model.
You can enable webhook delivery for wallet activity by creating or updating a webhook endpoint subscribed to bridge_wallet.activity.