A Frame workflow

Apply existing checks before payout

Require the PSP’s screening, approval and limit results before releasing a payout instruction.

Talk to us How it works

The customer problem

Start with the
job to be done.

Compliance results exist in separate systems, and operations need them bound to the exact payout being released.

For psps & payment processors
01 / FRAME’S ROLE

Connect the workflow.

Check signed verdicts and approvals against the private release policy; seal policy denials as well as authorisations.

02 / YOUR ROLE

Keep control.

The PSP or its chosen vendors perform KYC/KYB, screening and monitoring. The PSP supplies the signed results and owns the policy and payment execution.

03 / THE RECORD

Make the result useful.

A traceable decision showing which instruction and policy identity governed release or refusal, with detail available to the authorised institution.

Define the scope

A specific workflow.
A useful next step.

Your providers perform screening and onboarding. A signed policy refusal is different from an invalid or unauthenticated request rejected before a decision can be made.

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