Jurisdictions, rails, and scope

Confirm the Roots product scope, jurisdictions, customer types, currencies, and payment rails before you design a production workflow.

See API availability for the current API contract and enabled resources.

Current product scope

Roots supports a compliance-first USD account and payment model for institutional clients that serve end customers through the Roots platform.

Capability	Current scope	Integration consideration
Direct clients	Supported: banks, NBFIs, fintechs, payment companies, and similar financial platforms.	Your platform submits data and instructions on behalf of its end customers.
End customers	Supported: business and individual end customers.	Submit business data, associated-person information, and required documents.
Onboarding jurisdictions	Supported: refer to prohibited jurisdictions to determine whether your jurisdiction is supported.	Confirm enabled jurisdictions for your program before collecting or submitting data.
Currency	Supported: USD.	Confirm each enabled account currency and product before creating an account.
Account structure	Beta (invite only): FBO-backed virtual accounts.	Treat account issuance and activation as separate from review completion.
Money movement	Beta (invite only): international wires, Fedwire, FedNow, and ACH deposits and withdrawals, plus internal transfers.	Do not assume another rail is enabled without written confirmation from Roots.
Counterparties	Beta (invite only): external payment destinations subject to screening.	Use only counterparties that Roots reports as active.

flowchart LR
  Client[Financial platform] --> Customer[Business end customer]
  Customer --> Account[USD virtual account]
  Account --> Payments[International wire, Fedwire, FedNow, or ACH deposit or withdrawal]
  Account --> Internal[Internal transfer]
  Client --> Compliance[Onboarding, screening, and RFI workflow]

Product boundaries

Your program configuration determines the products, rails, jurisdictions, and limits that your platform can use. Do not infer availability from an endpoint, schema enum, or documentation example.

Stablecoin and trade capabilities are Beta (invite only). Confirm that the product, custody model, settlement behavior, and production authorization are enabled for your company before building a live workflow.

Versioned expansion

Roadmap capabilities can include additional customer types, payment rails, account structures, and digital-asset products.

Treat any capability outside the current scope table as subject to the released API contract and program approval. A new product, payment rail, account type, or higher-risk corridor can require a new review and bank gate.

Next steps

Read Compliance operating model for bank-gate behavior.
Read Onboard a business end customer to plan business onboarding.
Read Production readiness before enabling a live program.