A Frame workflow

Coordinate reciprocal FX obligations

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

Talk to us How it works

The customer 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.

For remittance & fx
01 / FRAME’S ROLE

Connect the workflow.

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

02 / YOUR ROLE

Keep control.

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

03 / THE RECORD

Make the result useful.

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

Define the scope

A specific workflow.
A useful next step.

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.

FrameSettle FrameRules FrameProof

Make the next move

Let’s start with your workflow.

Bring us the systems you use and the change you want to make. We’ll discuss how to move forward with the infrastructure you already use.

Talk to us

Your privacy

Functional storage remembers choices such as your Blueprint audience. Security verification protects enquiry forms.

Optional tools include Google Analytics, HubSpot, LinkedIn Insight, Snitcher, Vector and Swan. They measure visits, help identify visiting businesses and, where a match is available, business contacts, and support advertising. This is one combined choice for all these optional purposes.

Read our cookie notice