A Frame workflow

Apply corridor limits before release

Require the agreed counterparties, limits, approvals and cutoff rules before a corridor instruction is released.

Talk to us How it works

The customer problem

Start with the
job to be done.

A provider’s corridor rules and screening results must govern a particular instruction across its existing partner systems.

For remittance & fx
01 / FRAME’S ROLE

Connect the workflow.

Check signed inputs and the instruction against the provider’s configured policy; retain the authorisation or policy refusal with the relevant policy identity.

02 / YOUR ROLE

Keep control.

The provider owns the policy, registered counterparties and compliance suppliers. Its banks or payment systems execute instructions that are allowed.

03 / THE RECORD

Make the result useful.

A checkable release decision tied to the instruction and policy identity, with the institution retaining access to refusal reasons.

Define the scope

A specific workflow.
A useful next step.

Your providers perform screening and hold the required market permissions. Connecting different banks requires agreed endpoints, controls and execution arrangements.

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