Connect reciprocal FX obligations

Connect the two sides of an agreed currency exchange and make their authority and outcomes inspectable.

The problem

Start with the job to be done

Two counterparties owe different currencies to each other, so the release conditions and exposure between legs matter.

What Frame does

Represent reciprocal deliveries and policy decisions in one instruction, with configured holds, sequence and evidence of each reported leg.

What you keep

The counterparties agree and fund both sides, provide signed inputs and use their own banks or configured settlement venue to execute.

The record

A record of reciprocal obligations, agreed terms, policy decisions and reported outcomes, with the selected settlement assumptions explicit.

Scope

One workflow, then the next

Scope the two venues and release conditions. Different rails do not guarantee both-or-neither delivery; Frame does not supply FX liquidity. Cross-bank corridors work through configured connections.

Runs on

Your rules run first on every step, through the Rules Engine and the packs for this job.

More for market infrastructure

Other use cases

Frame for Market Infrastructure →

Your next move

Let’s scope it

Tell us about the flow you want to run. We’ll come back with a first step that uses the systems you already have.

Two products. One free tool.

Start where you are

Understand the next move

The people. The purpose.

Connect reciprocal FX obligations

Start with the job to be done

What Frame does

What you keep

The record

One workflow, then the next

Other use cases

Let’s scope it

Thank you.
Let’s talk.

Start with the job to be done

What Frame does

What you keep

The record

One workflow, then the next

Other use cases

Let’s scope it

Thank you.Let’s talk.

Thank you.
Let’s talk.