This release applies only to on-chain stablecoin transfers (wallet transfers,
batch transfers, and bridging).
How Transfer Approvals work
Approvals on Dashboard
- Members can initiate wallet transfers (onramp/offramp restricted to Admins)
- Member transfers require Admin approval before execution
- Email notifications sent for approvals/rejections
- Admin transfers execute without approval
Approvals on API
A new parameterrequireApproval can be included when creating transfers. If set to true, the transfer will enter the approval workflow until it is approved or rejected.
Create Transfer with Approval
false, so existing integrations are unaffected. This gives you the flexibility to define your own rules for when Admin approval is required.
Endpoints
POST /wallets/transfers– stablecoin to stablecoinPOST /wallets/transfers/batches– stablecoin batchPOST /wallets/bridges– stablecoin bridging
Because bridging is quote based, quotes are only generated after approval. This
ensures that they do not expire while waiting for review.
Notifications
- Admins receive email notifications when a transfer is pending approval.
- Members receive email notifications when their transfer request is approved or rejected.
Webhooks
If your organization has enabled webhooks, you can also listen for transfer approval events:TRANSFER.APPROVAL.PENDING- Request for approvalTRANSFER.APPROVAL.APPROVED- Transfer was approvedTRANSFER.APPROVAL.REJECTED- Transfer was rejected