Getting started with Portfolio Account and Capital Connect

Getting started with Binance Portfolio Accounts and Capital Connect is gated. The public product pages, the Capital Connect FAQ, and the vendor's April and September 2026 press describe an exchange-native omnibus account layer and a marketplace that sits on it. Availability depends on verification, financial thresholds, jurisdiction, and — for trading teams — licensing. The public Fund Account developer surface publishes a real read walkthrough — introduction, change log, and a catalog of signed GET routes — and leaves create, subscribe, redeem, marketplace-write, statements, and sandbox Not stated. This primer compresses those public sources into the decisions a desk has to make before it treats either product as an allocation rail — including a getting-started API order an engineering lead can plan from the public docs alone, and an explicit list of what those docs do not publish. The products belong to a third party. Primer Desk does not operate them, does not onboard anyone onto them, does not make introductions, and does not speak for the publisher of the docs.

Who this is for#

Family offices, bank and broker product leads, and crypto-native managers asked whether Portfolio Accounts or Capital Connect belongs inside an existing allocation or control framework — and whether any of that rail can be driven from an API the way CAAS can. The job is the meeting memo: which product is in the pitch, who can use it, where assets sit, which terms are portfolio-specific, and which Fund Account calls are public. Capital introduction in the introducing-broker sense is out of scope for this page. The white-label API screen with a full get-started order is Getting started with Binance CaaS.

What this is not#

This is not official Binance documentation. Primer Desk is not affiliated with, partnered with, or employed by Binance. It is not a ranking of trading teams, a recommendation to allocate, or an introduction service. A citation of the public FAQ, the product pages, or the Fund Account catalog is not access.

It is also not Portfolio Margin (or Portfolio Margin Pro). Those are derivatives unified-margin products with their own developer endpoints under /sapi/v1/portfolio/ and related paths. Confusing them with Portfolio Accounts / Fund Account — the fund / omnibus infrastructure under Capital Connect — is a scope error, not a synonym. Different product family. Different docs tree.

It is not capital introduction in the introducing-broker sense. Capital Connect is a venue marketplace plus account infrastructure. Do not collapse the two.

It is not a CaaS-style broker integration guide. The public Fund Account surface does not publish master-key versus sub-key matrices, KYC SaaS call order, markup groups, or transfer idempotency. Inventing that matrix here would be a claim this desk will not make.

Two products on one rail#

Public vendor language treats these as a pair.

Portfolio Accounts (also presented on the Fund Accounts product page) are the institutional omnibus account infrastructure. Trading teams pool and manage investor capital in one or more accounts by strategy. The April 2026 press describes allocation and redemption processes on that layer, and states that assets remain held on Binance and cannot be withdrawn by the trading teams. The developer docs brand the same infrastructure as Fund Account.

Capital Connect is the marketplace for discovering and allocating to professional trading strategies. Trading teams onboard to Portfolio Accounts, run strategies, establish a track record, then become discoverable. Eligible investors browse standardized portfolio information and express interest. The September 2026 press repeats that stack: Portfolio Accounts underneath, Capital Connect on top, with technology, custody, NAV computation, compliance gating, and standardized transparency provided by the venue.

A sentence that only says "we will use Capital Connect" is incomplete until someone can say whether the desk is the investor seat, the trading-team seat, or both — and whether Portfolio Accounts infrastructure is already live for that seat.

Eligibility is a gate, not a marketing line#

The FAQ and the press agree on the financial thresholds in substance: VIP Level 3 or above, about $1 million equivalent in total assets on Binance, or approved external-asset proof of about $1 million. They do not always agree on who may pass those thresholds.

• The FAQ (public page updated into April 2026 in the published metadata) has described Capital Connect as restricted to KYB-verified entities and has said individual users were not eligible, with the registered country also required to appear on the Capital Connect Permitted Jurisdictions list.
• The 16 September 2026 press announces expansion to eligible KYC-verified individual users at VIP Level 3+, while keeping the same financial qualification thresholds and zero investor-side platform fees.

Do not reconcile that conflict from a slide. Archive the live FAQ and the Permitted Jurisdictions list on the day of the meeting, and get the seat's path (KYC individual vs KYB entity) in a written vendor reply.

Trading-team gates are separate. Public FAQ and April press language require KYB and a valid licence or recognised exemption for investment, portfolio, or asset management activity for open listing. The FAQ states a portfolio needs a minimum of 30 active trading days before an open-offering application, and that trading teams cannot self-report or edit historical performance or NAV. Verified teams may have read-only marketplace access without going open; the 30-day rule applies to open listing eligibility.

Access path in the FAQ: log in, then More → VIP & Institutional → Capital Connect. Contact is through the dedicated account manager or the channels named on the product pages. Primer Desk is not that channel.

Assets stay on-venue#

This is the control that makes the product a custody question as much as a discovery question.

The FAQ states that assets within a Portfolio Account can only be transferred between the portfolio account and its assigned trading sub-accounts. Transfers to any external account are not permitted. Trading teams cannot withdraw assets. The April and September press repeat that assets remain held on Binance and that investment decisions and arrangements remain between the participants.

Treat that as the public claim to confirm in writing — not as insurance language, not as a bankruptcy opinion, and not as a substitute for a full custody and insolvency scorecard. That scorecard is not published on this desk.

What discovery actually shows#

The April 2026 press lists the compare fields eligible investors can filter on:

Initial connection is anonymous on both sides per the April press. If a trading team accepts a connection request, the investor receives the trading team's information while the investor remains anonymous. The FAQ states portfolio names are not visible on the marketplace until after the investor has engaged in the process the FAQ describes — confirm the live disclosure rule before assuming a brand is public.

The venue's own disclaimer (repeated in press) is blunt: Capital Connect is a connection and facilitation service on an "as is" / "as available" basis; it may be unavailable in a region; the venue is not responsible for completeness or accuracy of trading-team information; nothing on the service is advice, a personal recommendation, or an offer.

Fees, lock-up, and settlement#

Platform fees. The FAQ and the September 2026 press state that Capital Connect is free for investors. The FAQ describes an initial launch period with zero commission for all users, then a one-off commission on capital raised charged to trading teams (the FAQ names 1 percent), with no ongoing platform, management, or profit-sharing fee charged by the venue under that description. Get the live schedule in writing. Do not treat a historical percentage as the fee you will pay or charge.

Portfolio fees and liquidity. Management fees, performance fees, lock-up, and settlement window are set per portfolio and disclosed on the portfolio's Key Fact Sheet before subscription. The FAQ says that during the lock-up defined by the trading team, investors cannot submit redemption requests; after lock-up expires, redemptions follow that portfolio's settlement window. There is no single desk-wide lock-up number on this primer, and inventing one would be a claim this desk will not make.

Subscription finality. The FAQ states that once a subscription request has been submitted, it cannot be cancelled or revoked. Review the Key Fact Sheet and do independent diligence before sending the request.

Getting started with the Fund Account API#

This is the public getting-started order for the Fund Account developer surface — the API brand for Portfolio Accounts under Capital Connect. It is denser than a brochure and thinner than CAAS: every step below is either named on the Fund Account introduction / change log / REST catalog, or attributed to the shared Binance /sapi/ general-info pages with Not stated where Fund Account itself is silent. Soft HOLD on inventing writes, marketplace calls, or a sandbox.

Public Fund Account pages do not publish a dedicated getting-started or integration-guide document comparable to CAAS. The walkthrough here is inferred from those three Fund Account pages plus common SAPI. If a pitch deck shows create / subscribe / redeem / Express Interest as "API," ask for the public path or a written partner-only scope. Do not fill the gap from a slide.

What the public docs actually are#

That is the whole public product-doc tree for this family as of the research pass behind this page, plus the shared /sapi/ basics every other Binance SAPI product points at. It is not an empty shelf — and it is not CAAS.

Prerequisites before any API work#

1. Product eligibility for the seat (VIP / assets / KYC or KYB / jurisdiction) — see Eligibility above. API access does not replace those gates.
2. Portfolio Accounts / Fund Account enabled for the trading team or investor seat through the vendor's institutional path. The Fund Account introduction does not publish a self-serve enablement call.
3. A Binance API key with whatever permissions the vendor requires for these /sapi/ routes. The Fund Account pages do not publish a Fund Account-specific key type, a master-versus-sub split, or an IP-allowlist onboarding checklist. Confirm key scope and IP restriction with the account manager before engineering designs against production.
4. Clarity on seat: trading-team (IM) queries versus the single investor-facing NAV query. Mixing them is a product error, not a retry.

Credentials, hosts, and signing#

Stated on Fund Account catalog paths: the routes live under /sapi/ prefixes — /sapi/v1/vip/fund-info/…, /sapi/v1/capital-connect/…, /sapi/v2/portfolio-account/…, /sapi/v2/capital-connect/…, /sapi/v1/portfolio-account/investor/….

Stated on common SAPI general info (ordinary Binance /sapi/ pattern — confirm for this seat; Not stated as a Fund Account-only reprint):

Not stated on Fund Account product pages: a Fund Account-only base-host list, a per-route security type (USER_DATA / TRADE / …), a Fund Account-specific signing page, weight values for these GETs, or a Fund Account sandbox / QA host. Do not invent one. Do not copy CAAS broker key matrices into this product.

Documented writes#

None on the public catalog. Every Fund Account REST route named for this primer is GET. There is no public POST / PUT / DELETE for create-portfolio, enable-account, subscribe, redeem, statement download, or Capital Connect Express Interest / connection accept. History and redemption-calendar queries exist; submission does not. If engineering needs a write path, the public answer is Not stated — get a written vendor scope.

First calls — public catalog only#

Prefer v2 for new trading-team work. The 28 August 2026 change log calls the v2 Portfolio Account endpoints breaking replacements for the v1 fund-info endpoints; v1 remains callable and will be decommissioned in a future release.

Trading-team / investment-manager side

Persist the portfolio and investor identifiers the vendor's UI or onboarding already uses — the public catalog summaries do not publish a create-id call or OpenAPI parameter tables.

Investor side

Suggested call order (reads only)#

Trading-team seat, once the product is live and a key is issued:

1. Confirm product enablement and key permissions with the account manager (written). Confirm IP restriction and that the key can reach these /sapi/ routes.
2. GET /sapi/v2/portfolio-account/trading-team/portfolio-basic-info — discover which portfolios the key can see.
3. GET /sapi/v2/portfolio-account/trading-team/portfolio-nav-info — last-30-day NAV for a named portfolio (single-object shape).
4. GET /sapi/v2/portfolio-account/trading-team/investor-portfolio-his-info — completed subscription / redemption history for a named investor in that portfolio.
5. GET /sapi/v2/capital-connect/trading-team/redemption/calendar — upcoming redemption forecast across the team's portfolios.

Investor seat:

1. Confirm the seat can call the investor NAV path at all (product gate + key scope — Not stated as a self-serve toggle on Fund Account pages).
2. GET /sapi/v1/portfolio-account/investor/portfolio-nav-info — date and NAV per allocation only.

There is no public step that says "create sub-account," "run KYC," "subscribe," or "redeem" via API. Those product actions, where they exist for a seat, are outside this published catalog.

Errors and limits#

Stated on common SAPI (confirm for this seat):

Not stated on Fund Account introduction or change log: product-specific error codes for these portfolio / capital-connect routes, per-route weights, or Fund Account-only retry rules. The common SAPI error-code page does not name Fund Account either. A blank answer here is a meeting item, not a phase-two ticket.

What is not published (do not fabricate)#

Hold these as explicit gaps. Soft announce stays HOLD — this walkthrough is for the public read surface, not a CAAS-depth broker rail.

• No public create-portfolio, create-investor, or enable-Fund-Account endpoint.
• No public subscribe or redeem write endpoint (history and redemption calendar queries exist; submission does not on the public catalog).
• No public statement / reporting download API named on the Fund Account pages.
• No public Capital Connect marketplace API for browse, filter, Express Interest, or connection accept/reject.
• No public sandbox or QA base URL for Fund Account / Capital Connect.
• No public master-key versus trading-sub-account key matrix for this product (unlike CAAS).
• No public OpenAPI parameter tables or response examples on the Fund Account product pages reviewed for this primer — only catalog path summaries and change-log notes.
• Partner-only docs, if any, are out of scope for Primer Desk until they are public.

If engineering needs those write or marketplace paths, the answer from public docs is: Not stated. Get a written vendor scope. Do not copy CAAS broker endpoints into this product.

The buyer screen#

A blank line is a reason to stop. It is not a phase-two item.

Seat#

• Portfolio Accounts infrastructure, Capital Connect marketplace, or both — named.
• Investor seat, trading-team seat, or both.
• Explicitly not Portfolio Margin and not capital introduction.

Eligibility and jurisdiction#

• VIP Level 3+, on-venue asset threshold, or external-asset proof — which limb applies.
• KYC individual vs KYB entity, reconciled to the live FAQ after the September 2026 expansion.
• Registered country on the Permitted Jurisdictions list.
• Whether this seat can clear gated onboarding at all.

Trading-team gate (if that is the seat)#

• KYB complete.
• Licence or recognised exemption for open listing.
• Thirty active trading days (or the live FAQ's current number) before open offering.
• Whether the listing is open, private, or Express Interest / view-only.

Custody and transfers#

• On-venue holding confirmed in writing.
• Transfer path limited to portfolio ↔ assigned trading sub-accounts.
• Trading team has no external withdrawal path.
• Insolvency and segregation treated as open custody questions — not answered by the marketplace FAQ alone.

Key Fact Sheet and commercial terms#

• Strategy, performance, risk, minimums, currency, fees, lock-up, settlement window archived.
• Investor platform fee confirmed free; any trading-team platform commission confirmed.
• Subscription treated as irrevocable once submitted.
• Venue role limited to infrastructure and facilitation — no suitability guarantee.

API (Fund Account walkthrough)#

• Which public GET routes this seat can call — trading-team v2 versus investor NAV.
• v1 fund-info paths marked legacy; migration plan if anything still calls them.
• Common /sapi/ host + signing + recvWindow confirmed for this seat; Fund Account-specific security type and weights still Not stated.
• Key permissions and IP restriction confirmed with the account manager (not inferred from CAAS).
• Explicit acknowledgment that create / subscribe / redeem / marketplace / sandbox paths are Not stated on the public catalog.
• No fabricated broker matrix. Partner-only claims only with a written vendor reply.

If those blocks are not answerable from the public docs plus a written vendor reply, there is no integration plan. There is a demo.