SaFi Bank Space : Customers

Scope

Orchestration of the customer onboarding process & customer offboarding process
Customer lifecycle and data management
- customer profile changes
- customer settings changes
KYC and Ongoing customer due diligence

Overview

Service decomposition and external dependencies (legend)

Component	Description
Mobile App	Customer facing mobile banking app.
Backoffice Web App	Backoffice web application used by bank’s employees.
Customer Manager	Main micro-service in the customers domain responsible for orchestration of activities, processes and data management within the domain.
Deduplication Engine	Business rules and logic necessary to deduplicate customer records.
Customer Access	Client library responsible for technical aspects of communication with the Customers data store (e.g. JDBC Repository).
Temporal.io Access	Client library responsible for technical aspects of communication with the Temporal.io server (e.g. WorkflowClient, etc).
TM Vault Access	Client library responsible for technical aspects of communication with TM Vault. Integration with TM Vault required in order to create & manage status of customer records. Even though the customer record is created also in TM, the SoT for customer data is still in the Customer-Manager. The record in TM needs to be managed in order to unlock some possibilities within TM such as opening an Account.
Advance AI Gateway	Gateway enabling to integrate with Advance AI system which is responsible for customer identification, document OCR, document forgery, risk assessment, etc. The gateway serves as our facade over the AdvanceAI API and as a single point of communication with AdvanceAI.
Customers	Data store dedicated to the persistence of customer related data. Stores the: customer profile for customers in all states, including prospect customers (customers during onboarding) customer settings customer KYC documents, with data collected from ID OCR during onboarding and any re-scanning of documents
Workflows (Temporal.io Server)	Data store dedicated to the persistence of workflow definitions and workflow instances. The Temporal.io client stores and executes workflow definitions. It has access to resources of the customer-manager during execution.
Customer Events	Events representing significant activities realized by the Customer domain are published to the corresponding topics.
TM Vault	Core banking system.
Advance AI	External system providing capabilities for KYC related use cases such as document validation, OCR, etc.
Output Manager	Customer Manager delegates sending of OTP to verify customer’s phone number and other communication with the customer to the Output Manager.
Ticketing Manager	Cases/issues and all tasks needed to be realized manually will be created as tickets in the Ticketing System.
Product Manager	Activities related to the management of customer subscription are provided by Product Manager.
Scheduler	Central scheduler will be responsible for triggering of planned or recurring activities realized by Customer Manager.
Audit Log Events	Account Manager publishes audit relevant events to be stored by Audit Log.
Fraud Prevention Manager (Slacker)	Slacker evaluates risk of fraud according to the provided data. Based on the resulting risk score the Customer Manager will trigger step-up authentication, approve or reject the operation.
Account Manager	Customer Manager delegates main account creation to Account Manager during onboarding.
SMS Access	Client library responsible for technical aspects of communication with the SMS Gateway.
SMS GW	Gateway service enabling to integrate with the Infobip provider.
Google API Access	Client library responsible for technical aspects of communication with the Google API Gateway.
Google API GW	Gateway service enabling to integrate with Google Services.
Google	Google provides customer’s address according his GPS coordinates.

Component diagram

Domain model

Customer Data DB Model

Open Points

Open Point

Result

Case management for issues during onboarding

Onboarding related cases will be managed by AAI OneStop platform.

However for other use cases there will be tickets opened in the Ticketing system depending on the particular requirements of the use case. Once the ticket is resolved, the “feedback” from the Ticketing System will be propagated to the Customer domain either automatically via integration (if applicable) or manually by the user via BOFE. For more information see https://safibank.atlassian.net/wiki/spaces/ITArch/pages/4325395/Backoffice#Approach-to-integration-with-Ticketing-System

Do we need to schedule any recurring jobs?

Central scheduler.

Integration with Atome to check customer’s existence during onboading? Impacts if Atome service unavailable.