🤝 FrankieOne Reseller & Implementation Partner

FrankieOne verifies identity.
Moroku runs it.

FrankieOne gives you one connection to identity checks, document and selfie verification, AML screening and fraud signals. Moroku adds the operation around it: the board your team works from, the customer follow-up that gets documents back, the approve or decline decision, and an audit trail your regulator can follow.

One partner, one contract: the FrankieOne licence, our pre-built operations components and the implementation, already live in production with an Australian credit union.

KYC case · Ivy Hartley
✓ Approved
🔎
Electronic ID check · FrankieOne
Address not matched, referred
Mon 9:02
📨
Customer invited · documents and selfie
Completed on mobile, licence and liveness passed
Mon 11:40
🔍
AML, PEP and sanctions
No matches
Mon 11:41
✅
Decision · Daniel Okoro
Approved, reason recorded, 14 events in audit trail
Mon 2:15
Live
In production on FrankieOne today
1
Contract for licence, components and delivery
6
Production gaps covered out of the box
Every
Document and decision kept in the audit trail

What FrankieOne Does Really Well

We chose FrankieOne because it's a strong identity and compliance API: one integration, hundreds of data sources, and checks set to match your risk appetite.

🌐

One API, Many Sources

A single integration reaches hundreds of identity and data sources worldwide. Adding a country or a check is configuration, not a new vendor project.

🔎

Electronic ID Checks

Name, date of birth and address are checked against authoritative sources in real time, so most customers pass without ever showing a document.

🤳

Document & Selfie

OneSDK captures ID documents and a selfie with liveness, and matches the face to the document. Hosted or embedded in your app.

🔍

AML Screening

PEP, sanctions and adverse media screening, with reviewers able to clear false positives and ongoing screening as watchlists change.

🛡️

Fraud Signals

Device, email and phone signals at onboarding, plus transaction monitoring once the customer is active.

⚙️

Risk-Based Recipes

Recipes and workflows decide which checks run, in what order, for each product and risk level, including business (KYB) checks.

An API Is Not an Operation

FrankieOne answers "is this person who they say they are, and are they safe to bank?" Running KYC in production also has to answer "who is working on this case, what are we waiting for, who decided, and can we prove it?" These are the pieces banks and lenders usually have to build themselves.

What FrankieOne gives you

The verification engine

✓
Check results and risk
Pass, fail or refer for each check, with a risk level
✓
Document and selfie capture
OneSDK flow for the customer to complete
✓
Watchlist matches to review
AML, PEP and sanctions hits flagged for a reviewer
✓
Recipes and workflows
A platform to configure, once your policy is translated into it
✓
Webhooks and events
Notifications your systems need to interpret and act on
✓
Check history
A record of the checks run against each person

What production also needs

The operation around it

📋
A daily workspace for your team
One queue across the whole application, with owners and waiting times
📨
Getting customers to finish
Branded invitations and reminders, so cases don't stall
⚖️
Approve and decline decisions
Roles, a recorded reason and a hand-off to account opening or settlement
🧩
Recipe setup from your policy
Specialist time to configure, brand and test the edge cases
🔌
Integration plumbing
Event sequences mapped and statuses kept in step with your systems
🗂️
An audit trail regulators can follow
Every document, change, comment and decision in one record per customer

Every KYC Case, Start to Finish, on One Board

Your team creates a task, invites the customer, reviews FrankieOne's results and makes the call, with every step recorded.

1
➕

Create

Start a KYC task manually, or automatically from a loan or account application

2
📨

Invite

One click sends a secure, branded link to upload documents and take a selfie, with reminders

3
🔎

Verify

FrankieOne runs the checks and results update the card automatically

4
⚖️

Decide

Reviewers see all the evidence in one place, then approve, decline or refer with a reason

5
🗂️

Record

Documents and decisions go into the audit trail, and approval triggers the next step

Lending · KYC Operations Illustrative data
Leads 12
Hartley, IvyHome loan · Priya R.
Loan
Novak, EthanSavings · Marcus L.
Started KYC 50
Brennan, ChloePersonal loan · Daniel O.
LoanAwaiting docs
Sato, LiamTransaction · Priya R.
Referred 15
Okafor, GraceHome loan · Marcus L.
Multi-Tax Resident
Walsh, NoahCar loan · Daniel O.
Loan
Approved 20
Reyes, MiaHome loan · Daniel O.
Loan
Fischer, JackSavings · Priya R.
Active 50
Murphy, AvaTransaction · Marcus L.
Clarke, OscarPersonal loan · Priya R.
Loan
Declined 50
Dunn, HarperCar loan · Daniel O.
Ito, LucasSavings · Marcus L.

Columns and stages are configured to match your policy. Names shown are illustrative.

How Moroku Closes Each Gap

You keep FrankieOne as your verification engine. We add everything around it, already built and running in production.

📋
Daily workspace

Operations Board

A Kanban board for every case: owners, comments, flags such as multiple tax residency, and how long each case has waited, next to the loan or account it belongs to.

📨
Customers finish

Customer Invitations

Secure, bank-branded links to upload documents and take a selfie through FrankieOne OneSDK, on mobile or desktop, with automatic reminders.

⚖️
Decisions

Approve or Decline

Approve, decline or refer with a recorded reason. Role-based permissions separate reviewers from approvers where your policy requires it.

🗂️
Audit trail

One Record per Customer

Every document, check, data change, comment and decision, with who and when, in one timeline ready for internal audit or a regulator request.

🧩
Recipe setup

Policy to Recipe

We turn your KYC policy into FrankieOne recipes and workflows, brand the hosted capture flow, and test the edge cases before go-live.

🔌
Integration

Tested Plumbing

Our webhook and event handling is already proven in production, and the Moroku Digital Services Layer connects approvals to your core and origination systems.

Why Moroku Should Lead Your FrankieOne Deployment

Moroku is a FrankieOne reseller and implementation partner. That means one accountable partner for the licence, the components that make it work and the delivery, instead of a vendor API and an internal build.

We've already taken FrankieOne into production for an Australian credit union, so the hard lessons on recipes, hosted capture and webhook events are behind us, not ahead of you.

  • FrankieOne licence supplied through Moroku
  • Pre-built Operations Board, invitations and audit trail
  • Recipe and workflow configuration from your policy
  • Branded customer experience on mobile and desktop
  • Connects to your core and lending systems
  • Works alongside your systems integrator
The engine

FrankieOne

  • Identity, document and selfie checks
  • AML, PEP and sanctions screening
  • Data sources and watchlists
Lead partner

Moroku

  • FrankieOne licence
  • Operations Board and audit trail
  • Recipe setup and go-live
Delivery

Your SI partner

  • Programme delivery and change
  • Integration across your estate
Policy

Your team

  • KYC policy and risk appetite
  • Decisions on the board, every day

Live Sooner, Lose Fewer Customers

🚀

Faster to Production

Start from components already running live rather than building case management from scratch

📈

More Customers Finish

Managed invitations and reminders stop applications going stale while you wait for documents

👥

Less Manual Effort

One board replaces spreadsheets, inbox chasing and switching between screens

⚖️

Regulator-Ready

Every document and decision evidenced in one place for AUSTRAC, APRA and your auditors

Planning a FrankieOne Deployment?

Whether you're choosing FrankieOne or already have it, we'll show you the Operations Board working end to end and map out your path to production.