← Investor Overview
VajraCloudAI logo VajraCloudAI Demo Guide

Live Demo Scenario Guide

15-minute presenter script · 7 seeded test bank customers · each scenario maps to a real compliance workflow a Nepali commercial bank would run on the platform.

1
Dashboard
2 min
2
Pick scenario
1 min
3
Run assessment
8 min
4
Show history
4 min
Before you start Run docker compose up -d, ./start-backend.sh, and ./serve.sh. Open the compliance dashboard first to set context, then jump into the live demo via the links below. Use the Ask Vajra button (bottom-right) for the 15-minute script and scenario help.

Quick reference

CodeScenarioBest for showingStart here
CUST-001Clean new applicantHappy-path onboardingLive demo
CUST-002Low-activity existingPeriodic review, low riskLive demo
CUST-003High RTGS volumeBusiness account, medium riskLive demo
CUST-004Cash structuringAML alert + STR draftLive demo
CUST-005Possible PEPSanctions / PEP screeningLive demo
CUST-006Sanctions name matchFalse-positive screeningLive demo
CUST-007Document inconsistencyKYC address mismatchLive demo
CUST-001

Ram Bahadur Thapa

New applicant: clean retail

New Low risk

What to say

A branch officer submits a straightforward first-time account application. All documents are original and consistent: this is the happy path every bank wants automated.

Demo steps

  1. Load CUST-001 from the customer dropdown
  2. Click Run onboarding (KYC + Sanctions)
  3. Show risk score: expect Low with Approve recommendation
Expected: Low risk · Approve · under 10 seconds per check
Open in live demo PoC data flow
CUST-002

Sita Gurung

Existing customer: salaried, low activity

Existing Low risk

What to say

An existing savings customer with normal payroll credits and modest withdrawals. Shows how periodic review works for low-risk accounts already in the CBS.

Demo steps

  1. Load CUST-002
  2. Click Review transactions (AML)
  3. Run AML: transactions are pre-filled (payroll, ATM, grocery)
Expected: Low risk · No suspicious patterns · clean audit trail saved to MongoDB
Open in live demo
CUST-003

Rajesh Karki

Business account: high RTGS volume

Existing Medium risk

What to say

Import/export trader with legitimate high-value RTGS transfers. Medium risk not because of illegality, but because volume warrants enhanced monitoring under NRB guidelines.

Demo steps

  1. Load CUST-003
  2. Run AML analysis on pre-loaded RTGS transactions
  3. Optionally run sanctions screen on the business owner
Expected: Medium risk · Review recommendation · trade activity noted but explainable
Open in live demo
CUST-004

Bikash Shrestha

AML alert: cash structuring pattern

Existing High risk

What to say

The headline AML scenario. Stated income is NPR 50,000/month but the account received multiple large cash deposits followed by an outbound RTGS: classic structuring typology from NRB's 2025 STR/SAR guidelines.

Demo steps

  1. Start at the compliance dashboard: show STR draft
  2. Load CUST-004 in live demo
  3. Click Review transactions (AML) and run analysis
  4. Point to assessment history and dashboard activity feed
Expected: High risk · Escalate · STR pre-fill shown on dashboard · structuring pattern flagged
Open in live demo View STR draft
CUST-005

Prakash Dahal

New applicant: possible PEP

New Medium risk

What to say

Former ward chair applying for a current account. Not automatically blocked, but PEP screening must run before approval. Shows human-in-the-loop decision making.

Demo steps

  1. Load CUST-005
  2. Run Sanctions & PEP Screening tab (or full onboarding)
  3. Highlight occupation field: "Former ward chair / consultant"
Expected: Medium risk · Enhanced due diligence · Review before approve
Open in live demo
CUST-006

Mohammad Hassan

Sanctions rescreen: name similarity

Existing Medium risk

What to say

Scheduled rescreen after sanctions list update. Name is similar to an SDN entry: likely false positive. Shows why AI reasoning matters: compliance officers need explanation, not just a binary hit.

Demo steps

  1. Load CUST-006
  2. Run Sanctions & PEP Screening
  3. Discuss false-positive handling and audit trail
Expected: Medium risk · Possible match · officer clears with documented reasoning
Open in live demo
CUST-007

Anita Tamang

New applicant: document inconsistency

New Medium risk

What to say

Permanent address (Kathmandu) differs from citizenship issuing district (Dhading). Customer provided a certified copy: KYC engine should flag for review, not auto-reject.

Demo steps

  1. Load CUST-007
  2. Run KYC Assessment
  3. Point to notes field: certified copy provided
Expected: Medium risk · Review · document inconsistency flagged with reasoning
Open in live demo
Recommended 15-minute investor demo path Dashboard (CUST-004 STR) → CUST-001 happy path (2 min) → CUST-004 AML alert (5 min) → CUST-005 PEP screen (3 min) → show assessment history + MongoDB persistence (2 min) → link to VajraCore platform layer if technical audience.
VajraCloudAI · Live Demo Scenario Guide · Confidential / Internal Distribution Only · © 2026