Please note that you must be business verified to be able to make a transfer. For more information, you may contact [email protected].
The transfers API allows sending funds between coins wallet accounts of different users. It allows sending funds with different currencies (ie.
BTC->BTC) and takes care of the necessary conversion between currencies.
- id - ID of the transfer record.
- account - Account ID of the user making the transfer.
- target_address - The wallet address of the recipient.
- payment - Specifies the outgoing payment ID of the transfer if the transfer was successful.
- exchange - The exchange ID for non BTC->BTC transfers, such as BTC->PHP.
- status - Specifies whether the transaction is
- created_at - Specifies the date when the transfer was created.
- HTTP 400 - Whoops! We had to update the Blockchain Fee to 0.0001. Please confirm before continuing. Fee amount is optional parameter, but when it's provided, we compare it with the current fee 0.0001.
- HTTP 400 - Ensure this value is greater than or equal to X The error depends on currency limits which are set in the system.
- HTTP 400 - Ensure this value is lower than or equal to X. The error depends on currency limits which are set in the system.
- HTTP 400 - Unsupported currency. The error appears when you specified a currency that is different from currency of sender account or target address.
- HTTP 400 - You cannot transfer to yourself. This happens when the specified target address is owned by the sender.
- HTTP 400 - Target account not found. This happens when the specified target address does not exist.
- HTTP 400 - Invalid address format. API failed to recognise a type of target address.
- HTTP 400 - You cannot transfer between addresses of the same account.
- HTTP 400 - Target account not found. In case we find out that target address is "internalcoin" (for example PBTC) and it does not exist, we return the error.
- HTTP 400 - Currency mismatch. It happens when user tries to send funds from account to target address and its currency is different from the account.
- HTTP 400 - Direct transfer is not allowed. We limit ability to send money from/to non Bitcoin accounts except the system ones.
- HTTP 400 - Sending funds from your account is temporarily disabled, please contact our customer support team. This happens when the sender's account is currently disabled.
- HTTP 400 - Insufficient balance. It happens when account does not have enough funds
to create a payment. Historically it's part of non field errors.
- HTTP 400 - Phone or email verification is required.
- HTTP 400 - This is a flagged Bitcoin address used in Phishing attacks, for the safety of your funds, we have locked down your account.Please contact our support team to reactivate. We block users who try to send Bitcoins to a blacklisted list of addresses. Original motivation was that our customers got a virus which replaced a Bitcoin address and funds were "stolen". To prevent that ASAP, we have added user blocking on API level.
- HTTP 400 - Sending bitcoins is temporarily disabled.
- HTTP 400 - To transfer with low priority, please send at least 0.001 BTC.
- HTTP 400 - Please update your application in order to process this payment.
- HTTP 400 - This payment would result in exceeding recipient's limit.
- HTTP 400 - This account is no longer active. Sending to inactive accounts is not allowed.
- HTTP 400 - The amount you are sending will exceed your recipient's daily limits. Please try sending a smaller amount or wait 24 hours to send the funds.
- HTTP 400 - This recipient's daily limits have been met. Please wait 24 hours to send funds.
- HTTP 400 - The amount you are sending will exceed your recipient's limits. Please try sending a smaller amount.
- HTTP 400 - Unfortuately you cannot send to this recipient at this time because their limits have been met.