# Page 1

To gain a competitive edge, you absolutely need both, but they serve different "technical departments."

The technical departments within a bank are usually split into the "Platform/Core" team (the engineers) and the "Ops/Compliance" team (the business users). Here is exactly what each department needs to do with your system.

***

### 1. The Engineering / Platform Team

Their Tool: The API

This team hates logging into external dashboards. They want your system to be an invisible "utility" that flows into their own apps.

* Integration Task: They will use your API and Webhooks to connect your "Hub" to their *Core Banking System* (e.g., Temenos, Mambu).
* The "Event" Loop: They’ll set up a listener so that when a user's Soulbound Token (SBT) is burned or a new VC is shared, their internal database updates automatically.
* Automation: They use the API to trigger "Bulk Requests." For example, if they have 500 corporate clients due for a yearly KYB refresh, they’ll run a script to blast those requests through your Hub.

### 2. The Compliance / Risk Ops Team

Their Tool: The Dashboard

This team often has limited coding skills but high legal responsibility. They are the ones who "sign off" on high-risk clients.

* Human Review: For a $10M corporate account, a human must look at the documents. They will use your Dashboard to see the side-by-side forensics (pixel noise, metadata) you've built.
* Manual Overrides: Sometimes the AI flags a document as "suspicious" because of a weird stamp. The Analyst uses the Dashboard to click "Manually Approve" and adds a legal note for the regulators.
* The Panic Button: If an Analyst discovers a fraud ring, they don't want to wait for an engineer to "write an API call." They want to hit the "Revoke SBT" button in your UI immediately.

***

### 3. Why offering both is a "Legal Requirement" (2026 Standards)

In 2026, many financial regulators (like the EBA or SEC) require "Human-in-the-loop" for AI-driven decisions.

> The Compliance Gap: If you only have an API, the bank can't prove a *human* actually looked at the data when an auditor asks. The Dashboard provides the Visual Audit Trail (logs of who clicked what) that satisfies the regulators.

***

### 4. Technical Workload Comparison

| **Department**  | **What they build**                             | **How long it takes**            |
| --------------- | ----------------------------------------------- | -------------------------------- |
| Bank IT Team    | API Handlers, Webhook Listeners, Auth bridging. | 2–4 weeks (Sprint work).         |
| Bank Compliance | User Accounts, Role Assignments (RBAC).         | 1 day (Training/Config).         |
| Your Team       | The Core Hub + The Headless UI.                 | This is your main product build. |

***

### 5. Summary: The "Hybrid" Value Proposition

By providing both, you eliminate the "Not Invented Here" syndrome:

1. Low Friction: The Compliance team can start using your Dashboard on Day 1 (SaaS mode).
2. High Scale: Once the bank sees the value, the Engineers will automate the flow via the API.

Would you like me to help you draft the "Technical Specifications" for the Bank IT team? This would include the Webhook payloads (JSON) they need to listen for when a user shares a document.