SaFi Bank Space : Backoffice technical documentation

Created by Jakub Ukrop, last modified on Dec 02, 2022

Documentation for Backoffice-specific microservices.

The list of all components owned by the squad can be found in CODEOWNERS file.

Also, see the project-wide Dev HOWTO.

Videos

These were made during the ad-hoc FE onboarding and handover sessions.

  • Lark folder

    • 01 - FE docs overview, Audit logging architecture & FE, Maker-checker FE

    • 02 - Lark docs overview, Reconciliation design/BE/FE, Permissions architecture

    • 03 - The official technical handover, agenda per Engineering handover - Backoffice

    • 04 - Maker checker deep dive, both FE (part1) and BE (part2)

    • 05 - Reconciliation deep dive, both FE and BE

    • 06 - Official FE handover (docs, code)

Architecture

See Backoffice

Backoffice front-end (BOFE)

See Back-office front-end (BOFE)

The front end for backoffice employees.

  • Allows modifications of customer data (similar but not limited to what the Mobile app allows)

  • Includes reporting capabilities, most notably for reconciliation.

Backoffice manager

This service has several responsibilities documented separately

  1. Provides access to backend data for the backoffice frontend: Proxy endpoints for BOFE

  2. Handles Maker-Checker flows: Maker-checker flows

  3. Handles transaction reconciliation & settlement: Reconciliation

  4. Handles interactions with Genesys call center: Endpoints for Genesys

Audit log manager

See Audit log manager

  • Stores logs about data changes

  • Stores logs about communication history

  • Stores other logs (like login attempts or search attempts)

Other parts of the system are sending Kafka command messages when they need to log something.

Communication history manager

See Communication history manager

  • Stores emails/messages/chats sent or received by any part of the system and the customer

  • Stores call reports (memos written by CC agents after a call)

Jira gateway + Ticket manager

See Jira gateway and Ticket manager and Architecture

  • Allows getting a list of tickets based on criteria (customer ID) from Jira Ticketing System

  • Allows other MSs to create tickets in Jira

  • Emits ticket status of changed events

The ticket manager also houses dedicated endpoints to create tickets related to common business events like an investigation of a disputed transaction.

Meiro gateway

See Meiro gateway [wip]

  • Allows getting a customer profile from Meiro CDP

  • Used by backoffice-manager to get data about possible up-sell/cross-sell opportunities etc.

Genesys gateway

See Genesys gateway

  • Allows getting details of customer interactions from Genesys Call Center

  • Used by backofffice-manager to log Genesys call reports into communication-history-manager