Clearing vs settlement: what actually happens to a payment
The distinction behind payment risk, finality and why a cleared payment can still fail.
The settlement layer for modern finance.
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.
Your books. Your keys. Your control.
Ask Frame
Start with what you want to do.
See how Frame fits your business.
Two choices. A clearer way forward.
Explore the workflow. See the value.The Frame product family
Control what gets released. Give others evidence they can check. Reduce what treasury needs to fund.
Coordinate settlement through your own systems.
Connect the instruction, your systems’ execution and the reported result in one workflow. Each institution posts its own ledger entries and keeps control of its execution.
Your policy, enforced before money moves.
Rules checks instructions inside your instance, under keys you hold. Your risk management controls supply signed verdicts. A failed check stops release; an unavailable gate pauses settlement.
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 Verify , without a call to Frame or a login to your systems.
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.
One Frame.
The tools are included.
Issuer reserve proof and group treasury are in private preview.
Discuss your first projectYour infrastructure. New possibilities.
Keep the infrastructure you trust. Add policy before release and signed evidence of the reported outcome, while your platforms execute.
The film could not load. Read the complete workflow below, or open the video.
Start with the systems, accounts and connections you already use.
Frame Rules checks the instruction before release.
Your systems execute and report the entries on your books.
Frame Proof links the decision and reported outcome.
Illustrative transfer between accounts within one institution. Your platforms execute and report the entries.
Explore your workflowFrame 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 filmThe people behind Frame
Experience across payments, banking, digital assets and compliance. Brought together to modernize settlement through the systems institutions already use.
Modernizing settlement should build on the systems finance already runs. We built Frame to add the controls and evidence around them.
Meet our teamPartner with Frame
For the teams behind the systems institutions already run. Let’s define where policy and proof fit into your offering.
Explore partnershipsScope where an instruction is checked, how your systems report the outcome and which evidence the recipient needs.
Explore this togetherBring signed verdicts from the systems an institution already uses into its own settlement policy.
Explore this togetherDefine the receipt, trust roots and reporting scope your audit or counterparty workflow needs to verify.
Explore this togetherIntegration starts with your customer’s systems, policy and evidence requirements.
Your journey with Frame
Start with what you want to improve. We work with your team to define where Frame fits, validate the workflow and plan how it goes into operation.
Your systems. Your requirements. A path we agree together.
Define the workflow worth improving.
Together, we establish
A shared problem definition and a focus for your demo.
Your current systems, business and technical owners, and the result you want.
Agree where Frame fits.
Together, we establish
A defined scope, responsibilities and criteria for validation.
The integration points, policy requirements and teams that own execution.
Test the expected result and the exceptions.
Together, we establish
Reviewed results, refusal cases and gaps to resolve before rollout.
Agreed test data and reviewers from technology, operations and risk.
Plan the move into operation.
Together, we establish
An agreed implementation and recovery plan, with clear ownership.
Your internal approvals, operational owners and release requirements.
It starts with your workflow.
Rollout follows the validation and approvals agreed with your team.
Tell us the workflow you want to improve and the systems you use. We’ll shape a demo around the result your team needs.
The team will review your request and get in touch to arrange your demo.
Fields marked with an asterisk are required.
The team will get in touch to arrange a demo around your workflow.
Explore the product familyHaving trouble? Email Frame at [email protected]
The Frame perspective