Outgoing transactions
Choose when to send a Travel Rule message and connect it to your withdrawal flow.
Send Travel Rule information to the beneficiary VASP and reconcile delivery and response updates. Your backend controls the on-chain payment; CryptoSwift manages the message and returns information for your decision.
Choose the integration flow
| Your withdrawal flow | Integration |
|---|---|
| You need a decision before broadcasting funds. | Pre-transaction flow: create without a hash, evaluate the result, then broadcast and add the hash or cancel. |
| Your release checks are already complete and you send information alongside the broadcast. | Post-transaction flow: create with the transaction hash as soon as it is available. |
Choose the timing required by your operating model. The API does not coordinate message submission with your blockchain broadcast.
Before you start
- Get a Sandbox API key and keep it on your backend.
- Use KYW to determine whether the destination is custodial, supplementing the result with your own tools or customer information where needed. For a customer-controlled wallet, follow your wallet verification policy.
- Configure webhooks and recovery polling so later message updates reach your application.
You may also create a Travel Rule message for a self-hosted destination. Set blockchainInfo.destinationType to NON_CUSTODIAL so CryptoSwift does not search for a beneficiary VASP.
Pre-transaction flow
- Create an outgoing message with
POST /transactions, omittingblockchainInfo.transactionHash. - Save the returned
idand evaluate the message status, available risk information, and optionalruleEnginedecision. - If your policy permits the payment, broadcast it and PATCH the hash. If you abandon it before broadcast, PATCH
CANCELLEDwith a reason. - Continue reconciling later delivery, response, and exception updates.
See the pre-transaction flow implementation for complete requests and waiting behavior.
Post-transaction flow
Create the message with the transaction hash as soon as the transfer is broadcast, save the returned ID, and monitor later updates. The response confirms the API request; delivery and beneficiary review may continue asynchronously.
See the post-transaction flow implementation for the request and response handling.
Key data points explained
Provide the asset, amount, destination wallet, and required originator and beneficiary data. Use the blockchain name from GET /blockchains; an unlisted blockchain may be supplied as free text, with potentially reduced routing and screening coverage. Include the beneficiary VASP name when known.
Use the Travel Rule data model for writable fields, statuses, risk results, and warnings. See transaction updates for PATCH restrictions and improving delivery data for counterparty selection.
Test your integration
Use the Sandbox counterparty scenarios to exercise delivery, confirmation, decline, cancellation, and timeout handling. The interactive demo shows the complete journey.
Each newly created outgoing transaction consumes one credit. See Credit usage.
Next steps
- Implement the pre-transaction flow
- Implement the post-transaction flow
- Apply Rule Engine decisions
- Handle webhook updates