Withdrawal initiation with API#
Our service supports multiple withdrawal methods tailored to different payment systems. While the API endpoint remains unified, the required fields vary depending on the withdrawal method chosen.
Merchants should select the most suitable option for their specific needs, keeping in mind that certain methods come with limitations based currency, provider, or region. If you're unsure which withdrawal type is relevant for your use case, our technical support team is available to assist and guide you to the appropriate option. The sections below outline the necessary parameters for several base types, along with the examples and limitations.
Withdrawals are initiated via an API request to the endpoint. Examples of requests are described below. See the general endpoint specification at the bottom of this page.
Supported payment methods#
General API specification#
Withdrawal currency must be specified using the unique currency code from the supported currencies list (see the Currency column there). Cryptocurrencies with the same currency symbol can be deployed on different networks and under different contracts. Use network-specific currency codes, such as pUSDC for a Polygon-based asset, to avoid ambiguity.
Callback on Withdraw request#
The system will send a callback when the request is processed. The callback will have a special type and will be sent to the same URL that is used for deposit callbacks. More information can be found on the transaction callbacks for deposits and withdrawals page.
Idempotency#
This API uses orderId as an idempotency key. If this parameter is provided, the system prevents double spending in case of network error or processing failure. For withdrawal requests this field must be unique.