# Phase 14 Sprint Task Breakdown (App-Level Task IDs)

**Date:** 2026-03-26  
**Phase:** 14 - Admin and Merchant Expansion  
**Source Checklist:** docs/phase-14-execution-checklist.md

---

## 1. Planning Assumptions

- Sprint length: 2 weeks
- Phase length: 3 sprints (A, B, C)
- Status values: `not-started`, `in-progress`, `blocked`, `done`
- Priority values: `P0` (critical path), `P1` (important), `P2` (optimization)
- Every P0 task requires policy/security/audit evidence and operational readiness artifacts.

---

## 2. Task ID Scheme

Format:
- `P14-SA-<track><nn>` for Sprint A
- `P14-SB-<track><nn>` for Sprint B
- `P14-SC-<track><nn>` for Sprint C

Track letters:
- `A` Admin completion
- `B` Merchant onboarding and operations
- `C` Merchant acceptance channels
- `D` Inward remittance
- `E` Security/compliance hardening
- `F` Operational readiness and sign-off

---

## 3. Sprint A Tasks (Foundations)

## Track A - Admin Completion

### P14-SA-A01
- Title: Admin wallet PIN reset and suspend/close command set
- Apps: wallet_auth, wallet_accounts, wallet_web
- Priority: P0
- Owner: Wallet Web Team + Security Team
- Dependencies: none
- Acceptance criteria:
  - Admin commands for PIN reset and wallet suspend/close implemented.
  - ABAC and MFA controls enforce privileged access.
  - Audit events emitted for each action.
- Evidence: command/policy tests and audit samples
- Status: not-started

### P14-SA-A02
- Title: Advanced transaction inquiry filters baseline
- Apps: wallet_web, wallet_ledger
- Priority: P1
- Owner: Wallet Web Team + Operations Team
- Dependencies: none
- Acceptance criteria:
  - Date/amount/corridor/service filters available in admin inquiry.
  - Query performance remains within defined SLO target.
  - Regression tests pass.
- Evidence: filter tests and performance report
- Status: not-started

## Track B - Merchant Onboarding

### P14-SA-B01
- Title: Merchant lifecycle model and storage
- Apps: wallet_merchant, wallet_database
- Priority: P0
- Owner: Merchant Team + Compliance Team
- Dependencies: none
- Acceptance criteria:
  - Merchant states defined (draft/pending/approved/rejected/suspended).
  - Persistence and transition guards implemented.
  - Lifecycle tests pass.
- Evidence: lifecycle matrix and test report
- Status: not-started

### P14-SA-B02
- Title: Merchant compliance and risk integration baseline
- Apps: wallet_merchant, wallet_compliance, wallet_risk
- Priority: P0
- Owner: Compliance Team + Risk Team
- Dependencies: P14-SA-B01
- Acceptance criteria:
  - Onboarding checks trigger compliance and risk evaluations.
  - Escalation path available for exceptions.
  - Integration tests pass.
- Evidence: integration report and escalation tests
- Status: not-started

## Track D - Inward Remittance

### P14-SA-D01
- Title: Inward remittance adapter contracts and stubs
- Apps: wallet_integrations, wallet_api_contracts
- Priority: P0
- Owner: Integrations Team + Finance Team
- Dependencies: none
- Acceptance criteria:
  - Inbound remittance contracts documented and versioned.
  - Provider stub adapters implemented with callback verification.
  - Contract tests pass.
- Evidence: contract test report
- Status: not-started

### P14-SA-D02
- Title: Remittance metadata schema and persistence
- Apps: wallet_database, wallet_integrations
- Priority: P0
- Owner: Remittance Team + Database Team
- Dependencies: P14-SA-D01
- Acceptance criteria:
  - Schema stores sender/country/amount/reference/status metadata.
  - Migrations and validations pass.
  - Data governance tags applied.
- Evidence: migration tests and governance checklist
- Status: not-started

## Track E - Cross-Cutting

### P14-SA-E01
- Title: Phase 14 policy and contract baseline
- Apps: wallet_auth, wallet_api_contracts, wallet_web
- Priority: P1
- Owner: Security Team + Platform Team
- Dependencies: P14-SA-A01, P14-SA-B01, P14-SA-D01
- Acceptance criteria:
  - New privileged actions mapped in policy matrix.
  - API envelope/idempotency conformance tests are green.
- Evidence: security and conformance report
- Status: not-started

---

## 4. Sprint B Tasks (Core Capability Delivery)

## Track A - Admin Completion

### P14-SB-A01
- Title: Custom report builder and export engine
- Apps: wallet_web, wallet_reporting
- Priority: P0
- Owner: Reporting Team + Wallet Web Team
- Dependencies: P14-SA-A02
- Acceptance criteria:
  - Admin-configurable report builder supports CSV/Excel/PDF exports.
  - Export requests are audited and status-tracked.
  - Functional tests pass.
- Evidence: report builder and export tests
- Status: not-started

### P14-SB-A02
- Title: Dynamic rules/risk configuration UI
- Apps: wallet_web, wallet_limits_fees, wallet_risk
- Priority: P1
- Owner: Risk Team + Wallet Web Team
- Dependencies: P14-SA-A01
- Acceptance criteria:
  - Admin can create/update versioned usage and risk rules.
  - Change history and rollback path available.
  - Policy validation tests pass.
- Evidence: rule versioning tests
- Status: not-started

## Track B - Merchant Onboarding and Ops

### P14-SB-B01
- Title: Merchant admin operations console
- Apps: wallet_web, wallet_merchant
- Priority: P0
- Owner: Wallet Web Team + Operations Team
- Dependencies: P14-SA-B01, P14-SA-B02
- Acceptance criteria:
  - Merchant search, review, approve/decline/suspend actions available.
  - Actions are policy-protected and audited.
  - Admin workflow tests pass.
- Evidence: admin workflow report
- Status: not-started

### P14-SB-B02
- Title: Merchant settlement visibility baseline
- Apps: wallet_merchant, wallet_settlement, wallet_web
- Priority: P1
- Owner: Settlement Team + Merchant Team
- Dependencies: P14-SB-B01
- Acceptance criteria:
  - Merchant settlement statuses and exceptions view available.
  - Reconciliation hooks included.
  - Visibility tests pass.
- Evidence: settlement visibility report
- Status: not-started

## Track C - Merchant Acceptance Channels

### P14-SB-C01
- Title: POS/SoftPOS authorization and capture orchestration
- Apps: wallet_merchant, wallet_integrations, wallet_ledger
- Priority: P0
- Owner: Merchant Team + Integrations Team
- Dependencies: P14-SA-B01
- Acceptance criteria:
  - Authorization/capture/settle lifecycle implemented.
  - Failure and retry semantics validated.
  - Ledger invariants maintained.
- Evidence: lifecycle and invariant test report
- Status: not-started

### P14-SB-C02
- Title: Merchant QR payment customer flow
- Apps: wallet_web, wallet_merchant, wallet_transfers
- Priority: P0
- Owner: Wallet Web Team + Merchant Team
- Dependencies: P14-SB-C01
- Acceptance criteria:
  - Customer can scan and pay merchant QR.
  - Merchant receives payment confirmation status.
  - E2E tests pass for success/failure paths.
- Evidence: QR payment E2E report
- Status: not-started

### P14-SB-C03
- Title: Wallet payment API/SDK baseline
- Apps: wallet_api_contracts, wallet_merchant
- Priority: P1
- Owner: API Contracts Team + Merchant Team
- Dependencies: P14-SB-C01
- Acceptance criteria:
  - Partner API/SDK contract published with auth and error semantics.
  - Integration examples and contract tests available.
- Evidence: API contract test report and docs
- Status: not-started

## Track D - Inward Remittance

### P14-SB-D01
- Title: Remittance wallet-credit posting pipeline
- Apps: wallet_integrations, wallet_ledger, wallet_accounts
- Priority: P0
- Owner: Ledger Team + Integrations Team
- Dependencies: P14-SA-D02
- Acceptance criteria:
  - Inbound remittance credits post idempotently.
  - Duplicate/invalid events are safely rejected/escalated.
  - Financial integrity tests pass.
- Evidence: posting integrity and duplicate test report
- Status: not-started

### P14-SB-D02
- Title: Remittance notification and receipt baseline
- Apps: wallet_notifications, wallet_web, wallet_integrations
- Priority: P1
- Owner: Notifications Team + Wallet Web Team
- Dependencies: P14-SB-D01
- Acceptance criteria:
  - Customer receives remittance notifications by configured channels.
  - Receipt view includes sender/country/amount/reference.
  - Delivery and rendering tests pass.
- Evidence: notification/receipt report
- Status: not-started

---

## 5. Sprint C Tasks (Hardening and Sign-Off)

## Track C/D Completion

### P14-SC-C01
- Title: Merchant acceptance E2E closure and reconciliation hooks
- Apps: wallet_merchant, wallet_settlement, wallet_observability
- Priority: P0
- Owner: Merchant Team + Settlement Team
- Dependencies: P14-SB-C01, P14-SB-C02
- Acceptance criteria:
  - Full POS/SoftPOS/QR flow validated end-to-end.
  - Reconciliation variance hooks operational.
  - Monitoring and alert thresholds configured.
- Evidence: E2E and reconciliation report
- Status: not-started

### P14-SC-D01
- Title: Inward remittance E2E closure
- Apps: wallet_integrations, wallet_ledger, wallet_notifications, wallet_web
- Priority: P0
- Owner: Remittance Team + Integrations Team
- Dependencies: P14-SB-D01, P14-SB-D02
- Acceptance criteria:
  - End-to-end inward remittance flows pass success/failure/replay tests.
  - Customer receipts and notifications are reliable.
  - Exception handling and reconciliation are validated.
- Evidence: E2E and exception report
- Status: not-started

## Track A/B/E/F Sign-Off

### P14-SC-A01
- Title: Admin completion E2E and policy closure
- Apps: wallet_web, wallet_auth, wallet_reporting
- Priority: P0
- Owner: Wallet Web Team + Security Team
- Dependencies: P14-SB-A01, P14-SB-A02
- Acceptance criteria:
  - Admin controls and report builder flows validated end-to-end.
  - Policy and audit coverage complete for privileged actions.
- Evidence: E2E and policy report
- Status: not-started

### P14-SC-B01
- Title: Merchant onboarding and operations E2E closure
- Apps: wallet_merchant, wallet_web, wallet_compliance, wallet_risk
- Priority: P0
- Owner: Merchant Team + Compliance Team
- Dependencies: P14-SB-B01, P14-SB-B02
- Acceptance criteria:
  - Merchant onboarding to approval/suspension paths validated.
  - Risk/compliance escalations tested.
  - Operations handling validated.
- Evidence: E2E and escalation report
- Status: not-started

### P14-SC-E01
- Title: Security/compliance/audit conformance closure
- Apps: wallet_auth, wallet_compliance, wallet_observability, wallet_api_contracts
- Priority: P1
- Owner: Security Team + Compliance Team
- Dependencies: all P14-SC P0 tasks
- Acceptance criteria:
  - No unresolved critical security/compliance findings.
  - Audit and traceability matrix complete.
  - API conformance report finalized.
- Evidence: security/compliance report
- Status: not-started

### P14-SC-F01
- Title: Operations runbooks, tabletop, and support readiness
- Apps: docs, wallet_production
- Priority: P1
- Owner: Operations Team + SRE Team
- Dependencies: P14-SC-C01, P14-SC-D01, P14-SC-A01
- Acceptance criteria:
  - Runbooks published for merchant and remittance incidents.
  - Tabletop exercise completed with action items assigned.
  - Support escalation model approved.
- Evidence: runbook package and tabletop report
- Status: not-started

### P14-SC-F02
- Title: Phase 14 sign-off package
- Apps: docs
- Priority: P0
- Owner: Program Management + Track Leads
- Dependencies: P14-SC-A01, P14-SC-B01, P14-SC-C01, P14-SC-D01, P14-SC-E01, P14-SC-F01
- Acceptance criteria:
  - Phase 14 evidence checklist complete.
  - Open critical defects count is zero.
  - Sign-off from Product/Security/Compliance/Operations captured.
- Evidence: signed phase summary
- Status: not-started

---

## 6. Critical Path

1. P14-SA-A01 -> P14-SB-A01 -> P14-SC-A01
2. P14-SA-B01 -> P14-SA-B02 -> P14-SB-B01 -> P14-SC-B01
3. P14-SB-C01 -> P14-SB-C02 -> P14-SC-C01
4. P14-SA-D01 -> P14-SA-D02 -> P14-SB-D01 -> P14-SC-D01
5. P14-SC-A01 + P14-SC-B01 + P14-SC-C01 + P14-SC-D01 -> P14-SC-F02

---

## 7. Completion Gates Per Sprint

Sprint A gate:
- Must-complete tasks: P14-SA-A01, P14-SA-B01, P14-SA-B02, P14-SA-D01, P14-SA-D02
- Tolerance: maximum 1 P1 carryover

Sprint B gate:
- Must-complete tasks: P14-SB-A01, P14-SB-B01, P14-SB-C01, P14-SB-C02, P14-SB-D01
- Tolerance: no P0 carryover

Sprint C gate:
- Must-complete tasks: P14-SC-A01, P14-SC-B01, P14-SC-C01, P14-SC-D01, P14-SC-F02
- Tolerance: no open critical defects

---

## 8. Definition of Done (Phase 14)

A Phase 14 task is done only when:
- Implementation is complete and CI tests pass.
- Required security/compliance policy controls are validated.
- Audit and telemetry traces are captured for sensitive actions.
- Operations runbooks are updated for affected capabilities.
- Tracker artifacts include owner, status, and evidence references.