skills.rest
zenobiuszeto
zenobiuszetoCOMMUNITY
Explore all skills by this author →
GitHub

banking-domain-model

Define banking customer onboarding domain models with KYC and account opening workflows.

Updated Feb 25, 2026
Search Tags:#onboarding#identity-verification#kyc#consent-management#customer-profile#s3-presigned#product-catalog
One-click install
npx skills add https://github.com/zenobiuszeto/banking-strawman-capabilities --skill banking-domain-model
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: banking-domain-model
Source: https://github.com/zenobiuszeto/banking-strawman-capabilities/tree/main/skills/banking-domain-model
Command: npx skills add https://github.com/zenobiuszeto/banking-strawman-capabilities --skill banking-domain-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This unit solves the complexity of modeling and orchestrating customer onboarding in banking systems by providing a cohesive domain model for customer profiles, parties/households, account opening workflows, KYC ingestion, document management, and consent tracking so teams can deliver compliant, auditable account creation and identity verification flows.

Core Features & Use Cases

  • Customer Profile Aggregate: Centralized PII-aware CustomerProfile with encrypted sensitive fields, multi-address/contact support, and party relationships for households and joint accounts.
  • Account Opening & Eligibility: EligibilityEngine and AccountOpeningService to enforce age, SSN, and credit checks, produce idempotent account creation, and capture product snapshots.
  • KYC & Document Workflows: KycService with S3 presigned upload URLs, document tracking, pluggable identity verification adapters (Socure/Persona), and strict KYC state-machine transitions.
  • Compliance & Consent: Immutable consent audit records, customer preferences, Flyway migrations for schema control, and rules for encryption, auditing, and transactional consistency.
  • Use Case Example: Implement end-to-end onboarding that validates eligibility, initiates KYC, accepts S3 uploads for identity docs, delegates verification to an adapter, and transitions KYC state to approved or rejected while preserving audit trails.

Quick Start

Provide a complete data model and sequence diagram for customer onboarding including KYC state transitions and S3 document upload flow.

Frequently Asked Questions about banking-domain-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model a compliant customer onboarding workflow with KYC verification and document uploads?▼

Compliant customer onboarding is modeled using a centralized CustomerProfile aggregate with encrypted PII, pluggable identity verification adapters, S3 presigned document uploads, and transactional state-machine KYC workflows to ensure auditable account creation.

How does S3 presigned URL document upload work for banking identity verification?▼

S3 presigned URL document upload allows banking clients to securely upload identity documents directly to S3. The KycService generates these URLs, tracks document metadata, and delegates verification to pluggable adapters like Socure or Persona.

What is a transactional state-machine KYC workflow for account opening?▼

A transactional state-machine KYC workflow enforces strict state transitions during account opening, moving KYC status through initiated, pending, approved, or rejected states while preserving immutable audit trails and ensuring data consistency.

Can I use pluggable identity verification adapters for customer onboarding?▼

Yes, pluggable identity verification adapters support customer onboarding by allowing integration with external providers like Socure or Persona. The domain model delegates verification tasks to these adapters while maintaining strict KYC state transitions.

How do I enforce eligibility checks before opening a bank account?▼

Eligibility checks are enforced using an EligibilityEngine and AccountOpeningService that validate age, SSN, and credit checks. This process produces idempotent account creation and captures product snapshots for compliance.

Does this banking onboarding model support Flyway schema migrations and encrypted PII storage?▼

Yes, Flyway schema migrations control database schema evolution, while encrypted PII storage secures sensitive customer profile fields. Immutable consent audit records and customer preferences ensure full banking compliance and consistency.

Related Skills

Explore More Software Engineering Skills→
jabrenajabrena
423

513-frameworks-micronaut-db-migrations-flyway

Manage Flyway database migrations in Micronaut applications.

Community
Advanced
open-industry-operating-modelopen-industry-operating-model

kyc-customer-onboarding

Automate KYC customer onboarding for commercial banking workflows.

Official
Intermediate
ryan-nguyen-01ryan-nguyen-01
4

skill-storage-s3

Manage S3/MinIO uploads, downloads and access with presigned URLs and multipart uploads.

Community
Advanced
KelvinYauKKelvinYauK

PayKool × Home A Day 迎新消費獎賞

Validate PayKool × Home A Day welcome reward eligibility from customer and transaction data.

Community
Basic