Withdrawal policy

1Introduction

This policy sets out how you can withdraw funds from your Swap Adipex Ai account: which methods exist, how long they take, which checks apply and what your responsibilities are. By requesting a withdrawal you accept the conditions described here and in the Terms of Use.

It complements the deposit and withdrawal methods page, with which it is consistent on methods, fees and timing.

2Available withdrawal methods

You can withdraw by bank transfer to an account with a CBU or CVU in your name, to Mercado Pago, or to the Visa or Mastercard card you used to deposit. We do not offer withdrawals to third-party accounts or to methods that are not in your name.

When you connect an exchange by API, the funds you hold there are managed directly at that exchange; this policy refers to the money that moves through Swap Adipex Ai.

3Processing times

Once the request is approved, the usual times are: up to 24 hours with Mercado Pago, 1 to 3 business days by bank transfer and 1 to 5 business days by card. Times start counting from approval, not from the moment you send the request.

Delays can add up from bank holidays, institution cut-off times, extra checks or technical problems at the bank or payment processor.

4Fees and costs

We charge no fee to withdraw. Your bank, wallet or payment processor may apply charges of their own that we do not control. If an operation involves converting currency, the cost of the conversion is shown before you confirm the withdrawal.

Current values are on the fees and pricing page.

5Withdrawal limits

The minimum withdrawal amount depends on the method chosen and is shown in the dashboard before you send the request. We may set daily or monthly limits based on risk profile, verification level and the requirements of our payment providers.

If you need to withdraw more than the limit, contact your personal manager: in some cases it is possible to split the withdrawal or complete an additional verification.

6KYC and AML checks

Before processing the first withdrawal we require identity verification to be complete and two-step sign-in to be on. For large or unusual withdrawals we may ask for information about the source of funds.

These checks follow the KYC / AML policy and respond to legal duties; they are not a penalty or a suspicion about you.

7Causes of delay or rejection

A withdrawal may be delayed or rejected if the destination account details do not match your name, if documents are incomplete or unreadable, if an additional check was triggered, if credentials changed recently or for technical or regulatory reasons.

When we reject a withdrawal we tell you the reason in the dashboard and by email, as far as the law allows, and we tell you what to fix to request it again.

8User responsibility

You must check that the CBU, CVU, alias or wallet account is correct and in your name. We cannot recover funds sent to a wrong account because of a mistyped detail, although we will try to help you with the receiving institution.

You are also responsible for keeping your account secure: anyone who gets in with your credentials can request a withdrawal, so verification codes must not be shared with anyone.

9Cancelling or changing a request

While the request shows as pending in the dashboard you can cancel it or change the amount. Once it moves to "in process" or has been sent to the bank or processor, it can no longer be cancelled or edited.

If you need to change the method or destination, cancel the pending request and create a new one. Every change goes through the security checks again.

10Support

If your withdrawal takes longer than indicated, write to [email protected] with your request number, or ask your personal manager. We usually reply within one business hour.

If you are not satisfied with the answer, you can file a complaint following the procedure described on that page.

11Policy updates

We may change this policy to reflect changes in our processes, in payment methods or in the rules. Changes take effect when published on this page, and the version in force is the one shown on the site.

If a change affects a request that is already in process, that request is resolved under the conditions in force when it was sent.