Platform capabilities

Evaluate the Roots platform scope across customer types, jurisdictions, accounts, money movement, and compliance workflows.

See API availability for current API readiness and the released UAT contract.

Capability matrix

Area	Current scope	Version label	What you confirm before launch
Direct clients	Banks, NBFIs, fintechs, payment companies, and similar financial platforms.	Supported	Your company and product configuration are approved.
End customers	Business and individual.	Supported	Customer eligibility and required onboarding data.
Onboarding jurisdictions	Refer to prohibited jurisdictions to determine whether your jurisdiction is supported.	Supported	Your enabled jurisdictions and applicable restrictions.
Accounts	Roots FBO-backed USD virtual accounts.	Supported	Account issuance, activation, and instruction availability.
Accounts	Own FBO instance.	Beta (invite only)	Account issuance, activation, and instruction availability.
Currency	USD.	Supported	Enabled account and payment currency.
Incoming money movement	International wires, Fedwire, FedNow, and ACH withdrawals.	Supported	Enabled rails, account instructions, sender requirements, and hold behavior.
Outgoing money movement	International wires, Fedwire, FedNow, and ACH withdrawals.	Supported	Rail eligibility, payment approvals, limits, and destination requirements.
Internal movement	Internal transfers.	Supported	Eligible account relationship and status behavior.
Counterparties	Screened external payment destinations.	Supported	Required counterparty data and screening outcome.
Compliance operations	KYB/KYC, associated-person screening, counterparty screening, RFIs, holds, and post-funding review.	Supported	Required workflow, decision authority, and integration states.
USD/USDC trades	Appears in the Beta API surface.	Beta (invite only)	Product availability, pricing, settlement, and production authorization.
Additional rails, jurisdictions, and customer types	Controlled expansion.	Roadmap	Released API contract and program approval.

Evaluate the compliance model

Roots operates first-line platform controls. The partner bank retains final authority for decisions reserved to the bank.

Your platform owns customer-facing collection, internal workflow routing, and safe behavior when Roots returns a hold, restriction, RFI, or non-terminal payment state.

Evaluate the integration model

Start with front-office authentication and API keys. Then model businesses, associated people, accounts, counterparties, payments, and reconciliation around Roots IDs and lifecycle states.

Do not treat endpoint presence, schema enums, or UAT fixtures as confirmation that a product is enabled for production.

Next steps

Read Compliance operating model for decision authority.
Read Jurisdictions, rails, and scope for operational boundaries.
Follow Quickstart to begin an integration.