Skip to content

Architecture Overview

DragonPay's Payment Hub (PH-01–PH-13) is the shared domain, policy, routing, execution, journaling, reconciliation, and operations capability underneath every Payment Product. Payment Products and Experience (PP-01, CX-01, OX-01, CI-01) sit on top of it — the first is Person-to-Person payments, delivered through a channel experience embedded in a credit union's own digital banking, backed by the operations console and the first CU's concrete integration. See the architecture diagram in Product Overview for the shape of the whole system.

The pages under this tab are concise architecture overviews of how that gets built — not exhaustive implementation documentation. DragonPay is pre-code, so most of what's described here is either an approved direction with no code behind it yet, or still an open question. Where useful, a page says so in plain language (built, approved/planned, or unresolved) rather than a formal status field — see the Decision Register for what's actually still open, and Engineering Foundation and Platform Standards §4 for the current technology baseline.

Domains covered here

  • Security — the STD01-12 baseline and workforce/ operational identity controls.
  • Identity and Access — authentication, authorization, roles, and permissions.
  • Application Patterns — backend/frontend stack and the modular-monolith boundary model.
  • Data Architecture — the canonical payment domain model and persistence approach.
  • Event Driven Orchestration — durable workflow and asynchronous messaging.
  • Kubernetes and Infrastructure — runtime, cluster, and infrastructure-as-code direction.
  • Observability — logs, metrics, traces, and the distinction from PH-09's Journal and PH-13's reporting.
  • Integrations — the Connector/Adapter/Connection model every external integration follows.
  • Operations — how the platform will actually be run day to day, and how the environment gets stood up.
  • MultiTenancy — today's single-tenant reality versus future multi-CU scope.
  • Notification Engine — the domain/ mechanics split for outbound communications.