Payments & transaction ops
Trigger payment actions on customer records from one workspace, automatically or manually. Plug in your PSP, and access customer and transaction info at once. With audit trail for every step.
Forest is where your team and your agents trigger payment actions on the customer record. Your PSP moves the money; the process, approvals, and comms live with the case. Ready for audit.
Actions on the customer record
Refund, hold, partial refund, reverse, escalate to dispute. Each action lives on the customer or transaction record, not in a separate PSP dashboard.
Your PSPs, your way
Call Stripe, Adyen, Modulr, Mangopay, GoCardless, Wise, or whichever PSP moves the money. Add a second rail tomorrow, no re-platforming.
Approvals built into the action
A refund above a threshold can require manager approval. A reversal can require a two-person review. With Forest, approvals are part of the action, not a side process.
Agentic refunds and holds
Your AI agents handle eligible refunds and holds (configured by amount, reason, customer state), and route the rest to a human reviewer. All in one workflow.
Customer comms tied to the action
Refund confirmation, hold notification, and escalation messaging send from the same case through your help desk via MCP. Comms history lives with the action.
The audit holds every move
Every refund, hold, reversal, approval, and PSP response is recorded at the record level. Regulator-ready bundles export on demand.

Built for compliance at scale
A complete view per action
Customer, transaction, approval chain, agent reasoning, and PSP response live on the same case. No tab-switching, no broken context.
Governance for humans and agents
Roles, approval thresholds, and two-person reviews apply to your team and your AI agents the same way. Every action lands in one audit trail.
PSP flexibility, built in
Stripe, Adyen, Modulr and your other rails fully connected, ready to tap from your workflows. Routing across two PSPs is a configuration change.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
How do I configure a payment ops workflow in Forest?
Each payment action is a configurable step in the workflow you design: refund, hold, reverse, escalate. Approval thresholds, comms triggers, and PSP routing are decision criteria set at step level. Your team and AI agents work cases with one logic in one workspace.
Does Forest move money?
No. Forest exposes record-level actions and runs the workflow around them. Money moves through your PSP, which Forest calls at the point the action executes. The response is logged back to the case.
Which PSPs can I connect?
Common connections include Stripe, Adyen, Modulr, Mangopay, GoCardless, Wise, Checkout.com, and PayPal Braintree. Other PSPs connect through the same pattern.
Can my agents trigger refunds on their own?
Within the rules you configure. Agents can execute eligible refunds (configured by amount, reason, customer state) under their own scoped permissions. Anything outside those rules routes to a human.
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 at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record.

