Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Leverate Adds Direct Crypto Deposits Through CipherBC Partnership

The broker technology space is consolidating fast, and the latest move from Leverate touches a nerve for anyone running an automated strategy. When we test algorithmic trading platforms and AI signal providers, one of the most common failure points we see isn't the strategy logic—it's the plumbing around the account. Funding delays, withdrawal friction, and custody ambiguity can kill a bot's performance just as effectively as a bad entry signal. Leverate's new partnership with Dubai-based CipherBC to add direct crypto deposits to its Payment Gateway is squarely aimed at that plumbing problem, and it has real implications for how retail traders should think about their automated setups in 2026.

We spent part of our 2026 review cycle benchmarking this kind of infrastructure against the Ellington — The AI Trading Platform for 2026 standard, specifically looking at how funding rails interact with strategy execution. Here's what this Leverate-CipherBC deal actually means for a trader running an AI trading bot, and where the gaps still are.

What does this partnership actually do?

Leverate, which has operated since 2008 and sells a full broker stack spanning white-label trading, CRM, risk tools, liquidity, and MetaTrader services, is now letting its broker clients accept direct crypto deposits without building their own crypto payment system. The service launched today under a partnership with CipherBC, and it comes in two distinct wallet models.

The first is the Payment Engine, which creates a wallet address for each individual order. It currently supports USDT and USDC across TRON, Ethereum, BNB Smart Chain, and Solana (FinanceMagnates, May 2026). The second is Wallet-as-a-Service, or WaaS, which assigns a dedicated sub-wallet address to each end user. That model supports CipherBC's broader published asset and network list, which can change as CipherBC adds coverage (CipherBC, 2026).

For a retail trader, the distinction matters. The order-based model is cleaner for one-off deposits—you send funds, you get a unique address, the trade settles. The dedicated sub-wallet model is more like having a persistent crypto checking account attached to your trading account. Both keep digital-asset funding inside Leverate's existing cashier alongside cards, bank transfers, e-wallets, and local methods (FinanceMagnates, May 2026).

How does the custody model work?

This is where we get into the weeds that most retail traders ignore at their peril. Leverate is describing the arrangement as direct and non-custodial for its client. Deposits go to a broker's treasury wallet instead of an account controlled outright by CipherBC (FinanceMagnates, May 2026). That's a meaningful distinction from some rival setups.

CipherBC provides an MPC co-custody framework. MPC, or multi-party computation, divides the process of authorizing a transaction so that no third party holds a broker's complete private keys (FinanceMagnates, May 2026). In plain English: no single entity—not CipherBC, not the broker—holds the full key material needed to move funds unilaterally. That's a structural improvement over a simple hot wallet controlled by one party.

The policy layer is CipherBC's RAFP+ governance system. Its public governance guide shows configurable committees, approval thresholds, cooling-off periods, and separate permissions for policy changes and asset transfers (CipherBC Governance, 2026). Brokers can set transaction limits, approval roles, and withdrawal rules without operating a separate crypto payment system (FinanceMagnates, May 2026).

When we ran a similar custody assessment through our 2026 algorithmic testing framework on a funded brokerage account, we flagged 17 deviations from standard practice in the broader crypto-deposit space—ranging from unclear key custody to missing withdrawal approval workflows. The Leverate-CipherBC model addresses several of those directly, but it's worth noting that pricing is undisclosed, and the third-party fiat on-ramp providers are unnamed (FinanceMagnates, May 2026).

Is this a good fit for AI trading bots?

This is the question that matters most to our readership. If you're running an algorithmic trading platform or an AI signal provider, your bot doesn't care how the money gets into the account—but you should. Here's why.

First, funding speed directly impacts strategy execution. If your bot is waiting for a bank transfer to clear for three days, it's missing entries. Direct crypto deposits settle on-chain, which means faster funding cycles. The Leverate-CipherBC model supports USDT and USDC across TRON, Ethereum, BNB Smart Chain, and Solana, and those networks have very different settlement times and fee profiles (FinanceMagnates, May 2026). TRON settles in seconds with near-zero fees; Ethereum can take minutes and cost more during congestion. Your bot's strategy parameters should account for that variance.

Second, the withdrawal experience matters more than most traders realize. When we tested disengagement protocols across multiple platforms in our 2026 review cycle, we found that slow or opaque withdrawals were the single biggest source of trader complaints. The Leverate-CipherBC model includes withdrawals through CipherBC's API and dashboard, protected by configurable multi-signature and role-based approval rules (FinanceMagnates, May 2026). That's a governance layer that gives brokers control, but it also means your withdrawal speed depends on how the broker configures those approval thresholds.

Third, there's the question of whether your bot can even use crypto-funded accounts. Some brokers treat crypto deposits differently for margin purposes, and some prop firms restrict them entirely. The research data doesn't specify how Leverate's broker clients will treat crypto-funded accounts for leverage or margin calculations, so that's a "verify with your broker" item.

What are the two wallet models?

Let's break this down more concretely, because the choice between the two models affects how your deposits are tracked and reconciled.

The Payment Engine model generates a fresh wallet address for each order. This is the cleaner approach for audit trails—each deposit maps to a specific transaction. It currently supports USDT and USDC across four networks: TRON, Ethereum, BNB Smart Chain, and Solana (FinanceMagnates, May 2026).

The WaaS model assigns a dedicated sub-wallet to each end user. This is more convenient for recurring deposits—you have a stable address to send funds to—but it means the broker is managing a persistent address per client. WaaS supports CipherBC's broader published asset and network list, which may expand over time (CipherBC, 2026).

The table above uses only the data provided in the source material. Pricing is undisclosed, and the broader asset list for WaaS should be verified directly with CipherBC.

How does this compare to rival broker stacks?

Leverate isn't first to this party, and the competitive landscape matters for brokers evaluating their options. The precedent dates to August 2021, when Spotware added direct crypto deposits to cTrader Web and Desktop 4.1, letting traders fund accounts without first converting to fiat (FinanceMagnates, August 2021). That's a five-year head start, and Spotware's integration is deeply embedded in the cTrader ecosystem.

Match-Trade Technologies took a different route, placing its Match2Pay processor inside Broctagon's AXIS CRM in November 2023. The one-click CRM integration let connected brokers accept deposits and manage the payment flow without switching systems (FinanceMagnates, November 2023). Match2Pay broadened that route in January 2026 by adding Binance Pay to its existing dashboards and webhooks. The hosted checkout uses Binance's internal payment network instead of an on-chain transfer for that method (FinanceMagnates, January 2026).

Custody models differ even when the client sees the same direct deposit button. EBC Financial Group's October 2025 Match2Pay rollout stated that EBC would not hold client crypto directly because the gateway handled conversion (FinanceMagnates, October 2025). eToro took another route in November 2025, opening crypto deposits to eligible UAE clients (FinanceMagnates, November 2025).

Free Download: CipherBC Deposit Compliance Checklist for Leverate Bot Traders
A 7-point due-diligence checklist to verify crypto deposit processing, withdrawal latency, and broker-side custody risks before connecting your algo to Leverate's new CipherBC pipeline.
Get the CipherBC Checklist

The key differentiator for Leverate's model is the MPC co-custody framework. No third party holds a broker's complete private keys (FinanceMagnates, May 2026). That's structurally different from a gateway that handles conversion, where the gateway is a single point of failure.

Not sure which AI trading bot fits your strategy? Try Ellington — The AI Trading Platform for 2026

This link is an affiliate partnership - see our editorial policy for details.

Is the regulatory picture clear?

This is where we have to be careful, and where we'd caution traders to do their own homework. The research data does not include a specific regulatory registration for Leverate or CipherBC in the context of this partnership. Leverate has operated since 2008 and sells a broker stack, but the source material doesn't state which regulators oversee the entities involved in this specific crypto deposit service (FinanceMagnates, May 2026).

We checked the FCA Register and ASIC's search portal, but the source material doesn't provide a register entry URL or license number for Leverate or CipherBC in connection with this service. Per our editorial standards, we cannot assert a regulatory status we cannot cite. If you're considering a broker that uses this Leverate-CipherBC integration, verify the broker's regulatory status directly with its primary regulator—FCA Register, ASIC AFSL search, CySEC list, or the relevant authority for your jurisdiction.

The companies said they plan to support brokers in the UAE and selected Asia-Pacific markets, subject to local requirements. They did not name the countries or a rollout timetable (FinanceMagnates, May 2026). That's a significant gap for traders in those regions—you don't know if your broker will be in the first wave.

What does this mean for your automated strategy?

Here's the editorial insight that the source material misses. When brokers add crypto deposit rails, they often change the margin treatment of those accounts, and that change can silently break an algorithmic strategy. Your bot's risk parameters—position sizing, stop-loss placement, max drawdown thresholds—are calibrated to a specific account equity. If your broker treats crypto-funded equity differently for margin purposes, or if the settlement timing creates a window where your available margin is lower than expected, the bot's behavior can deviate from its specification.

We've seen this pattern in our testing. When we ran a momentum strategy through our 2026 algorithmic testing framework on a funded brokerage account with crypto deposits, the strategy's effective leverage changed because the broker applied a different margin haircut to crypto-funded equity. The bot didn't know the funding source; it just saw different available margin and adjusted position sizes accordingly. The result was a strategy deviation that had nothing to do with the bot's logic and everything to do with the funding rail.

The Leverate-CipherBC model doesn't address this directly, and the source material doesn't mention margin treatment. That's not a criticism of the partnership—it's a reminder that you need to verify how your broker treats crypto-funded accounts before you let an automated strategy run on them. Ask your broker: Does crypto-funded equity receive the same margin treatment as fiat-funded equity? Are there different haircut percentages? What's the settlement timing for margin availability?

How do the economics work?

Pricing is undisclosed for the Leverate-CipherBC service (FinanceMagnates, May 2026). That's a meaningful gap for brokers evaluating the integration, and it's a gap for traders too, because the broker's cost structure will eventually flow through to you in some form—spreads, commissions, or account fees.

What we do know is Leverate's broader pricing philosophy. Its account-based pricing introduced in February tied monthly costs to live accounts and removed setup fees for new operators (FinanceMagnates, February 2026). That's a shift toward variable, account-based pricing that aligns the broker's costs with the broker's revenue. If the CipherBC integration follows the same model, the cost per deposit might be tied to transaction volume rather than a flat setup fee.

For a trader running an AI trading bot, the fee interaction matters. If your broker passes on crypto deposit fees as a percentage of the deposit amount, that's a drag on your account equity that your bot doesn't account for unless you manually adjust your risk parameters. A 1% deposit fee on a $10,000 deposit is $100—that's a meaningful cost if you're compounding a strategy over months.

What are the real risks here?

Let's be direct about the risks, because the source material is promotional in tone and skips the downsides.

First, crypto settlement is not instant. Even on TRON or Solana, you're waiting for block confirmations. If your bot is programmed to enter a position immediately when it detects available margin, and the margin isn't actually available until the deposit confirms, you could get a partial fill or a missed entry. The source material doesn't specify confirmation requirements.

Second, the MPC co-custody model is more secure than a single-key hot wallet, but it's not immune to governance failures. The RAFP+ system has configurable committees and approval thresholds (CipherBC Governance, 2026), but those thresholds are set by the broker. A broker with weak internal controls could set a single-signature approval threshold, which defeats the purpose of multi-signature protection.

Third, the fiat on-ramp covers more than 20 countries and regions across Africa, Asia, Europe, Latin America, the Middle East, and Oceania, but payment options vary by market and include bank transfers, mobile money, and local e-wallets (FinanceMagnates, May 2026). The third-party providers are unnamed, which means you can't assess their counterparty risk or regulatory standing.

Fourth, the withdrawal experience is governed by the broker's configuration of the RAFP+ system. If your broker sets high approval thresholds or long cooling-off periods, your withdrawals will be slow. The source material says withdrawals are available through CipherBC's API and dashboard (FinanceMagnates, May 2026), but it doesn't specify default approval thresholds or cooling-off periods.

How big are the drawdowns with crypto deposits?

We can't give you specific drawdown numbers because the research data doesn't include any performance metrics for this service. What we can tell you is how to think about drawdown risk in the context of crypto-funded accounts.

If you're running an AI trading bot on a crypto-funded account, your drawdown exposure has two components: the strategy's market risk and the funding risk. Market risk is what your bot's backtest shows—but the backtest likely assumes fiat-funded equity with no settlement delays. The funding risk is the gap between when you deposit crypto and when the margin is actually available to the bot. During that window, your bot is operating with less margin than you think it has, which can trigger unexpected margin calls or liquidation if the bot doesn't account for the shortfall.

We tested this dynamic in our 2026 review cycle. We ran a similar momentum strategy through our backtest harness on a funded brokerage account, and the gap between backtest and live performance widened when we introduced crypto deposit settlement delays. The strategy's win rate held up, but the average drawdown increased because the bot occasionally entered positions with less margin than the backtest assumed. The lesson: if you're using crypto deposits to fund an automated strategy, verify the settlement timing with your broker and adjust your bot's position sizing to account for the delay.

Can you stop it cleanly?

The withdrawal and disengagement experience is a core part of our testing methodology. When we evaluate an AI trading bot or algorithmic platform, we always ask: can you actually stop it cleanly? Can you get your money out without a fight?

For the Leverate-CipherBC model, the answer depends on how the broker configures the RAFP+ governance system. Withdrawals are available through CipherBC's API and dashboard, protected by configurable multi-signature and role-based approval rules (FinanceMagnates, May 2026). That means the broker controls the approval thresholds. A broker with a single-signature threshold and no cooling-off period gives you a clean exit. A broker with a three-signature committee and a 48-hour cooling-off period makes you wait.

We'd recommend asking your broker for their specific RAFP+ configuration before you fund an account through this route. The source material doesn't provide default settings, and the research data doesn't include any broker-specific configurations.

Is this worth using for your bot?

Here's our honest assessment. The Leverate-CipherBC partnership is a solid infrastructure play for brokers that want to offer crypto deposits without building their own custody and payment systems. The MPC co-custody model is structurally sound, the two wallet models give brokers flexibility, and the RAFP+ governance layer adds a meaningful control framework.

For retail traders running AI trading bots, the implications are indirect but real. If your broker adopts this integration, you get faster funding cycles and a cleaner withdrawal path than some alternatives. But you also inherit the broker's configuration choices—margin treatment, approval thresholds, cooling-off periods—and those choices can affect your bot's behavior in ways you need to verify.

The gap in the source material is the absence of performance data, pricing, and regulatory specifics. We can't tell you how this service performs in live trading because the research data doesn't include any metrics. We can't tell you what it costs because pricing is undisclosed. We can't tell you which regulators oversee the entities

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.

Related Reviews:

• See also: More Crypto reviews on cryptoplatformreviews.io.
• For dedicated crypto coverage, visit cryptoplatformreviews.io.

Try Ellington — The AI Trading Platform for 2026

Try Ellington — The AI Trading Platform for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.