Skip to content

Payment orchestration

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical Payments
Prototype reference Payments prototype (ConnectSoft.DesignPrototypes)
Managed edition ManagedPlus (D33, D34)
Data residency tenant-region (restricted) (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Payments go through one provider with no fallback, reconciliation by hand, and no evidence per transaction.

Product intent

Payment intents, provider routing with fallback, reconciliation and disputes with receipts per transaction.

What the Factory makes different here: provider routing modelled like the model router (capability evidence, fallback chains, receipts).

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Enterprise Architect Agent, Security Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration, security, api-gateway
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent —
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Enterprise Architect Agent, Security Architect Agent, Integration Architect Agent, Backend Developer Agent, QA Agent, Compliance Officer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test, observability
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: security-and-compliance-workflows.

Generated product shape

C4Context
    title Payment orchestration system context
    Person(user, "Users", "Payments users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Payment orchestration") {
        System(ctx_Intents, "Intents", "intents, authorizations, captures")
        System(ctx_Routing, "Routing", "providers, rules, fallback")
        System(ctx_Reconciliation, "Reconciliation", "settlements, matching")
        System(ctx_Disputes, "Disputes", "chargebacks, evidence")
    }
    Rel(user, ctx_Intents, "uses through the product gateway GW-07")
    Rel(factory, ctx_Intents, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Intents intents, authorizations, captures PaymentCaptured
Routing providers, rules, fallback ProviderSelected
Reconciliation settlements, matching SettlementReconciled
Disputes chargebacks, evidence DisputeOpened

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
API gateway connectsoft-apigateway
Provider clients connectsoft-api-library
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Payments prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

ManagedPlus; PCI scope kept in providers; restricted classification.