Choose your country or region

For compliance and operations

Your auditor will ask why. You’ll know.

Every score comes with its reasons. Every high-risk decision needs two people. Every action is on the record.

The problem

Spreadsheets don’t survive an audit.

Reviews spread across email, spreadsheets and provider portals are slow and hard to defend. Nobody can say why a customer scored what they did.

Here, every applicant’s checks, score, documents and decisions sit in one place – with the reasons attached.

  • Your policy, versioned and published by two people
  • A reason for every point of every score
  • One queue for personal and business applications
What changes

Controls that run every time.

Built into the work, not bolted on after.

Explained risk

Same inputs, same score, and a reason for each point under your policy.
Learn more

Two-person decisions

The person who recommends a high-risk case can’t also approve it.

No tipping off

Customers never see scores, checks or reviews – not even in emails.

Provider errors stay neutral

An outage is retried and recorded – never held against the customer.

Risk after opening

Policy changes, new answers, screening alerts and periodic reviews keep risk current.

Full audit trail

Who did what, when and why – by name, and exportable for your auditors.
Learn more
How it works for you

One review, four steps.

  1. Step 1: Checks runIdentity, screening and registry checks start when the customer submits.
  2. Step 2: Score with reasonsYour policy scores the applicant and routes the case.
  3. Step 3: Ask, if neededRequest information or documents in plain words.
  4. Step 4: Decide with two peopleHigh risk needs a recommendation and a different person to finalise.
Questions

The questions you’d ask.

Can we reject applicants automatically?
Only if your bank turns it on, and only for clear-cut cases your policy prohibits – such as a country you don’t serve or an applicant under your minimum age. It’s off by default. The customer is told the decision was automatic and can ask for a person to review it. A score, a possible match or a provider error always goes to your team.
How do you avoid tipping off customers?
Customers see only simple statuses. Messages – including your own templates – can’t use words about risk, screening or reviews.
Can we see what changed when we publish a new policy?
Yes. Each re-assessment shows how many customers were checked, how many changed tier and how many reviews it opened.
Pilot programme

Test it on your toughest reviewer.

A demo set up as your bank: a customer applying, your team deciding, a business paying.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment