CMi SDK

CMi SDK allows multiple mobile apps (provided by group companies and 3rd parties - partners) to use federated identification, authentication and authorization features of the CASE mobile application.

This approach has multiple business benefits:

• Customers activate just CASE mobile - all other apps can be just downloaded and used directly without any activation
• CASE mobile can be built as the “trust element”, “the key to the bank” and is the only place (application) that requests customers to enter the PIN
• Bank Federated Identity can be used in 3rd party partner applications, which (independently from the size, brand power or trustworthiness of the partner) technically have to be treated as untrusted elements in the business process

With CASE mobile handling all communication with the FS ecosystem, other applications (hereinafter also as “TPA(s)) do not need to bother with implementation details of the FS backends, do not need to handle activation and other processes related to the lifecycle of the activated mobile app, and - most importantly - do not need to synchronize their lifecycles with releases the security infrastructure. The CMi SDK is designed as the single point of contact between TPAs and the FS ecosystem.

Purpose of this documentation

This documentation describes the CMi SDK provided by Monet+ and Ahead iTec to developers of applications that use the ID services of CASE mobile. This documention will be subject to further changes as the CASE mobile evolve. This documention does not describe any business and organizational aspects of the “TPA onboarding process”.

Description of term and abbreviations can be found in Glossary.