Onboard faster, without lowering your guard.
New-customer checks scatter across email threads, PDF packs, and a sanctions search someone ran once. RUBIQ turns intake into one governed flow: KNECT verifies the entity and scores its risk into one defensible record, KAIRO keeps the audit trail, and the deal still moves.
- KYC / KYB
- AML & sanctions
- POPIA
- GDPR
The governed flow 4 gates
One front door, governed at every step.
RUBIQ runs every customer and supplier through four governed gates: invite, verify, decide, monitor. KNECT does the verifying and KAIRO, RUBIQ's GRC hub, holds the evidence, so each stage clears its gate before the next begins and the record is audit-ready by the time you say yes.
- KNECT
Invite & intake
An invite collects registration, directors and documents into one structured record. No duplicate accounts, no five-inbox paper chase.
One clean record opened - KNECT
Verify
Identity, entity, sanctions, adverse media, document integrity and your own rules resolve into a single risk score. The doubtful item routes to a person.
Five-factor screen cleared - KNECT + KAIRO
Decide
Every finding aggregates into one viability report, rated Clear, Caution or High Risk. You approve it; the evidence is already assembled and timestamped.
Decision logged and archived - KNECT → KAIRO
Monitor
A director resigns or a VAT status lapses, and the record re-screens itself. Renewals fire on schedule, so trust does not expire the day after signing.
Continuous, evidence-linked
Privacy-first by design
Customers and suppliers hold their own data in their own vault. KNECT works from a consent key that is authorized, traceable and revocable, so you get a verified answer without becoming the place their identity documents get stolen from.
How KNECT verifiesQuestions, answered
The short version.
How does RUBIQ verify a new customer or supplier?
RUBIQ verifies a new customer or supplier through one governed flow with four gates: invite and intake, verify, decide, then monitor. The verify gate runs a five-factor screen across identity, entity, sanctions, adverse media and documents, resolving them into a single risk score and routing any doubtful item to a person.
What is the difference between KYC, KYB and AML in RUBIQ onboarding?
KYC verifies an individual's identity, KYB verifies the business entity (its registration, directors and beneficial owners), and AML covers sanctions, PEP and adverse-media screening for money-laundering risk. RUBIQ runs all three inside one verify step, compositing identity, entity, sanctions and adverse media into a single risk score.
Where is the customer's identity data stored during onboarding?
The customer or supplier holds their own data in their own vault; RUBIQ does not become the place those identity documents get stolen from. KNECT works from a consent key that is authorized, traceable and revocable, so you receive a verified answer rather than a stored copy of their raw documents.
Does RUBIQ support POPIA and GDPR for onboarding?
Yes. RUBIQ is built for POPIA and GDPR onboarding, and is ISO 27001:2022 Certification Ready, POPIA and GDPR aligned. Its consent-key model means the subject keeps custody of their own data while you get a verified answer, so fewer copies of sensitive identity documents exist to lose.
What is the viability report, and when is onboarding decided?
The viability report is the single defensible record every finding aggregates into, rated Clear, Caution or High Risk, ready for sign-off. You make the decision; the evidence is already assembled and timestamped. After approval the record re-screens itself when details change, so trust does not expire the day after signing.
Ready when you are
See it run against your real onboarding.
A 30-minute discovery call about the way you actually onboard, customer side and supplier side. We scope the intake, the five-factor screen, the viability report and the monitoring that keeps it true, then arrange a demo on your own flow.
ISO 27001:2022 Certification Ready · POPIA & GDPR aligned