A customer can onboard themselves on sifi.app, or a specialist can raise the request by hand in the Internal Hub. Both end with a company in Core Banking and an authorised person who can sign in. Switch the channel on the map: every station shows which system acts, what gets written and the code behind it. Click a station or press Play.
36 stations7 phases14 Hub review states21 known gaps in this channel
Plain words first; who may act, the ordered steps across Hub ↔ Onboarding-MS ↔ Core Banking, endpoints, code by repo (web/, oms/, ih/, cb/), states written, emails and flags. Click any path to copy it.
Every runtime switch found in the five repos that turns a step, check, integration or message on or off: its default in code, what each position does and the stations it touches. Rows lit in green touch the selected station. Click a station to show it on the map.
CONSTANCE_CONFIG (config/settings.py:633-1031) and every environment switch, each followed to the line that reads it. Pure connection values (URLs, secrets, timeouts) are left out unless leaving them empty switches something off.SystemConfigParameter) or XML config, sifi.app's in its build environment.NAFATH_* (only the dashboard uses that client), POSTHOG_ENABLED (analytics only), sifi.app's marketing-page flags.The service split into its five departments: the wiring, the front desk (HTTP APIs), the back office (data and background jobs), the outside world (integrations) and shared tools. Open a box for its key files and the stations where it acts; a station chip shows that station's summary under the map. With “Follow the walk” on, the boxes involved in the selected station stay bright and are listed in the bar.
Django service Onboarding-MS/ (repo root; packages under onboarding/). Serves the customer API that sifi.app calls, the internal API that Internal Hub calls, and runs the background jobs (Celery) behind both gates.
config/settings.py:104-130 (LOCAL_APPS) and the URL mounts in config/urls/apis.py; models from each package's models.py.integrations/nafath is only imported by core/dashboard; on the web journey Nafath approval runs through the Core Banking registration endpoints (D3).