Embedded finance & platforms
With Forest, run customer onboarding, payments, and compliance reporting on your BaaS rails. Multi-tenant access for your client merchants.
Forest hosts the workflows you need to operate an embedded finance program: customer-facing ops, partner reporting, and multi-tenant access.
Customer onboarding through your BaaS
KYC and KYB run through your BaaS partner's accepted providers as workflow steps. Risk routing per customer tier; agentic triage on routine cases.
Payment ops on your rails
Refunds, holds, reversals, and payout actions live on the customer record. Forest calls Stripe Connect, Modulr, or your BaaS partner's PSP at the configured step.
Multi-tenant for platforms
If you run a platform with sub-merchants or end customers, each tenant works inside scoped permissions. Consolidated audit across tenants.
Compliance refresh and re-screening
Periodic KYC, PEP, and adverse-media re-screening run on schedule. Decisions live on the customer record alongside the original onboarding.
Partner reporting
Reports for your BaaS partner, your card processor, or your regulator package on schedule. Forest assembles, your team reviews and submits.
Customer support and dispute handling
Support tickets, dispute intake, and refund requests live on the customer record. AI agents draft routine responses; your team handles judgement calls.

Built for embedded operations
A complete view per customer
Customer, accounts, transactions, KYC, and prior cases live on the same record. Your team and tenants work from one view, with scope enforced.
Governance for teams, AI agents, and tenants
Permissions and approvals apply to your team, your AI agents, and your client tenants the same way. Every action lands in one audit trail.
Plug into your BaaS stack
Modulr, Solaris, Treezor, and your BaaS partner's accepted providers fully connected, ready to tap from your workflows. Add a connection as a config change.
Plug into your BaaS stack
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
Do I need a banking licence to use Forest for embedded finance?
No. The licence sits with your BaaS partner. Forest hosts the operational layer of your embedded finance program; your BaaS partner remains the regulated entity.
How does Forest connect to my BaaS partner and my rails?
Forest reaches your stack through datasources (for customer, account, and transaction data) and through MCP connectors (for calling your BaaS partner's PSP, your KYC provider, and your other tools inside workflows).
Can my client tenants operate inside the same Forest?
Yes. If you run a platform with sub-merchants or end customers, each tenant has scoped permissions inside your Forest workspace. They see only their own data; you see consolidated audit across all of them.
Which BaaS providers does Forest work with?
Forest is BaaS-agnostic. Common connections include Swan, Solaris, Treezor, Modulr, Synapse, Bond, Stripe Connect, Marqeta, and Highnote. Other BaaS partners connect through the same pattern.
How do you ensure customer data never leaves our environment?
The Forest backend runs inside your infrastructure, alongside your databases. Customer data travels to a provider only when its service is called, and the response is logged back to the case. Data stays in your systems of record.
