Using a sub-account for a channel's calls

Why can't you answer the month-end question?

A month after you subscribed, your balance is different from what it was. Some of that came from the channel's calls. Some came from a position you opened yourself on a Tuesday night, some from a spot bag you bought before you had ever heard of the channel, and some from funding payments on a perpetual you have been carrying since spring. The subscription fee, meanwhile, is a precise number. You know it to the cent.

So the only question that matters — was this worth paying for — has an exact cost on one side and a fog on the other. That is not a discipline problem or a spreadsheet problem. It is a container problem. Everything went into one box, and a box cannot be un-mixed after the fact.

The fix is boring and free on most venues: the channel's trades get their own account.

What is a sub-account, mechanically?

Most large exchanges let one verified identity hold several trading accounts underneath it. They are usually called sub-accounts or subaccounts. Each has its own balance, its own positions and its own API keys, while the identity, the verification documents and the login that governs them all stay in one place — the main or master account.

The important part for a follower is how money moves, and this is where venues genuinely differ. A few examples of what the exchanges themselves publish, as of August 2026:

• OKX. Its help centre states that "You can only transfer crypto from your main account into your sub-account," and that "To transfer funds from your sub-account back to your main account, you must do this within the main account." On withdrawals it is blunt: "Sub-accounts can be used for spot, spot leverage, contract trading, and deposits for standard sub-accounts, but activities such as withdrawals and buy/sell crypto are not allowed." The same page puts the count at "a maximum of 5 sub-accounts" for regular users, with VIP tiers allowed twenty to thirty (What is sub-account?, How do I transfer/deposit crypto with my sub-accounts?).
• Binance. Its sub-account FAQ answers the question of whether a sub-account can move assets on its own with "No, only the master account can manage asset transfers. Asset transfer between sub-accounts and third-party accounts is not supported." Binance also requires that you complete identity verification and enable two-factor authentication before using the feature, and states that "Each sub-account can create up to 30 API Keys" (Binance Sub-Account Functions and FAQ).
• Bybit. Its API documentation for transfers notes that "When use sub acct api key, it can only transfer to main account" — a sub-account's own credentials cannot push funds sideways to another sub-account (Bybit V5 API, Create Internal Transfer).
• Kraken. For derivatives subaccounts, its support article says "Withdrawals from sub-accounts are blocked, clients will need to move funds back to the master account in order to withdraw funds out of Kraken Derivatives," while internal movement runs in every direction — master to sub, sub to sub, sub to master. Its developer guide describes the same shape for spot subaccounts: "Use AccountTransfer to move funds between master and sub-accounts in either direction," and adds that "Transfers between accounts are instant and do not incur fees" and that "Each sub-account can have its own API keys with independent permission sets" (Understanding Derivatives subaccounts, Sub-accounts and multi-account management).

Read those four together and the pattern is clear, along with its limits. Every one of these venues lets you hold separate balances under one identity, and every one moves money between them internally rather than on-chain. But how many accounts you get, which direction transfers may be initiated from, and whether the sub-account is a wall or a label are per-venue answers that also change over time. Check your own exchange's help centre rather than assuming any of the above applies to it, and check it again if you set this up a year ago.

What does the separation actually buy you?

A number at the end of the month. One balance goes in on day one. Nothing else touches the account. At the end of the month there is one balance and one difference, and it belongs to exactly one channel. That difference already has the fees inside it, and the funding payments, and the trades where the entry never filled — all the leakage that lives between a published result and your account. Now the subscription fee has something to be compared against. Without the separation you are comparing a precise cost to a guess, and the guess will usually be generous, because you remember the calls that worked.

This is also the version of a track record you can trust, because you produced it. A channel's own numbers are a claim about the channel; a sub-account statement is a fact about you. The two answer different questions, which is why the account balance does not replace keeping your own trade log — the log tells you why the number came out that way, the account tells you what the number is.

A cap on the blast radius. The moment you hand an API key to a bot, a copy-trading tool or a channel's "automation", the question stops being how good the calls are and becomes what that key can reach. A key issued on a sub-account reaches the sub-account: the balance you decided to put there, and nothing else. A key issued on your main account reaches everything you own on that exchange. Venue rules can make this stronger than it sounds — Bybit documents that sub-account credentials can only push funds back toward the main account, which is not a useful direction for someone who should not have them. Do not assume that holds everywhere: what a sub-account key is permitted to move differs by venue and by the permissions you tick when you create it, so read that screen before you issue the key rather than after.

None of that replaces the basics of API keys and account security — no withdrawal permission, an IP allowlist where the venue offers one, and a key you can kill in one click. It stacks with them. Permissions decide what a key may do; the sub-account decides how much it is standing next to.

An exit with no residue. Leaving a channel from a mixed account is an archaeology project: which of these seven open positions were theirs, was the stop on that alt mine or a call from March, do I still have their bot running somewhere. Leaving from a sub-account is three steps. Close what is open, transfer the balance back to the main account, revoke the key. The account can sit empty at zero cost on venues that charge nothing to keep one, and your own portfolio never knew the channel existed.

A limit that holds when you get excited. The size of the box is decided once, at the transfer screen, in a calm moment — not at 3 a.m. when a call looks like the one you cannot miss. That is a different mechanism from position sizing for signal followers, and it works even when the sizing discipline slips, because topping the account up takes a deliberate transfer from a different screen.

What does a sub-account not do?

Be exact about this, because the word "separate" does a lot of quiet work.

It is an organisational boundary inside one exchange, under one identity. The verification documents are the same, the terms of service are the same, and the counterparty is the same. If the venue freezes the identity, restricts your region, suffers an outage during a volatile hour or fails outright, every account under it is affected together. A sub-account is not custody and not diversification; if that distinction matters to you, the question is which venues and which wallets you use at all, which starts back at setting up an exchange account safely.

It is not a wall on every venue either. Kraken's own documentation describes transfers in either direction between master and sub-accounts, so on that shape the separation is bookkeeping plus a withdrawal block, not a hard container. Where a venue lets funds flow freely both ways, the discipline is yours to keep, and it is worth knowing which kind you are on before you rely on it.

And a "managed" sub-account is a different product entirely. Some venues offer an arrangement where a sub-account is entrusted to another party who trades it for you. That is not the setup described here. Here, you keep the keys and place or automate the trades yourself; you have simply put a wall between this channel's activity and the rest of your money.

What is the practical setup order?

1. Read your venue's page first. Sub-account type, how many you get, which directions transfers run, whether creating one is free. Every one of those varies by exchange and changes over time.
2. Create it with a name that says whose it is. Not "sub1". If you follow more than one source, the name is what saves you in month three, when the whole point is that each one is separately answerable.
3. Fund it by internal transfer, once, with an amount decided in advance. Kraken, for one, documents that transfers between accounts are instant and incur no fees; confirm the same on your own venue rather than assuming it, and decide the amount before you fund rather than after.
4. Write down the starting balance and the date. Two lines. This is the baseline that makes the month-end number mean something.
5. Only then issue an API key, and only if something actually needs one. On the sub-account, never on the main account. No withdrawal permission. IP allowlist if the venue supports it.
6. Set an end date for the review. A month, or a fixed number of calls. Deciding when you will look protects you from looking only after a good week.

The two settings people forget

The new account starts on the venue's defaults, not yours. Leverage, margin mode and position mode on a freshly created account are whatever the exchange ships, not the carefully chosen settings on the account you have been trading for a year. Nothing warns you; the first call simply lands on a configuration you did not choose. Check them before the first order, not after.

Where the key lives, and who else has it. A key created for a bot is often pasted into a third-party panel, and the sub-account only limits the damage if the key belongs to the sub-account. Issuing it from the main account "because that is where I was logged in" is the single mistake that undoes the entire arrangement. Check which account is selected in the API screen before you click create, and check again after a browser session where you switched accounts.

None of this makes a bad channel profitable. It makes a channel countable, keeps its automation away from money you never assigned to it, and lets you walk away in three steps. Those are the parts of the outcome you control, and they cost one screen and one transfer.