Skip to main content

Sign transactions with Temenos

If a user is already logged in, they can sign transactions using their registered authenticator.

Transaction signing using a mobile banking app​

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

  1. After the user is logged in, the mobile banking app requests transaction signing.
  2. The user is prompted to authenticate themselves with a PIN or biometric data.
  3. The mobile banking app authenticates the transaction with the help of Nevis Mobile Authentication SDK and Authentication Cloud.
  4. The mobile banking app receives the authentication confirmation.

The following diagram shows a more detailed example of an end-to-end sequence of signing a transaction using a mobile banking app. 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 authenticate the operation and verify the status token. For more information about these calls, see Authenticate transactions with QR code or deep link and Authenticate transactions with push notification.

Transaction signing using a mobile and a web banking application​

In this use case, both a mobile banking app and a web banking application are used to sign a transaction. Either a QR code or a push message, or both can be used to sign a transaction. The following step list shows the high-level workflow:

  1. After the user is logged in, the web banking application requests transaction signing.
  2. The web banking application performs one or both of the following actions:
    • Presents a QR code that the user must read with the mobile banking app.
    • Sends a push message to the mobile banking app and presents the codes for number matching.
  3. The user authenticates the transaction with PIN or biometric data using the mobile banking app.
  4. The web banking application confirms the transaction signing.

The Transaction signing with QR code and Transaction signing with push message diagrams show more detailed examples of the transaction signing use cases. The diagrams include 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.

Transaction signing with QR code​

In this use case, the user is presented with a QR code, and by reading QR code, they initiate the authentication.

Authentication Cloud functions include API calls to initiate the authentication, verify the status token, and optionally, to get the username. For more information about these calls, see Sign transactions with QR code and Retrieve a user.

Transaction signing with push message​

In this use case, the user receives a push message that initiates the authentication. For added security, you can use the optional number matching feature.

Authentication Cloud functions include API calls to initiate the authentication, verify the status token, and optionally, to get the username. For more information about these calls, see Sign transactions with push notification and Retrieve a user.