Online Banking Integration with RES

Existing customer authentication to OLB

There are 2 touch points where an existing customer needs to login into the Online Banking (OLB) to continue with their application. These are:

1. Where an applicant who is already logged in to OLB clicks a link to apply for a new product.
   In this instance, upon clicking the OLB link, to apply for a new account, OLB will redirect the user to the TJM application form with a user access token on the URL.
   
   TJM will use this token as a means of Authentication Bearer and fetch existing customer details from the API endpoint .  The existing customer details will be prefilled into the application form, and the customer number / ID will be stored with the TJM application for later account origination API calls.
2. The OLB authentication flow where the applicant enters the application from an external source, such as an email or bank’s website
   There are two scenarios for this anonymous entry into the application:
   1. When the primary applicant opens the application form and on the first page selects "I am an existing customer”.
   2. A joint applicant, who was nominated by primary applicant, as an existing customer of the bank, is requested to log into the application with their OLB credentials.
   
   In these two anonymous scenarios, the applicant is redirected to the login form which allows them to enter their OLB credentials. The login form will send the credentials to the customer identity and access management system, and request a user access token, which will then be used for an API call to fetch the existing customer details, same as in point 1 above.

Customer Onboarding

The solution supports two different API integration flows for customer onboarding.

These APIs will be called as part of the STP (straight through processing) or later, after successful application submission and review by the bank’s staff members.

1. Customer onboarding via the Digital Servicing
   This API orchestration is used where the Digital Servicing has been provisioned as part of the RES package.
   This flow will ensure that the customer record/s are created in both the Digital Servicing (OLB) and Core Banking systems. In this flow its assumed that the Digital Servicing system is responsible for creating the customer record in the Core Banking system immediately as well:
   1. Create prospect API call
   2. Create customer API call
2. Customer onboarding directly in Temenos Transact via the IRIS APIs
   This API orchestration is used where the Digital Servicing has not been provisioned as part of the RES package and the customer record/s need to be created directly in the Core Banking system.
   1. Create Customer

Configuration of the utilized APIs

The configuration toggle for the two above customer onboarding API orchestration flows is maintained in the Retail Origination solution Global Environment Configuration Service deployed with the solution, where service parameter = origination-common-includeServicing.

All service connection details including credentials for the APIs will be deployed as the following artefacts.

Service connections:

• Temenos Core – base URL and creds for T24/IRIS APIs
• Temenos Core Access Token – URL and creds to fetch API access token (Authentication Bearer) for the Transact API calls
• Temenos Digital Servicing – base URL and creds for Digital Servicing API calls
• Temenos Digital Servicing API Token – API token endpoint for Digital Servicing API calls
• Temenos Digital Servicing User Token – base URL and creds for existing customer access token fetch API

Resource (API) deep URLs are configured in the origination-common-baseContextPath parameter of the Global Environment Configuration Service.