AI proposes. People set the limits.

The question you are asking

Can we let AI do more without more unapproved exposure?

The straight answer

For moves routed through Okren, yes. Routine moves inside your limits go ahead without a person in the way. Anything outside is reduced, held for a person, or stopped. Finance sets the limits.

Example

Where we would start

One workflow where volume or approval queues are the pain, in Shadow for a fixed period.

The question you are asking

Does this replace what we already do for screening and monitoring?

The straight answer

No. Okren sits alongside your screening, monitoring and reporting. It adds an independent check against your limits before a governed move executes, and a record kept apart from the system that proposed the move.

Example

Where we would start

Shadow on one path. Put Okren’s answers next to what your process did, and take that comparison to your committee.

The question you are asking

Will this get between my team and the release, or add a second queue?

The straight answer

Not for routine moves. In Shadow, nothing about how you release changes. In Enforce, moves inside the limits go ahead and exceptions go to the person you name. What happens to a held payment at a cutoff, and who is alerted, is agreed with you before Enforce.

Example

Where we would start

One existing wire or supplier-payment approval path, in Shadow for a fixed period.

The question you are asking

Will our cash limits hold before the money leaves?

The straight answer

Yes. Per-move limits and approved destinations apply to every system that can start a move, checked before the money leaves. A move over a limit is reduced to the permitted amount, or sent to a person.

Example

Where we would start

One transfer path between accounts or entities, in Shadow.

The question you are asking

Can the system proposing a move bypass, change or switch off the control?

The straight answer

The proposing system cannot approve its own move or define its own limits. Okren supervises what is routed through it, inside your environment. A path that skips Okren is not supervised, so the first step is mapping where your moves execute.

Example

Where we would start

Map your execution paths, then Observe one of them.

The question you are asking

What do we have to build, and what happens when it fails?

The straight answer

One decision point before a move executes. Your system sends the proposal, and Okren answers Approve, Reduce, Ask or Stop and records it. On a governed path, nothing executes until Okren has answered. If Okren cannot answer, the move is held, not executed.

Example

Where we would start

One path, Observe first, so you see the volume and shape of activity with no change to execution.

The question you are asking

Can I reconstruct a decision without asking the system that made the move?

The straight answer

Yes. The record is kept apart from the system that proposed the move. For each governed move it shows what was proposed, which limits applied, what Okren answered and why, who was involved and what happened next.

Example

Where we would start

Ask for a sample record from a Shadow period and test it against your own standard. Do not take our word for it.

The question you are asking

Can we start without changing how our payments are released?

The straight answer

Yes. Okren runs in Shadow beside your current release process, which carries on as usual.

Example

Where we would start

One existing wire or supplier-payment approval path, in Shadow for an agreed period, for example four weeks. Then compare Okren’s answers with what your process did and choose whether any of it should be binding.

The question you are asking

Will my strategy keep running?

The straight answer

Yes. Order size, account and counterparty limits are checked on each order before it goes to market, and routine orders are not slowed by a person. Orders from people, systems or AI go through the same check.

Example

Where we would start

One strategy or desk, in Observe, then Shadow.

The question you are asking

Is the check in place before anything is signed or released?

The straight answer

On a governed path, yes. Amount, destination, account and which agent is asking are checked before a move is signed or sent. If the destination is not permitted, it does not go out.

Example

Where we would start

Map where signing happens, then Observe one path.

The question you are asking

Can one set of rules sit above every provider we use?

The straight answer

Yes. Payouts, refunds and supplier payments started by people, systems or AI are checked against the same rules, whichever card, wallet, bank or payment provider carries them out.

Example

Where we would start

One payout or refund flow, in Observe.