Markets, account modes and execution
Sections ↑Bitget combines a centralised crypto exchange with margin, perpetual contracts and copy trading. Its September 2026 corporate release reported more than 125 million users, a cumulative company figure whose definition should not be confused with monthly active exchange traders. The same release describes a wider product ecosystem including tokenised assets. This profile concentrates on the exchange account: the separate Bitget Wallet and any specialised securities or CFD route have different asset handling and terms.[20]
The main exchange service routes
| Route | What it does | Account consequence |
|---|---|---|
| Spot | Orders exchange supported crypto assets on an order book. | The traded asset balance is distinct from exposure through a futures contract.Source 2 |
| Unified Trading Account | Combines eligible spot, margin and futures functionality. | Mode selection determines eligible collateral and whether positions share margin.Source 4 |
| Futures copy trading | Replicates an elite trader through a dedicated allocation. | Execution and profit sharing follow copy-service rules, not simply the leader’s displayed return.Source 7 |
| API access | Programmatic account and trading instructions. | A permitted action can be executed without a fresh manual confirmation for each order.Source 8 |
In a unified account, assets can receive a collateral haircut before they contribute to margin. A displayed wallet valuation is therefore not the same amount as spending power, withdrawable value or risk capacity. The calculation also accounts for liabilities and existing positions. Cross margin links supported exposures through shared equity; isolated margin assigns a separate risk unit to a position. Neither setting removes execution risk when a liquidation or closing order reaches the market.[5]
Account controls that change behaviour
| Control | Published operation | Practical distinction |
|---|---|---|
| Mode conversion | Open orders, unsupported positions or outstanding liabilities can block a switch. | Changing a screen preference does not automatically migrate live obligations.Source 6 |
| Classic-to-UTA migration | Trading, transfers and withdrawals are temporarily frozen during the upgrade; deposits are not. | The original spot account becomes the funding account and the other eligible accounts merge.Source 4 |
| Copy-trading exit | The detailed exit flow offers immediate market closure or following the trader’s remaining closing actions. | The latter stops new copies while leaving existing positions exposed until closure.Source 7 |
| API keys | The documentation permits ten keys per UID, with configured read or write permissions; withdrawals require an IP whitelist. | A reporting integration should be distinguished from a key able to trade or move assets.Source 8 |
The copy-trading guide describes a high-water-mark profit-sharing model and a default 0.5% slippage limit, which the follower may adjust. An order can fail the slippage or balance checks, so two followers need not hold identical positions. The guide’s detailed exit options qualify its simplified statement that stopping copying closes positions: the option selected in the confirmation determines whether closure is immediate.[7]
Trading fees, borrowing and incentives
Sections ↑The August 2026 FAQ supplies standard rates before VIP and token benefits. The live page did not expose a complete numeric tier grid, so an older VIP ladder is not substituted. Account, product and promotional conditions can change the applicable tariff.[2][3]
Published baseline transaction charges
| Product and basis | Maker | Taker |
|---|---|---|
| Standard spot; percentage of executed value | 0.10% | 0.10%Source 2 |
| Standard futures; percentage of position value executed | 0.02% | 0.06%Source 2 |
| Eligible BGB payment of spot fees | Published schedule displays a 20% deduction | Requires the fee-payment setting and sufficient BGBSource 3 |
Worked example: a 2,000 USDT spot purchase at 0.10% costs 2 USDT in exchange fees. Selling the same notional at the same fee rate adds another 2 USDT, making 4 USDT before bid–ask spread, price movement and any withdrawal. A 10,000 USDT futures opening executed as a taker at 0.06% costs 6 USDT; an equal-notional taker close adds 6 USDT. The 12 USDT total is calculated on exposure, not on the margin deposited, and excludes funding and liquidation-related charges.[2]
Costs beyond the headline fee
| Cost or adjustment | How it arises | What determines the amount |
|---|---|---|
| Perpetual funding | Payments pass between long and short positions at the settlement event. | Position value multiplied by the applicable rate; the API exposes one-, two-, four- and eight-hour intervals.Source 30 |
| Interval changes | A dated notice moved ONEUSDT from one-hour to four-hour settlement on 22 September 2026. | The actual contract schedule overrides a general explanation that says all funding is every eight hours.Source 27 |
| Borrowing | Margin liabilities require interest treatment separate from transaction fees. | The relevant asset, account mode and current borrowing schedule govern the charge.Source 5 |
| Futures bonus | Bonus principal is neither transferable nor withdrawable. | Transfers, withdrawals and expiry can invalidate unused credit and change available collateral.Source 25 |
VIP qualification is not simply a larger account receiving a permanent rate. The published notes use rolling volume and asset measurements, aggregate specified main and sub-account activity and select the highest qualifying level. The fee currency also matters: paying with BGB consumes a separate token balance. The new UTA FAQ describes a 20% deduction for both spot and futures, while the more general fee FAQ discusses the spot discount. This account-version difference should be resolved against the actual account tariff; a universal futures deduction is not assumed here.[3][4]
Fiat payments, crypto transfers and withdrawal holds
Sections ↑The terms describe third-party fiat conversion. Bank-route eligibility and bank-account checks can be narrower than exchange registration.[1][10]
Selected published fiat routes
| Eligible route | Published charge | Operational qualification |
|---|---|---|
| Individual EUR via SEPA | Deposit: EUR 0; withdrawal: EUR 1. | Create the deposit order before sending; the transferred amount and account name must match.Source 9 |
| USD via SWIFT | Deposit: USD 0; withdrawal: USD 30. | Provider availability and bank deductions remain separate from the stated platform tariff.Source 9 |
| BRL via Pix | Deposit: BRL 0; withdrawal: BRL 2.60. | The published route includes Pix/bank withdrawal; identity and currency-specific conditions apply.Source 9 |
| EUR rejected-payment refund | Individual refund fee: EUR 0.20–2; institutional: EUR 2. | No refund is issued if the original amount is smaller than the refund processing fee.Source 11 |
The EUR instructions reject joint-account funding and warn against using SWIFT for the SEPA route. The support page’s general SEPA processing estimate is one to three working days; that is not a guaranteed withdrawal time or a promise that every transfer uses SEPA Instant. Its institutional rows and personal-only explanatory text do not establish one consistent institutional offer, so the individual EUR tariff above should not be carried across to corporate funding.[9][11]
Why an available balance may not be withdrawable
| Situation | Published treatment | Relevant next record |
|---|---|---|
| Recent security change | Password, 2FA or specified security changes can impose a 24-hour hold. | Security-change time and the withdrawal restriction notice.Source 12 |
| New device | Payment and withdrawal functions can be unavailable on that device for one hour. | Device login record; this differs from a platform-wide halt.Source 12 |
| Address controls | Withdrawal whitelisting restricts destinations; optional withdrawal cancellation provides a short buffer. | The saved address, network and enabled confirmation settings.Source 13 |
| Network or compliance review | A transfer may be affected by maintenance, risk review or insufficient required confirmations. | The transaction ID and network status, not only the trading balance.Source 12 |
Bitget’s account security guide also records login time, location, IP address and device information, with a stated three-month activity-history window. These records can help separate an unauthorised login from an asset-network delay. A withdrawal whitelist and cross-device verification protect different steps: the former limits the destination set, while the latter adds confirmation of the action. Neither turns a wrong network selection into a recoverable transfer.[29][13]
Custody, September 2026 incident and reserve evidence
Sections ↑The material recent custody event is the 24 September 2026 wallet incident. Bitget’s later incident account gives approximately USD 388 million as the final verified affected amount and identifies 12 hot or warm wallet addresses. It says cold wallets were unaffected and user account balances remained intact. Those statements are the operator’s account of the incident, not an independent conclusion reached by FXBrokers.[14]
Incident and restoration chronology
| Date, UTC where specified | Published event | Scope of the evidence |
|---|---|---|
| 24–25 September 2026 | Unauthorised transfers triggered an emergency response and withdrawal suspension. | Original exchange security notice; distinguish the initial loss estimate from the later final accounting.Source 15 |
| 30 September 2026 | The exchange announced Mandiant and SlowMist investigation reports. | Bitget’s summary says third-party security-product compromise enabled access; this profile does not claim to have re-performed either forensic investigation.Source 17 |
| 30 September 2026 | Protection Fund replenished above USD 300 million. | Replenished fund value and the incident loss are different measures.Source 18 |
| 2 October 2026 | The staged restoration completed for remaining tokens, fiat and C2C. | An exchange completion announcement; subsequent asset-specific maintenance can still occur.Source 16 |
The distinction between ledger balances and immediate withdrawal availability matters here. An account may show the full entitlement while a security hold prevents transfer. Conversely, restoring withdrawals does not itself prove that every control weakness has been permanently eliminated. The company says tracing and recovery continued after containment. The specific operational interruption belongs beside its protection claims rather than being reduced to a generic statement that assets are held in cold storage.[14][16]
Reserve disclosure versus protection mechanisms
| Mechanism | Dated published evidence | What it does not establish |
|---|---|---|
| Proof of Reserves, issue 47 | Snapshot on 29 September 2026: total reserve ratio 131%, covering 19 assets. | A ratio over selected covered balances is not a full audit of every liability or a guarantee of access at all times.Source 19 |
| Protection Fund | The October explanation reports replenishment above USD 300 million after the incident. | This is an operator-funded mechanism, not a demonstrated statutory per-customer compensation entitlement.Source 18 |
| User security settings | 2FA, withdrawal address controls and login/activity records. | These limit particular account risks; they do not remove exchange-level operational or counterparty exposure.Source 29 |
Client eligibility and regional restrictions
Sections ↑The current terms require adults and identity checks and exclude the US, Canada, France, Germany, Austria, Hong Kong, Japan, Singapore, Malaysia, Russia and specified Ukrainian territories, among others. Corporate US connections also require assessment.[1]
Product eligibility is another layer. Bank providers can require a particular identity document; a unified-account upgrade can be unavailable for a region or account subtype; copy and institutional services have additional conditions. The current restricted-country wording is consequently more useful than an undated claim of worldwide availability. France remains excluded in these terms even though the AMF’s older warning page now records removal of the website from its blacklist on 9 July 2026. Removal of a warning is not itself a positive service authorisation.[10][6][23]
Support, complaints and account records
Sections ↑Official service and evidence routes
| Need | Published route | What to retain |
|---|---|---|
| Routine account or product help | Bitget support centre, multilingual support and ticket route. | Account UID and relevant order, transfer or transaction identifier.Source 28 |
| Withdrawal interruption | Support centre announcements plus the specific account restriction notice. | Asset/network, requested time and any security-setting changes.Source 12 |
| Trading records | Website export of transaction history and order history. | CSV/Excel asset movements; PDF/CSV/Excel order records where supported.Source 26 |
| Asset or ownership statement | Website account statement export in PDF. | An asset statement is a dated snapshot; ownership reports contain personal identification data.Source 26 |
Website exports allow up to two years per history request; download links expire after seven days. Transaction and order files capture different evidence. The terms require a written claim and a 30-day resolution period before the specified Hong Kong arbitration route.[26][1]
Authorisations, registrations and unresolved scope
Sections ↑Regulatory evidence needs separate interpretation
| Jurisdiction or route | Evidence inspected | Scope retained |
|---|---|---|
| European Union | Bitget’s October compliance guide refers to an Austrian MiCA application announced in July 2026. | An application is not treated here as an authorisation; no current positive CASP entry was independently established.Source 22 |
| France | AMF notice records blacklist removal on 9 July 2026. | This corrects the historical blacklist status; it does not establish permission for every Bitget product.Source 23 |
| Japan | FSA unregistered-operator list contains Bitget Limited and a November 2024 warning. | The warning concerns service to Japanese residents; it is distinct from the operator name in today’s global terms.Source 24 |
| Other claimed arrangements | Company roadmap lists local licences, AML registrations and a UK financial-promotion arrangement. | These categories are not interchangeable; they have not been converted into independently verified permission rows.Source 21 |
The company’s UK wording concerns cooperation with an authorised person for financial promotions. That description should not be republished as a universal FCA approval of the exchange or of client-asset protection. Similarly, an AML registration and a derivatives licence address different activities. A proper account-specific regulatory conclusion requires the legal counterparty, product and current official entry to align; the inspected marketing roadmap does not establish that alignment for every user.[21]
Operator and commercial scope
Sections ↑The agreement names BTG Technology Holdings Limited, but its incorporation jurisdiction was not established. A group press-release dateline cannot resolve that legal-entity question. Cumulative users likewise do not establish active traders or execution depth.[1][20]
- Operator
- BTG Technology Holdings Limited; affiliates and third-party fiat providers are separately scoped
- Exchange model
- Centralised
- Service scope
- Centralised spot, margin and perpetual trading with classic/unified account modes and copy trading. The separate Bitget Wallet and specialised product routes are not treated as the same custody service.
- Client types
- Retail clients; Institutional clients
- Pricing publication
- Public and quoted pricing
- Pricing scope
- Published standard trading fees and provider-specific fiat fees; account, tier and product conditions vary.
- Funding scope
- Crypto deposits/withdrawals and eligible third-party fiat routes including SEPA, SWIFT and Pix; currency, identity and country restrictions apply.
- Custody and asset handling
- Exchange-held assets. September 2026 wallet incident and October restoration are documented in the body. Company PoR and Protection Fund disclosures have different scopes; neither is treated as a statutory compensation guarantee.
- Client eligibility
- Global terms contain substantial territorial exclusions. Product and payment providers impose further checks; the selected countries are set out in the body.
- Support
- Official support centre and ticket/contact service; announcements cover maintenance and network availability.
- Authorisation and registration scope
- Company claims and current warnings/removal notices are distinguished. No positive current official permission entry is asserted for the global operator; company-reported Austrian application remains an application.
Exchange metadata checked 20 Oct 2026Source 1Source 2Source 4Source 9Source 14Source 19Source 21Source 28
Covered contracting entities
BTG Technology Holdings Limited
- Jurisdiction
- Not established from inspected global terms
- Covered services
- Named global platform operator; some services are supplied by affiliates or third parties.
- Client and location scope
- Subject to the global terms and additional product restrictions.
Sources & further reading
- Terms of Use, updated 20 October 2026 Bitget · Accessed 20 Oct 2026
- Trading Fees FAQ Bitget · Accessed 20 Oct 2026
- Public fee schedule and VIP calculation notes Bitget · Accessed 20 Oct 2026
- Unified Trading Account FAQ Bitget · Accessed 20 Oct 2026
- Collateral ratios and margin calculations Bitget · Accessed 20 Oct 2026
- Switching account modes in UTA Bitget · Accessed 20 Oct 2026
- New Futures Copy Trading: Copiers Guide Bitget · Accessed 20 Oct 2026
- Unified Trading Account REST API documentation Bitget · Accessed 20 Oct 2026
- Bank deposit and withdrawal fees and processing Bitget · Accessed 20 Oct 2026
- Bank deposit supported countries and regions Bitget · Accessed 20 Oct 2026
- Linking a EUR bank account Bitget · Accessed 20 Oct 2026
- Withdrawal restrictions and suspensions Bitget · Accessed 20 Oct 2026
- Withdrawal settings Bitget · Accessed 20 Oct 2026
- Security incident: chronology and final accounting Bitget · Accessed 20 Oct 2026
- Security notice: 24 September 2026 wallet incident Bitget · Accessed 20 Oct 2026
- Completion of phased withdrawal restoration Bitget · Accessed 20 Oct 2026
- Mandiant and SlowMist investigation update Bitget · Accessed 20 Oct 2026
- Protection Fund replenished above USD 300 million Bitget · Accessed 20 Oct 2026
- Proof of Reserves issue 47 Bitget · Accessed 20 Oct 2026
- September reserve release and reported user scale Bitget · Accessed 20 Oct 2026
- Regulatory compliance roadmap Bitget · Accessed 20 Oct 2026
- 2026 licensing guide and Austrian application status Bitget · Accessed 20 Oct 2026
- Public notice with July 2026 blacklist removal update Autorité des marchés financiers · Accessed 20 Oct 2026
- List of unregistered crypto exchange business operators Japan Financial Services Agency · Accessed 20 Oct 2026
- Futures trading bonus rules Bitget · Accessed 20 Oct 2026
- Exporting account data and statements Bitget · Accessed 20 Oct 2026
- ONEUSDT funding interval change Bitget · Accessed 20 Oct 2026
- Support and announcements centre Bitget · Accessed 20 Oct 2026
- Advanced account security settings Bitget · Accessed 20 Oct 2026
- Current funding-rate API fields Bitget · Accessed 20 Oct 2026
This profile reports dated public information, including exchange-published services and terms. It does not independently test or guarantee trading, custody, pricing or withdrawals. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.