The settlement layer for modern finance.

Modernize settlement. Keep control.

Modernize settlement through the systems you already use. Frame checks your policy before release and creates signed evidence of the reported outcome. Your platforms execute. You stay in control.

Request a demo

Your books. Your keys.

Ask FrameFind your starting point.

Your business.
Your next move.

Choose your organisation and the job you need to do. See where Frame fits.

A place to start

Make it
specific.

Pick your organisation above, or describe the workflow you want to improve.

Your taskFrame’s roleYour evidence

The Frame product family

One Frame.
Four products.

Control what gets released. Give others evidence they can check. Reduce what treasury needs to fund.

  1. 01Move

    FrameSettle

    Coordinate settlement through your own systems.

    Connect the instruction, your systems’ execution and the reported result in one workflow. Your institution posts the entries on its own ledger and keeps control of both settlement legs.

    • One connected workflow
    • Your systems settle
    • Your ledger stays in control
    Explore
  2. 02Check

    FrameRules

    Your policy, enforced before money moves.

    FrameRules checks instructions inside your instance, under keys you hold. Your screening systems supply signed verdicts. A failed check stops release; an unavailable gate pauses settlement.

    • Policy at the release step
    • Customer-controlled keys
    • Included in every deployment
    Explore
  3. 03Prove

    FrameProof

    A settlement receipt others can verify independently.

    Give the recipient a signed record of the instruction, decision and reported result. They check it on their own machine using FrameVerify , without a call to Frame or a login to your systems.

    • Signed decision records
    • Refusals included
    • FrameVerify included
    Explore
  4. 04Release

    FrameNetting

    Reduce the funding tied up across your accounts.

    Prove a position against the cash on your own books. Net obligations between entities, let your systems settle the residual, and preserve the gross record for tax reporting.

    • Group treasury
    • Net obligations, settle residuals
    • Preserve the underlying record
    Explore

One Frame.
The tools are included.

FrameAPI
Connect Frame to your systems.
FrameConsole
Work with your instance and its records.
FrameVerify
Check the evidence on your own machine.
Start with Frame

Issuer reserve proof and group treasury are in private preview.

Discuss your first project

THE FRAME PRODUCT FAMILY

Frame

Illustrative product records. Your books. Your keys. Your control.

Your infrastructure. New possibilities.

Connect your existing systems to digital finance.

Keep the infrastructure you trust. Add policy before release and signed evidence of the reported outcome, while your platforms execute.

One instruction. Policy, execution and evidence connected.ILLUSTRATIVE WORKFLOW
  1. 01

    Keep your infrastructure.

    Start with the systems, accounts and connections you already use.

  2. 02

    Check your policy.

    Frame Rules checks the instruction before release.

  3. 03

    Your platforms execute.

    Your systems execute and report the entries on your books.

  4. 04

    Keep the evidence connected.

    Frame Proof links the decision and reported outcome.

Illustrative transfer between accounts within one institution. Your platforms execute and report the entries.

Explore your workflow
Read the full workflow

Frame adds a policy decision before release and signed evidence of the reported outcome to existing customer settlement infrastructure. Customer platforms execute and retain their books and keys. This illustrative workflow takes place within one institution. The film is silent. It follows an instruction from an operating account to a treasury account. An approval is required and received; release is then permitted. Customer execution subsequently reports a debit, a credit, and a ledger update. Frame Proof links the instruction, policy decision, and reported result in one signed receipt. The final wide view retains the completed operational details. Frame Rules supplies the policy decision; Frame Proof connects the instruction, decision and reported outcome.

Open the film

Explore a sample workflow

Follow a settlement.
See each decision.

Follow an illustrative transfer between two accounts. Explore the steps, try a refused instruction and see what your systems would record.

Illustrative workflow. No money moves and no account is connected.

Start on your books.

Your system submits a settlement instruction. Your institution keeps its accounts, signing keys and control.

One instruction. Both legs inside your institution.

Your policy decides.

Frame checks signed inputs against your active policy before release. A failed check stops the instruction. An unavailable gate pauses settlement.

The authorisation is recorded before release.

Your systems settle.

After an allow decision, your institution posts the entries on its own books and reports the outcome.

Frame does not hold the money or execute the entries.

The evidence travels.

Frame seals the decision and reported outcome into a portable receipt. Its recipient checks it on their own machine, using a trusted verification key.

Verification works without a call to Frame.
SETTLEMENT / 001329Illustrative data
Your institutionYour books · Your keys
  1. Instruction
  2. Policy
  3. Books
  4. Evidence
FrameSettle Submitted
Settlement instruction4,250,000USD
FromOperating account
ToTreasury account
Awaiting your policy check. Books unchanged.
FrameRules Allow
01Signed instructionVerified
02Your screening verdictClear
03Required approvals2 of 2
Release decisionAuthorised.
Signed decision recorded before release.
Your institution’s ledgerPosted

Your systems post the entries.

Operating account− 4,250,000 USD
Treasury account+ 4,250,000 USD
Net change across both accounts0USD
Outcome reported by your institution.
FrameProof Sealed record
One portable receiptReady to verify.
Policy decision
Allow
Reported outcome
Entries posted
Receipt integrity
Signature + log inclusion
Auditor or counterparty
Checks with trusted verification keys
01 / 04 · Instruction submittedILLUSTRATIVE

Illustrative data from one institution. Cross-bank corridors are in development.

Explore Frame Proof

Solutions

The problem is complex.
The difference is clear.

Find the workflow you want to improve. See the change in a concrete example.

Design settlement around your existing banks.

Your banks execute on separate systems. A shared workflow needs an agreed handoff between the instruction, each institution and the reported result.

Why it matters

A defined handoff both sides can inspect, while each institution keeps its own books and keys.

How Frame fits

Scope a workflow around your existing banks. Connect the instruction, policy decisions and reported outcomes; each institution retains execution.

In your demo Map the two institutions, the handoff and the connections to validate.

Scope your bank workflow Explore the solution
ForBanks & financial institutionsRemittance & FX
ILLUSTRATIVE EXAMPLE
The institutional boundary stays intact

Separate books.
Shared evidence.

INSTITUTION AOwn booksOwn signing keys
INSTITUTION BOwn booksOwn signing keys
Portable settlement receipt
Instruction
What was agreed
Authority
Who authorised it
Policy identity
Which policy governed it
Reported outcome
What the systems recorded

The recipient checks the receipt using a trusted verification key. Cross-bank corridor design is in development.

Cross-bank corridors are in development. Current settlement workflows run within one institution. Connections and execution arrangements require scoping.

Fund the net. Keep the gross record.

Your entities owe each other money. Funding every gross obligation ties up cash, while finance still needs the original detail for reconciliation and reporting.

Why it matters

Fund the remaining amount after eligible obligations are offset, with the original obligations still accounted for.

How Frame fits

Net eligible obligations, calculate the residual and let your systems settle it. Keep the gross record attached to the result.

In your demo Work through an illustrative cycle and inspect the net funding and gross obligations.

Explore your netting cycle Explore the solution
ForCorporates & treasuryBanks & financial institutions
ILLUSTRATIVE EXAMPLE
Three entities. One settlement window.

What do you
actually need to fund?

Original obligations
A → B
USD 10m
B → C
USD 8m
C → A
USD 6m

The gross record stays intact.

Gross obligationsUSD 24m

USD 24m across three obligations.

After netting, A funds USD 4m; B and C receive USD 2m each. All amounts are illustrative.

Group treasury is in private preview. The example assumes eligible obligations in one currency and settlement window; results depend on those obligations.

Bring the cash leg into your asset workflow.

Asset delivery and payment can happen in different systems. Your team needs to connect the trade obligations, release conditions and reported results.

Why it matters

A defined asset and payment workflow, with records operations teams and counterparties can inspect.

How Frame fits

Scope the asset and cash endpoints, policy and execution arrangements. Connect the paired obligations, decisions and reported results in the agreed workflow.

In your demo Map one asset and cash workflow: who executes each leg and what the record would contain.

Scope your asset and cash workflow Explore the solution
ForExchanges & digital assetsBanks & financial institutions
ILLUSTRATIVE EXAMPLE
Illustrative cash-leg evidence

A cash payment.
A checkable record.

CASH-LEG RECORD / EXAMPLE
Instruction
Cash payment for an asset trade
Decision
Signed under your keys
Outcome
Reported cash-leg result
Integrity
Anchored to the signed log
Your auditor or counterpartyChecks it independently.

The recipient uses trusted verification keys on their own machine.

This example shows evidence of the cash leg. Asset delivery, funding and finality depend on the configured venue and connected providers.

See what a receipt proves

Asset and cash endpoints require scoping. Both-or-neither delivery is specific to a configured shared venue; it is not guaranteed across arbitrary banks or rails.

Coordinate payouts across your existing providers.

Allocating a payment across accounts, providers or forms of money means keeping each destination tied to the approved split.

Why it matters

One allocation to follow across your configured destinations, from the instruction to the reported results.

How Frame fits

Bind the allocation to the instruction, check your policy before release and connect the outcomes reported by your providers.

In your demo Walk through a payout allocation, its release checks and the results your providers report.

Map your payout workflow Explore the solution
ForPSPs & payment processorsRemittance & FX
ILLUSTRATIVE EXAMPLE
A governed split across destinations

One instruction.
Every leg accounted for.

Settlement instructionUSD 100,000
60%Fiat paymentUSD 60,000
40%Tokenised depositUSD 40,000
  1. 01Allocation bound to the instruction
  2. 02Your policy checked before release
  3. 03Your systems execute; results recorded

An illustrative allocation, subject to your integrations and policy.

Illustrative allocation, subject to integrations, funding and policy. Frame does not supply a payout network or liquidity.

Delegate payment requests within clear limits.

An application acting for your team needs explicit boundaries on where it can request a payment and how much it can request.

Why it matters

Delegated requests governed by your limits, with decisions your team can review.

How Frame fits

Use a signed mandate to define the delegator, permitted destinations and limits. Check the request before your systems execute and record the policy decision.

In your demo Try a request within a mandate and one above its limit, then compare the decisions.

Scope your delegated workflow Explore the solution
ForPSPs & payment processorsCorporates & treasury
ILLUSTRATIVE EXAMPLE
A signed mandate sets the boundary

Delegated authority.
Defined limits.

Per-payment limitUSD 500Approved destination · Signed mandate
Example decisionUSD 180: within the mandate.

The request can be authorised under this limit. Your systems execute.

In this example, the authorised request and policy refusal each produce a verifiable mandate record.

Illustrates the documented mandate demo. Scope agentic payment deployments with our team.

Industries

Your world.
A clearer way to settle.

Different institutions. Different obligations. See where Frame fits in the work your team already does.

Sunlight between limestone and glass financial buildings
01 / 05Banks & financial institutions
Frame for Banks & FIs

Connect new forms of money to the systems you already run.

A client may hold one form of money and need a payment or position in another. Start with the accounts, providers and controls your bank already uses.

Your team's task

Define the source, destination and providers for a bank-money or digital-money workflow.

With Frame

Connect the configured instruction, supplied conversion terms, policy and reported results. Your institution retains custody and execution.

Scope a bank settlement workflow
In your demo

Map a stablecoin or tokenised-deposit workflow against your existing accounts and controls. Identify the connections and conversion arrangements to validate.

Evidence your team can use

The instruction, governing policy, agreed terms and results reported by connected providers.

Request a demo

Current settlement workflows run within one institution. Cross-bank corridors are in development. Digital-money connections require scoping.

Explore this industry
A customer making a contactless payment in a shop
02 / 05PSPs & payment processors
Frame for PSPs & processors

Keep payout instructions, approvals and outcomes connected.

Merchant obligations can span several destinations and providers. Operations needs to follow the approved allocation through to each reported result.

Your team's task

Distribute a known amount across approved accounts and providers.

With Frame

Govern the allocation before release and connect the results your providers report to the original instruction.

See a payout allocation
In your demo

Walk through one allocation, the checks before release and the provider results your operations team needs to follow.

Evidence your team can use

The payout instruction, destination allocation, policy decision and reported outcomes.

Request a demo

Subject to your integrations, funding and policy. Frame does not supply the payout network or liquidity.

Explore this industry
Travellers crossing an international airport terminal
03 / 05Remittance & FX
Frame for Remittance & FX

Carry agreed conversion terms through settlement.

The quote, funding source and destination must describe the same payment. Your team needs to follow the agreed rate and amounts through to the reported outcome.

Your team's task

Connect your provider’s quote, source amount and destination requirements.

With Frame

Bind the supplied conversion terms to the instruction and policy decision, then retain the outcomes reported for each leg.

See the settlement workflow
In your demo

Trace a supplied quote through the agreed amounts and rate, the instruction and the reported payment results.

Evidence your team can use

The agreed rate, currency amounts, instruction, authority and reported outcomes.

Request a demo

Subject to configured providers, funding and policy. Frame does not provide FX liquidity. Cross-bank corridors are in development.

Explore this industry
Container cranes at a working port in warm evening light
04 / 05Corporates & treasury
Frame for Corporates & treasury

Fund what your group owes after netting.

Reciprocal obligations can offset the amount your group needs to fund. Finance still needs the gross detail for reconciliation and reporting.

Your team's task

Identify eligible obligations, available liquidity and the settlement window.

With Frame

Calculate the eligible net result, let your systems settle the residual and preserve the underlying gross record.

Try the netting example
In your demo

Work through illustrative obligations and inspect both the net funding requirement and the original gross record.

Evidence your team can use

The original obligations and net result, with the detail needed to reconcile them.

Request a demo

Group treasury is in private preview. Eligibility, currency and settlement window determine the result. The gross record does not determine tax treatment.

Explore this industry
A market operations floor overlooking the city
05 / 05Exchanges & digital assets
Frame for Exchanges & digital assets

Connect the trade to its cash payment.

An asset and its cash payment may use separate endpoints. Your team needs to coordinate the obligations and understand what each reported result means.

Your team's task

Define the asset leg, cash leg, release conditions and execution providers.

With Frame

Scope a governed workflow connecting the paired obligations, policy decisions and results. Your venue and connected providers execute.

See the cash-leg evidence example
In your demo

Map one asset and cash workflow: who executes each leg, which conditions apply and what a counterparty could check.

Evidence your team can use

The paired asset and cash obligations, governing decisions and reported results within the agreed scope.

Request a demo

Execution and finality depend on the configured venue and connected providers. Settlement evidence is distinct from proof of solvency or reserve coverage.

Explore this industry

The people behind Frame

Built by people
who know the stakes.

Experience across payments, banking, digital assets and compliance. Brought together to modernize settlement through the systems institutions already use.

WHY WE BUILT FRAME

Modernizing settlement should build on the systems finance already runs. We built Frame to add the controls and evidence around them.

Talk with our team
Alexander Taskey

Alexander Taskey

Founder & CEO

20 years in B2B payments. Co-founded Merchant Broker, acquired by AMCS Group in 2022.

Lloyd Moore

Lloyd Moore

Co-Founder & CTO

20+ years building financial infrastructure. Former CTO at Blockdaemon; previously Valence, Atom Bank and the Royal Marines.

Nathalie Oestmann

Nathalie Oestmann

COO

20 years scaling regulated financial services. Former COO at Curve and Outlier Ventures; previously American Express.

Joanna Jenkins

Joanna Jenkins

CCO

20 years in banking, fintech and digital asset compliance. Former Head of International Compliance at Kraken.

Noah Herman

Noah Herman

CSO, North America

Payments and digital assets executive leading North American growth. Previously scaled stablecoin revenue at Fortris; Circle’s first go-to-market hire.

Louisa Murray

Louisa Murray

CSO, UK & EMEA

Payments executive leading UK and EMEA growth and partnerships. Former Chief Revenue Officer at Railsr/Equals Group.

Bhanu Chawla

Bhanu Chawla

CMO

15 years scaling high growth fintech companies. Previously Klipboard and ComplyAdvantage.

Mitchell Salis

Mitchell Salis

CFO

20+ years advising and scaling companies. Experience across lending platform exits at Lendful and Thinking Capital.

Build with Frame

Your infrastructure.
A stronger
settlement offer.

For the teams behind the systems institutions already run. Let’s define where policy and proof fit into your offering.

Explore partnerships
01Core systems & ledgers

Connect the release step.

Scope where an instruction is checked, how your systems report the outcome and which evidence the recipient needs.

Explore this together
02Screening & monitoring

Put existing checks to work.

Bring signed verdicts from the systems an institution already uses into its own settlement policy.

Explore this together
03Audit & assurance

Make the evidence usable.

Define the receipt, trust roots and reporting scope your audit or counterparty workflow needs to verify.

Explore this together

Integration starts with your customer’s systems, policy and evidence requirements.

From discovery to rollout

Start with one workflow.
Build the path forward.

Agree what a better result looks like, where Frame connects and what your team needs to validate. Your operating model sets the scope.

  1. 01

    Discovery

    Define the workflow worth improving.

    Inputs and outcomes for discovery
    Your inputs
    Your current systems, business and technical owners, and the result you want.
    What you establish
    A shared problem definition and a focus for your demo.
  2. 02

    Scoped workflow

    Agree where Frame fits.

    Inputs and outcomes for scoped workflow
    Your inputs
    The integration points, policy requirements and teams that own execution.
    What you establish
    A defined scope, responsibilities and criteria for validation.
  3. 03

    Controlled validation

    Test the expected result and the exceptions.

    Inputs and outcomes for controlled validation
    Your inputs
    Agreed test data and reviewers from technology, operations and risk.
    What you establish
    Reviewed results, refusal cases and gaps to resolve before rollout.
  4. 04

    Rollout

    Plan the move into operation.

    Inputs and outcomes for rollout
    Your inputs
    Your internal approvals, operational owners and release requirements.
    What you establish
    An agreed implementation and recovery plan, with clear ownership.

Rollout follows the validation and approvals agreed with your team.

Start with a tailored demo
Talk to FrameLET’S GET SPECIFIC

See Frame in
your workflow.

Tell us the workflow you want to improve and the systems you use. We’ll shape a demo around the result your team needs.

Your demo covers
  • Your workflow mapped to your existing systems.
  • A relevant walkthrough of the controls and execution steps.
  • Integration questions and a proposed scope for validation.
What happens next

The team will review your request and get in touch to arrange your demo.

Request your Frame demo.

Fields marked with an asterisk are required.

Review mode. Test the form freely. Nothing is sent to Frame or HubSpot.

Your details and enquiry

A few lines are enough.

Review only. Your test details stay in this browser and are not sent to Frame. Privacy policy.

Loading form…

Your privacy

This website uses local storage to remember functional choices, such as your selected Blueprint audience.

Optional analytics and advertising cookies are not active on this website. Review forms simulate submission locally. No details are sent to Frame or HubSpot.

The story behind Frame

Frame, with Alex and Lloyd