Connector 01 · Portal
InvestNext
Push transaction codes and receipt PDFs into the investor portfolio view at close. Embed the verify widget on the subscription confirmation page.
● ProductionWebhook + widget
Investors verify on Fund Base Camp, but sponsors usually run subscription, communication, and reporting through a portal — InvestNext, Juniper Square, Carta, Allocations, a self-built dashboard. Learn more about the full process on our How it works page, or explore how we structure access for issuers on For sponsors overview. The integration surface below covers the connectors we maintain, the engineering primitives any sponsor can build against, and the path to ask for something new. Everything we expose is read-mostly, rate-limited, and documented.
Connectors push verification links and receipt PDFs into the portal's investor view at subscription, and surface the live verify endpoint as an embedded widget. You can also verify transaction records directly on the verification page, and review system safeguards under platform security standards. Status indicates production-readiness; "Beta" connectors have working integrations but limited reference customers.
Push transaction codes and receipt PDFs into the investor portfolio view at close. Embed the verify widget on the subscription confirmation page.
Attach the FBC custody record to each investor's subscription record. Custody URL surfaced on the investor dashboard's documents tab.
For Carta-managed SPVs, surface the verification code in the investor's Carta documents tab and provide a deep-link to /verify with the code prefilled.
Embed the FBC verify widget inside the Allocations-hosted investor view. Receipt PDF available from within the SPV detail page.
FBC custody disclosed on the Sydecar deal page; transaction codes delivered with the subscription confirmation.
European-domiciled SPV platforms. FBC connector surfaces custody records to EU-resident investors with appropriate jurisdictional disclosures.
Vendor connector to feed FBC invoicing into sponsor accounting. Memos include SPV and custody-record references for clean reconciliation.
Same as the QuickBooks connector — sponsor-side invoicing flowed into Xero with custody-record metadata.
Dashboard access via the sponsor's existing identity provider. SAML, OIDC, and SCIM provisioning supported on Tier 02 and above.
Whatever portal or workflow you run, the engineering primitives below cover the integration. Most sponsors at Tier 02 are using the widget + webhook combination; engineers integrating from scratch use the REST API directly. Full technical context is documented in How the system works, and commercial onboarding details are available under Pricing plans.
Three endpoints — ingest, verify, receipt. Ingestion requires authenticated HMAC; verify and receipt are public and rate-limited. JSON in, JSON out, semantically versioned with 12-month deprecation notice.
Drop-in widget that renders the verify endpoint inside a sponsor portal. No iframe, no data leaves the sponsor domain except the verification code. CSP-safe, zero dependencies, branded to the sponsor's style tokens.
Outbound HTTP calls when material state changes in custody — primarily anchor.finalized when a deposit's Bitcoin anchor reaches ≥3 confirmations. Signed with HMAC-SHA256, retried with exponential backoff.
For sponsors running their own admin software, the same verify endpoint can be called server-to-server. No special API; identical to the public endpoint, just with optional User-Agent identification for support routing.
The standard widget integration. The script tag and a target element; everything else is rendered by FBC on your domain. Style tokens override the defaults — match your portal's colors and fonts.
Note
The widget is available at Tier 02 and above. Style tokens supported: data-theme, data-accent, data-font, data-paper, data-ink, data-radius. Email engineering@ for the full token reference.
The connectors above are the ones we maintain in production. New connectors are built when a sponsor asks — usually because they're moving an SPV onto FBC custody and the portal in question is where their investors already log in. If you're ready to proceed, you can reach us via our contact page or review onboarding requirements on sponsor onboarding overview. Lead time is typically two to four weeks for a new connector; sometimes less if the platform has a clean partner API.
Email engineering@→