Skip to main content

MVP implementation backlog

Status: Proposed dependency sequence, not a committed sprint plan. Use GitHub Issues for delivery tickets with links to requirement IDs.

Workstream 0 — Legal, commercial and partner decisions​

  • B-001: Validate custody, licensing and consumer debt-discharge structure (FR-010/012).
  • B-002: Select payment/token-vault/settlement/payout providers and confirm API capability (FR-005/008/011).
  • B-003: Approve mandate and customer notice wording, retry and dispute policy (FR-004/008/013).
  • B-004: Confirm merchant pricing, processing costs, reserves and fee invoicing model (FR-017).

These decisions gate production money movement; engineering can prototype against a simulator while unresolved.

Workstream 1 — Platform foundation​

  • B-101: Monorepo/repository conventions, CI, environments, observability and secrets.
  • B-102: PostgreSQL/Prisma base schema, migrations and test fixtures.
  • B-103: Authentication, RBAC and tenant isolation (FR-002).
  • B-104: Audit event, idempotency key and outbox/inbox infrastructure (FR-006/016).

Workstream 2 — Merchant and consumer foundations​

  • B-201: Merchant onboarding and KYB status gates (FR-001).
  • B-202: Merchant portal team, integrations and API credentials (FR-021).
  • B-203: Consumer registration, verified linking and recovery (FR-003).
  • B-204: Hosted tokenisation, mandate evidence and preferences (FR-004/005).

Workstream 3 — Billing and orchestration​

  • B-301: Merchant bill API, validation, versions and status webhooks (FR-006/014).
  • B-302: Scheduling, notification outbox and merchant cutoffs (FR-007/015).
  • B-303: Provider adapter, attempt state machine and unknown-outcome recovery (FR-009).
  • B-304: Policy-constrained fallback and failure notifications (FR-008).

Workstream 4 — Financial integrity​

  • B-401: Balanced immutable ledger and accounting event keys (FR-010).
  • B-402: Settlement ingestion, reconciliation and exception workbench (FR-011/018).
  • B-403: Eligible payout reservation, aggregation and return handling (FR-012).
  • B-404: Refund, dispute, reserve and chargeback workflows (FR-013).
  • B-405: Effective-dated merchant pricing, fee assessment and invoicing (FR-017).

Workstream 5 — Pilot readiness​

  • B-501: End-to-end sandbox and fault-injection tests.
  • B-502: Security review, penetration test and access review.
  • B-503: Operational runbooks, alerts, backup restore and incident rehearsal.
  • B-504: Partner and merchant certification; limited pilot approval.

Dependency rules​

Do not build production payout execution before ledger, settlement eligibility and reconciliation are tested. Do not initiate production collections before mandate evidence, partner authorisation and unknown-outcome controls exist. Do not use a successful UI demo as evidence of financial correctness.

Ticket template​

Include requirement ID, user story, scope/non-scope, API and data changes, permissions, failure cases, acceptance tests, telemetry, dependencies, owner and approval status.