In short
- Nine modules run independently, yet they lean on one identity core and one contract.
- You pick the integration path by flow, not by module: mobile, web, backend or merchant cabinet.
- The core can change without the modules changing, because they only ever talk through the contract.
From the outside RS-ID looks like nine separate products. Inside there is one thing: the identity verification core. Everything else is a way into that core.
Why there is only one core
Building a separate biometric check per channel would have been the most expensive mistake available: a model update would ship in three places, be measured in three places, and leave us with three different error statistics. So the verification logic lives in a single point.
- One model version, which keeps results comparable across channels.
- One audit log, so a regulator request is answered from a single source.
- Thresholds are tuned in one place and reach every channel at the same time.
The module map
The modules split neatly into three layers by role: intake, verification and control.
- Intake: Mobile SDK, Web SDK and the QR sign-in flow.
- Verification: liveness, anti-spoofing, document comparison and digital signature.
- Control: merchant cabinet, reporting and key management.
9
Modules
3
Integration paths
1
Identity core
60+
Connected partners
The contract is the important part
A module never reaches into the core directly. It knows only the contract: what goes out, what comes back, and what an error looks like. That is why we can swap the model inside the core without changing a line in partner code.
A good identity layer is good not because it offers a lot, but because it stops reminding you of itself once integration is done.