Payments
With Forest, run merchant onboarding, refunds, reconciliation, and dispute handling on top of any PSP. Audit at every step.
Forest hosts the workflows your PI, EMI, or PSP runs every day. Merchant onboarding, refunds, reconciliation, dispute handling, partner reporting.
Merchant and customer onboarding
KYC, KYB, and initial sanction screening run as steps in your onboarding workflow. Risk routing per merchant tier; agentic triage on routine cases.
Refunds, holds, and reversals
Trigger payment actions on the customer or transaction record. With Forest, approvals are part of the action; comms send through your help desk via MCP.
Settlement reconciliation
Continuous reconciliation across your PSPs, your acquirer, and your ledger. Breaks become cases routed with the source data attached.
Chargeback and dispute handling
Disputes from Stripe, Adyen, or your PSP land as cases with evidence auto-assembled. AI agents draft routine responses; your team submits the contested.
AML and ongoing screening
Detection stays with Hawk:AI, ComplyAdvantage, or Unit21. Forest runs the triage, review, escalation, and SAR workflow on the alerts they surface.
Partner-bank reporting
Sponsor-bank reports, regulatory submissions, and treasury statements package automatically and route through your existing transmission channel.

Built for licensed payment ops
A complete view per merchant
Merchant or customer, transactions, approvals, reconciliations, and disputes live on the same record. No tab-switching, no broken context.
Governance for humans and AI agents
Roles, approval thresholds, and two-person reviews apply to your team and your AI agents the same way. One audit trail.
Plug into the rails you already run
Stripe, Adyen, Modulr, Marqeta and your other rails fully connected, ready to tap from your workflows. Adding a new rail is a configuration change.
Plug into your payments stack
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
Does Forest move money?
No. Forest exposes record-level actions and runs the workflow around them. Money moves through your PSP, your acquirer, or your card processor. The response is logged back to the case.
How does Forest connect to my PSP and my processor?
Forest reaches your stack through datasources (for customer and transaction data) and through MCP connectors (for calling Stripe, Adyen, Marqeta, or any rail inside workflows). Adding a new PSP is configuration.
Can I route across two PSPs?
Yes. Workflow steps pick the rail they call based on rules you configure (cost, jurisdiction, customer segment, fallback). The audit is consolidated across rails.
How do approvals work on refunds and reversals?
Approval steps are configured per action and per role. A refund above a threshold can require manager approval; a reversal can require a two-person review. Approvals are part of the action.
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.

