Jumio turns identity into a live signal, Forest acts the moment it changes

A customer passes onboarding cleanly. Documents check out, selfie matches, no sanctions hit. Eighteen months later, the same account is quietly running money-mule activity. Nothing about the original verification was wrong; the person simply changed, or was always going to. For most of the industry’s history, that gap was invisible, because identity was treated as a box ticked once at signup and never revisited. The verification was a photograph. Reality kept moving.

Closing that gap is the shift Jumio has been pushing, and it changes what the operational layer underneath has to do.

What Jumio does: identity verification that keeps watching

Jumio has been in identity verification since 2010. Its platform recognizes 5,000+ ID document types, pairs document checks with biometric liveness detection built to stop deepfakes, and has processed over a billion transactions across 200+ countries and territories. It was named a Leader in the 2024 Gartner Magic Quadrant for Identity Verification, and ships no-code orchestration and AML screening in the same platform.

What’s most interesting for this conversation is where Jumio has taken the product recently. With Jumio Watch, launched in April 2026, it moves identity verification from a point-in-time decision into a continuous intelligence signal, on the explicit premise that a user verified today can become a fraud risk tomorrow. Some users start legitimate and drift; some are patient from the start. Either way, the verdict from onboarding day has a shelf life, and Jumio is now built to keep re-evaluating it.

What happens when a verified customer’s risk changes?

This is a better model of identity. But it raises a question that verification alone can’t answer: when the signal changes, what happens? A continuously updated risk score on an existing customer is worth exactly as much as the action it triggers. If the score quietly climbs and nothing in the operation responds, the intelligence just documents a loss instead of preventing one.

Acting on a changing signal is harder than acting at onboarding. At signup there’s a natural moment: the user is waiting, the flow is linear. Mid-lifecycle there’s no such moment. The customer is already active, the alert arrives in the background, and something has to decide whether to re-verify, restrict the account, open a case, or escalate, on the right customer, at the right threshold, with a record of why. That’s not verification work. That’s operational orchestration, and it’s where a continuous signal either becomes protection or evaporates.

How a Jumio risk change triggers a Forest workflow

That’s where Forest sits. A Jumio signal, at onboarding or from ongoing monitoring, lands in a Forest workflow and runs the steps your compliance team defined. When a returning customer’s risk profile shifts, the change can trigger the workflow automatically: re-run verification, open a review case with the full history attached, restrict specific actions pending a decision, or route to the right analyst. Nobody has to happen to notice.

The customer isn’t re-onboarded on a calendar; your team responds when the signal actually moves.

One audit trail, from onboarding to the latest risk change

Every step runs under one permission model and one audit trail, whether a human or an AI agent takes it. The response to a mid-lifecycle risk change is as governed and reviewable as the original onboarding decision. A regulator asking "you flagged rising risk on this account, what did you do about it and when?" gets an answer the workflow produced on its own, not one reconstructed after the fact.

That’s the direction Forest is heading, and one we already deploy with clients through partners like Jumio: continuous identity intelligence from a platform built to keep re-evaluating trust, feeding a backoffice that turns each change into a governed action. The two teams are working together on this model.

Continuous intelligence needs a continuous operation

Jumio solved a hard half of the problem: making identity a living signal that keeps re-evaluating trust long after onboarding, instead of a decision frozen at signup. But a signal that evolves only protects a business if the operation around it evolves in step: a rising risk score has to become a re-verification, a restriction or a reviewed case at the moment it rises. Otherwise continuous intelligence just produces a more detailed record of what went wrong.

That’s Forest’s job: turning a live identity signal into a live operational response, on the right customer, under the right rules, with the proof built in. Jumio says trust is changing. Your team decides what the business does about it, and Forest keeps the record.

If you’re moving identity from a one-time check to continuous monitoring but your operation still only reacts at onboarding, that’s precisely the conversation we have every day. Come show us the flow you’re trying to run.