ID-Truster is a parallel system for verification. It runs alongside your systems, not inside them. How the parts connect is in How the ID-Truster ecosystem fits together.
Your systems stay as they are
You keep your CRM, your email system, your SMS provider, and your phone system.
Your current systems talk to ID-Truster through APIs. They call your ClientDB, which returns what they need, such as a trust code.
Neither messages nor calls go through ID-Truster
Your emails, texts, and calls go out through the systems you use today. ID-Truster is a parallel system that only handles verification.
When you send an email or a text with a trust code, ClientDB returns the code to your system, and your own email system or SMS provider sends the message. When you call, the call goes through your own phone system. Only the verification signal passes through ID-Truster.
If your ClientDB or ID-Truster is down
Your own systems keep working. Your CRM, email system, SMS provider, and phone system do not depend on ID-Truster, so your emails, texts, and calls still go out as usual.
Only verification is affected. Until the service is back, your customers cannot check your messages and calls in the app, and you cannot issue new trust codes.


