A Frame workflow

Split a settlement across destinations

Keep a grouped allocation and its release decision together when one instruction has multiple destinations.

Talk to us How it works

The customer problem

Start with the
job to be done.

A bank-client instruction must allocate value across more than one approved account or form of payment.

For banks & financial institutions
01 / FRAME’S ROLE

Connect the workflow.

Bind the allocation to the instruction, check policy before release and record the reported outcome of each configured leg.

02 / YOUR ROLE

Keep control.

The bank defines the allocation and approved counterparties; its systems and configured providers execute and report each leg.

03 / THE RECORD

Make the result useful.

The source, destination allocations, decision and per-leg reported results remain tied to the same instruction.

Define the scope

A specific workflow.
A useful next step.

Each destination needs a configured connection. Completion depends on the participating systems; the workflow does not guarantee automatic failover or both-or-neither delivery across different rails.

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