Multiple Betfair Accounts for Trading Bots: What the Rules Allow

If you landed here, you probably have a working bot (or three) and a question about multiple Betfair accounts that sounds simple: can I give each strategy its own account on Betfair or Smarkets?

Short answer: no. And you don't need to.

Both exchanges limit you to one account per person, and no browser configuration changes what the terms say. Which is genuinely annoying if you've already designed your bankroll splits around one account per strategy. That's the plan most people arrive with, and unpicking it is a dull evening's work.

So: what the exchanges allow, why they look so hard for linked accounts, how to run lots of strategies cleanly on the one account you're allowed, what to do if that account gets restricted, and where (if anywhere) an antidetect browser earns a place on your machine.

Multiple Betfair accounts: what the exchanges actually allow

Betfair and Smarkets both operate under UK Gambling Commission licences, and both limit customers to a single account. That's not a quirk of exchanges. It's how almost every licensed gambling operator works, because so much of their regulatory duty is tied to knowing exactly who each customer is.

A few things follow from that:

One account, in your own name, verified with your own documents. UK-licensed operators have had to verify age and identity before letting customers gamble since 2019.
Your account is for you. Operators' terms generally forbid letting other people use your account or using someone else's. Sharing a login with a trading partner counts.
Automation is allowed, through the official route. Betfair runs a developer programme with its own application keys and terms. Smarkets has offered API access too; check its current developer documentation for how access is granted.

I'd love to hand you exact clause numbers. I'm not going to. Terms get revised, blog posts don't, and I'd rather you read the live wording than quote mine back at a customer services agent who has the current version open. Both are linked from each exchange's site footer, buried about where you'd expect.

Why exchanges look so hard for linked accounts

This is the part that surprises people. Exchanges earn commission on winning bets, so they don't lose money when you win. Why would they care how many accounts you run?

Because the reasons have very little to do with who wins.

Identity and money laundering. A licensed operator has to know whose money is moving. An account that's really controlled by someone other than its named holder breaks that chain, whatever the intent behind it.

Safer gambling. Self-exclusion only works if a person can't simply open another account. UK-licensed online operators have to take part in GAMSTOP, the national self-exclusion scheme, and duplicate-account checks are part of how that promise holds up.

Market integrity. Two accounts controlled by one person can match each other's bets, inflate apparent liquidity, or move a thin market. On an exchange (where customers trade against each other, not the house) that's a direct harm to every other trader in the market.

Charges and incentives. Betfair applies an extra charge to some very profitable customers (the Expert Fee, which replaced the older Premium Charge in 2025; check Betfair's charges page for the current rules), and both exchanges run promotions and commission offers tied to an account. Splitting activity across accounts to dodge an account-level charge or claim an offer twice is exactly what the one-account rule exists to stop.

How do they spot it? I'm not going to draw you a map of the detection systems, partly because I'd be guessing — nobody outside those risk teams knows the weightings — and partly because it isn't the point. In broad strokes, operators compare identity documents, payment methods and bank details, contact details, the devices and networks people log in from, and how accounts behave in the market.

Browser signals are one input among many, and usually not the decisive one. That's the detail the whole "just use a different browser" theory quietly skips. But whether an exchange spots a second account isn't really the question: a second account breaks the terms however carefully it's set up.

What breaking the one-account rule actually costs

People tend to price multiple Betfair accounts as a one-way bet: worst case, I lose the spare one. That's not the worst case.

Operators' terms commonly allow them to close every account they believe is connected, void bets, and withhold or claw back winnings while they investigate. Your payment methods and identity can end up excluded, which means you've lost more than a bot slot: you've lost access to the exchange, full stop.

And if the extra account was opened in a friend's or family member's name, you've moved out of terms-of-service territory and into identity misuse, which is a much worse conversation to be having.

Real talk: for a profitable trader, the exchange account is the business. Risking the business to get a tidier P&L breakdown per strategy is, in my opinion, one of the worst trades available to you — and the API hands you that breakdown anyway, for nothing.

Bad odds. Obviously bad odds.

Running several strategies the legitimate way

So you have one account and five strategies, and multiple Betfair accounts are off the table. Here's how to keep them apart without a second login.

1. Use the API, not a browser

Betfair's Exchange API is the supported route for automated trading. You get an application key from the developer programme. There's a delayed-data key for building and testing, and a live key with its own activation process (which, for personal use, has historically come with a one-off fee; check the current figure on the developer site rather than trusting an old number).

For login, Betfair offers a non-interactive "bot" login that authenticates with a self-signed certificate you upload to your account. No browser, no session scraping, no headless login flow to babysit.

If a tutorial tells you to automate the website login page to get a session for your bot, it's doing it the hard way. Scraped sessions break whenever the login page changes, and the certificate route is the one Betfair documents for bots.

2. Tag every order with a strategy reference

This is the feature most hobby bots ignore. The placeOrders call accepts a customerStrategyRef, and each instruction can carry its own customerOrderRef. Give every bot a short, stable strategy tag:

{
  "marketId": "1.234567890",
  "customerStrategyRef": "tennis-a",
  "instructions": [
    {
      "selectionId": 12345678,
      "handicap": 0,
      "side": "BACK",
      "orderType": "LIMIT",
      "limitOrder": { "size": 2.0, "price": 3.5, "persistenceType": "LAPSE" },
      "customerOrderRef": "tennis-a-000184"
    }
  ]
}

Keep the strategy tag short: Betfair's placeOrders documentation limits customerStrategyRef to 15 characters (customerOrderRef to 32), so check the current docs before you choose a naming scheme. Then filter your cleared orders by strategy reference when you report. That gives you per-strategy profit and loss, which is the thing most people actually wanted from "one account per strategy" in the first place.

3. Put risk limits in your own code

A separate account felt like a firewall: if the football bot goes haywire, the tennis bank is safe. You can build that firewall yourself, and it's a better one.

A maximum stake and a maximum open exposure per strategy tag
A daily loss limit per strategy that stops that bot (and only that bot)
A kill switch that cancels every open order carrying one strategy's reference
Separate processes, so one crash doesn't take the others down with it

None of this is glamorous. Writing a kill switch is the dullest evening you'll ever spend on a trading bot, and it's also the only part of the thing you'll be grateful for at two in the morning when a price feed goes strange and one strategy starts doing something creative with your bank.

4. If you're bigger than one person, talk to the exchange

Building software that other people will use? Running money for a business rather than yourself? Those situations have their own arrangements and terms, and the right first step is the exchange's developer or commercial team, not a workaround. Ask them directly. Worst case they say no, and you've lost nothing.

If your account gets restricted or suspended

This happens to legitimate traders too, usually after a verification request, a sudden change in activity, or a payment issue. The route back is boring and it's the only one that works:

Contact customer services and ask what triggered it. You won't always get the full reasoning, but you'll usually learn what they need from you.
Supply what they ask for promptly. Identity documents, proof of address, source-of-funds information. Delays read badly.
Use the formal complaints procedure if you think the decision is wrong. Put it in writing and keep copies.
Escalate to ADR. UK-licensed operators must offer an independent alternative dispute resolution service once their own complaints process has run its course. The operator will tell you which one it uses.

And the one thing not to do: open a new account while the old one is restricted. That turns a reviewable dispute into a clear breach, and it's the fastest way to make a temporary restriction permanent.

Where an antidetect browser fits (and where it doesn't)

Honest answer first. If you're one person with one exchange account and a bot on the API, you don't need JustBrowser for the trading itself. Your bot never opens a browser.

Odd thing to write on our own blog, I know. The alternative is selling you a tool you'd open twice and then resent paying for.

There are still a few jobs around a trading operation where separate, isolated browser profiles are genuinely useful:

Keeping your one login away from everything else. A dedicated profile that's only ever used for your exchange account, with no extensions and no everyday browsing, is a sensible security habit. That's about protecting your account from malware and session theft, not hiding anything from the exchange.

Testing a trading tool or tipster site you're building. If you sell software or publish content for traders, you'll want to see your own pages the way visitors in different countries and on different setups see them. Locale, timezone and screen differences break layouts more often than you'd think. This is plain QA and ad verification.

Agency work on client-owned accounts. If you run social or ad accounts for a trading-education brand, each client's accounts can live in their own profile, with access granted by the client. JustBrowser's team seats are free and can run profiles the owner shares with them, so a junior can work in a client profile without being handed the client's whole setup.

Automation you control. JustBrowser has a local REST API (bound to 127.0.0.1) and CDP access for Playwright, Puppeteer and Selenium. A short QA run that opens a profile visibly and checks how your own landing page renders:

import asyncio
import requests
from playwright.async_api import async_playwright

API = "http://127.0.0.1:36542/api/v1"
TOKEN = "..."  # from the app's API/AI tab
HEADERS = {"Authorization": f"Bearer {TOKEN}"}
PROFILE_ID = "qa-landing-ie"

async def main():
    # The API starts profiles headless unless you ask otherwise
    r = requests.post(f"{API}/profiles/{PROFILE_ID}/start",
                      headers=HEADERS, json={"headless": False})
    cdp_url = r.json()["data"]["cdp_url"]

    async with async_playwright() as p:
        browser = await p.chromium.connect_over_cdp(cdp_url)
        context = browser.contexts[0]  # the profile's own context, never new_context()
        page = context.pages[0] if context.pages else await context.new_page()
        await page.goto("https://your-tipster-site.example/offers")
        await page.screenshot(path="offers-ie.png", full_page=True)
        await browser.close()  # only disconnects

    requests.post(f"{API}/profiles/{PROFILE_ID}/stop", headers=HEADERS)

asyncio.run(main())

For more on wiring profiles into automation, the Playwright and Puppeteer REST API tutorial goes further. If you want to understand what fingerprinting actually measures, start with how WebGL fingerprinting works, then the JA4 TLS fingerprinting explainer. And if you still think incognito mode or a fresh Chrome profile does anything for privacy, the antidetect browser myths post is a quick read.

Two caveats, because they matter here. JustBrowser doesn't include proxies; you bring your own. And please don't use a proxy, VPN or any browser to reach an exchange from a country where it isn't licensed to serve you. Gambling access is set by jurisdiction, and getting around it puts your account and your balance at risk in exactly the way this whole post is warning about.

If you publish trading content and pay for traffic to it, it's also worth watching that traffic's quality with something like ClickzProtect, which is a separate product built for affiliates and traffic operators.

Frequently Asked Questions

Can I have more than one Betfair or Smarkets account?

No. Both exchanges limit you to one account per person, which is standard for UK-licensed gambling operators. A second account in your name, or one opened in someone else's name for you to use, breaks the terms, and operators' terms typically let them close the accounts and void bets. Read the current terms on each exchange's site for the exact wording.

How do I run several betting bots on one Betfair account?

Use the Exchange API with your own application key and the non-interactive (bot) login, which uses a certificate rather than a browser. Tag each order with a strategy reference (the customerStrategyRef field on placeOrders) so you can report profit and loss per strategy, and keep separate stake and exposure limits for each bot in your own code.

Do I need an antidetect browser for Betfair API trading?

Almost certainly not. API bots talk to the exchange directly and never open a browser. A separate, locked-down browser profile for your one exchange login is a reasonable security habit, but using an antidetect browser to hide extra accounts from the exchange is a terms violation, not a trading setup.

What should I do if my exchange account is restricted or suspended?

Contact the exchange's customer services, ask what triggered it, and supply any verification documents they request. If you're unhappy with the outcome, use the operator's complaints procedure; UK-licensed operators must also offer an independent alternative dispute resolution (ADR) service. Don't open a new account to get around the restriction.

Why do exchanges care about linked accounts if they only take commission?

Because their obligations go well beyond who wins. Identity checks, anti-money-laundering rules, safer-gambling tools such as self-exclusion, and market integrity all depend on one person mapping to one account. Linked accounts can also be used to trade against yourself or to sidestep account-level charges.

Try JustBrowser

Native Chromium antidetect browser, not extension-based, with a custom engine that's patched on every upstream Chromium release. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. Local REST API for Playwright, Puppeteer, Selenium. Runs on Windows x64 and macOS (Apple Silicon). $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles, unlimited cloud sync, unlimited team seats.

Get started → · How it differs from Multilogin / GoLogin / AdsPower