# KYC/B workflow Manager

It is a frustrating irony: banks lecture you about "cybersecurity" and "phishing," yet many still demand sensitive documents like passports and tax returns via standard email—one of the least secure communication methods in existence.

There are three main reasons why banks (especially older institutions or specific departments) stick to this "bad habit."

***

### 1. The "Legacy System" Bottleneck

Many banks operate on core banking systems that are 30 to 40 years old. These systems weren't built with APIs or customer-facing portals in mind.

<a class="button secondary"></a>

* Email as a "Universal Bridge": Email is the only system that "talks" to everything. An analyst can receive an email and manually drag the attachment into their internal (and often very clunky) document management system.
* Cost of Integration: Building a secure, user-friendly portal that integrates perfectly with a bank’s internal compliance workflow (like the one you're building in AdonisJS) is incredibly expensive and slow.

### 2. Speed vs. Security (The "UX" Trap)

Banks often find that when they force customers to use a portal, "conversion rates" drop.

* Password Fatigue: Customers often forget their portal logins. If a mortgage officer needs a document *now* to close a deal, they know you can send an email in 30 seconds, whereas resettting a portal password might take 10 minutes.
* Mobile Convenience: It is easier to take a photo of a document on a phone and "Share to Email" than it is to log into a mobile-optimized portal, navigate to a specific "Case ID," and upload.

### 3. Organizational Silos

In large financial institutions, the "Digital Team" might have a beautiful portal, but the "Small Business Lending" or "Compliance" team might not have been granted access to use it for their specific workflows.

* Departmental Independence: High-touch departments (like KYB for complex corporate structures) often prefer email because it allows for a "conversation" alongside the document. A portal is often a "black hole" where the user can't ask questions.

***

### The Danger (and why your product is needed)

Sending docs by email is objectively dangerous for two reasons that your AdonisJS/Vue system solves:

1. Data at Rest: Your passport is now sitting in your "Sent" folder, the bank's "Inbox," and likely on multiple mail servers in between. If your email is hacked three years from now, that passport is still there.
2. No Chain of Custody: Emails can be intercepted or spoofed. Your system’s Audit Trail and Secure Upload features provide the "Proof of Integrity" that email lacks.

   <a class="button secondary"></a><a class="button secondary"></a>

> Peer Tip: When a bank asks you for an email attachment, the best "pro-move" is to send them a password-protected ZIP file or a Link to a secure folder (like ProtonDrive or OneDrive) and send the password via a different channel (like SMS).

***

#### How this helps your KYC/KYB product

This is actually your primary selling point. You aren't just selling a "Portal"; you are selling a way for the bank to stop using email. Would you like me to help you draft a "Marketing Comparison" table for your product that shows the security risks of Email vs. your Secure Relay? (This is exactly what you would show to a Chief Information Security Officer).