Skip to main content

Register an authenticator with Temenos

If a user already exists in the customer-side system, you can initiate an authenticator registration that creates the same user in Infinity Fabric and Authentication Cloud and creates a new FIDO UAF authenticator tied to this user. On this page, you can find two main registration use cases: registration using only a mobile banking app, and registration using a mobile banking app and your web banking application.

Registration using mobile banking app​

In this use case, a mobile banking app is used to register an authenticator. The following step list shows the high-level workflow:

  1. The user opens the mobile banking app and enters their username and password.
  2. The user chooses to register a second-factor authenticator.
  3. The user receives an SMS with a code and enters the code into the mobile banking app.
  4. The mobile banking app registers the new authenticator with the help of Nevis Mobile Authentication SDK and Authentication Cloud.
  5. The mobile banking app receives the registration confirmation.

The following diagram shows a more detailed example of an end-to-end sequence of registering a new PIN or biometric authenticator through a mobile banking app. The diagram includes customer, Temenos, and Authentication Cloud functions, with the following color coding:

  • Yellow: Temenos functions
  • Blue: Nevis Mobile Authentication SDK and Authentication Cloud functions
Nevis Mobile Authentication SDK

The SDK is integrated into the mobile banking app.

Authentication Cloud functions include API calls to initiate the registration, verify a status token, and optionally, to get the username. For more information about these calls, see Register a mobile app and Retrieve a user.

Registration using a mobile banking app and a web application​

In this use case, both the web banking application and a mobile banking app are used to register an authenticator. The following step list shows the high-level workflow:

  1. The user opens the web banking application and enters their username and password.
  2. The user chooses to register a second-factor authenticator.
  3. The web banking application presents a QR code to start the registration.
  4. The user reads the QR code with the mobile banking app.
  5. The mobile banking app registers the new authenticator with the help of Nevis Mobile Authentication SDK and Authentication Cloud.
  6. The web banking application sends the registration confirmation to the mobile banking app.

The following diagram shows a more detailed example of an end-to-end sequence of registering a new FIDO UAF authenticator using a mobile banking app and your web application. The diagram includes customer, Temenos, and Authentication Cloud functions, with the following color coding:

  • Gray: Customer functions
  • Yellow: Temenos functions
  • Blue: Nevis Mobile Authentication SDK and Authentication Cloud functions
Nevis Mobile Authentication SDK

The SDK is integrated into the mobile banking app.

Authentication Cloud functions include API calls to initiate the registration, verify a status token, and optionally, to get the username. For more information about these calls, see Register a mobile app and Retrieve a user.