# Phase 14 Execution Checklist (Admin and Merchant Expansion) Reference artifacts: - docs/business-requirement-gap-analysis.md - docs/gap-closure-implementation-plan.md - docs/phase-14-sprint-task-breakdown.md - docs/phase-13-execution-checklist.md - docs/phase-13-sprint-task-breakdown.md - docs/wallet-implementation-plan-apps-mode.md - docs/phase-tracker.md - docs/domain-map.md - docs/adr/0005-api-error-and-idempotency-response-contract.md - docs/adr/0006-security-and-key-management-baseline.md - docs/adr/0007-observability-and-audit-traceability-standard.md - docs/adr/0011-compliance-and-data-governance-controls.md ## 1. Phase Objective Complete back-office operational capabilities and unlock merchant/remittance growth channels by delivering advanced admin controls, merchant acquiring workflows, and inward remittance end-to-end processing. Phase status target: - Start: not-started - End: done when all Phase 14 tracks are implemented, validated, and approved by Product, Security, Compliance, and Operations. Current phase status: not-started (2026-03-26) - planned in gap-closure roadmap; implementation not started. ## 2. Scope In scope: - Admin portal completion: wallet PIN reset, wallet suspend/close, advanced filters, report builder, dynamic rule controls. - Admin transaction and customer operations hardening with richer audit trails. - Merchant onboarding lifecycle and merchant profile/risk/compliance checks. - Merchant acceptance channels: POS/SoftPOS/QR payment orchestration baseline. - Wallet as payment option at merchant points (API/SDK contract baseline). - Inward remittance ingestion and wallet credit workflows. - Remittance metadata model (sender, country, amount, channel reference). - Remittance notifications and receipt generation. - Security policy, observability, reconciliation hooks, and runbook readiness for all new flows. Out of scope: - Lending product engine and underwriting flows (Phase 15). - Investment provider integrations (Phase 15). - Full VAS features (Phase 15). ## 3. Work Breakdown ## Track A: Admin Portal Completion and Control Maturity 1. Implement admin wallet PIN reset and wallet suspend/close controls. - Owner: Wallet Web Team + Security Team - Output: privileged admin actions with policy, approval checks, and full audit timeline. - Status: pending - Evidence: policy tests and audit trace report. 2. Implement advanced transaction inquiry filters. - Owner: Wallet Web Team + Operations Team - Output: filters for date range, amount range, corridor, and service type. - Status: pending - Evidence: query correctness tests and UI regression report. 3. Implement custom report builder with export formats. - Owner: Reporting Team + Wallet Web Team - Output: admin-configurable report builder with CSV/Excel/PDF exports. - Status: pending - Evidence: report builder tests and export validation. 4. Implement dynamic rules/risk configuration controls. - Owner: Risk Team + Wallet Web Team - Output: admin UI to configure usage controls and risk rules with versioned changes. - Status: pending - Evidence: rule versioning tests and policy conformance report. ## Track B: Merchant Onboarding and Acquisition 1. Implement merchant domain model and onboarding lifecycle. - Owner: Merchant Team + Compliance Team - Output: merchant registration, verification, approval, rejection, suspension states. - Status: pending - Evidence: lifecycle matrix and workflow tests. 2. Implement merchant KYC/KYB and risk checks integration. - Owner: Compliance Team + Risk Team - Output: onboarding risk and compliance checks with case escalation support. - Status: pending - Evidence: compliance/risk integration report. 3. Implement admin merchant operations console. - Owner: Wallet Web Team + Operations Team - Output: merchant search, profile review, approval/decline actions, and status tracking. - Status: pending - Evidence: admin UX tests and policy validation. 4. Implement merchant settlement visibility baseline. - Owner: Settlement Team + Merchant Team - Output: merchant settlement status and exception visibility for operations. - Status: pending - Evidence: settlement visibility report and tests. ## Track C: Merchant Acceptance Channels (POS/SoftPOS/QR) 1. Implement POS/SoftPOS/e-com transaction orchestration baseline. - Owner: Merchant Team + Integrations Team - Output: merchant acceptance flow with authorization, capture/settle statuses. - Status: pending - Evidence: orchestration lifecycle tests. 2. Implement QR merchant payment flow. - Owner: Wallet Web Team + Merchant Team - Output: customer scan/pay and merchant receive/confirm workflows. - Status: pending - Evidence: E2E QR payment test report. 3. Implement wallet-as-payment-option contract (API/SDK baseline). - Owner: API Contracts Team + Merchant Team - Output: partner-facing API/SDK contract for merchant-side wallet payments. - Status: pending - Evidence: contract tests and developer integration guide. 4. Implement acceptance channel observability and reconciliation hooks. - Owner: Observability Team + Settlement Team - Output: metrics and traces across auth/capture/settle/failure paths. - Status: pending - Evidence: traceability and reconciliation report. ## Track D: Inward Remittance Channel 1. Implement inward remittance ingestion adapters. - Owner: Integrations Team + Finance Team - Output: inbound remittance intake from supported rails/providers. - Status: pending - Evidence: adapter contract tests and ingestion simulation report. 2. Implement remittance metadata model and persistence. - Owner: Remittance Team + Wallet Database Team - Output: sender, country, amount, corridor, reference, and status persistence model. - Status: pending - Evidence: schema/migration tests and data model validation. 3. Implement wallet crediting pipeline for remittance receipts. - Owner: Ledger Team + Integrations Team - Output: idempotent credit posting and exception handling for inbound remittance. - Status: pending - Evidence: posting integrity tests and duplicate-ingestion report. 4. Implement remittance customer notifications and receipts. - Owner: Notifications Team + Wallet Web Team - Output: customer alerts and downloadable/visible remittance receipt details. - Status: pending - Evidence: delivery/receipt tests and content validation. ## Track E: Security, Policy, and Compliance Hardening 1. Validate privileged action controls for admin and merchant operations. - Owner: Security Team - Output: ABAC and MFA checks for sensitive admin and merchant controls. - Status: pending - Evidence: security test report. 2. Validate data governance controls for merchant/remittance entities. - Owner: Compliance Team + Database Team - Output: PII tagging, retention, and access controls for all new schemas. - Status: pending - Evidence: governance checklist and approval notes. 3. Validate audit trail completeness for regulated operations. - Owner: Observability Team + Compliance Team - Output: complete actor/action/resource/outcome traces. - Status: pending - Evidence: audit coverage report. 4. Validate API envelope and idempotency conformance. - Owner: Platform Team - Output: contract and retry-safe behavior compliance for new endpoints. - Status: pending - Evidence: conformance report. ## Track F: Operational Readiness and Go-Live Evidence 1. Produce runbooks for admin, merchant, and remittance incidents. - Owner: Operations Team + SRE Team - Output: runbooks for failed merchant onboarding, payment disputes, and remittance credit failures. - Status: pending - Evidence: runbook package and walkthrough notes. 2. Execute tabletop exercises for merchant and remittance failures. - Owner: Operations Team + Security Team - Output: incident simulation, response validation, and action-item register. - Status: pending - Evidence: tabletop report and corrective actions. 3. Validate support readiness and escalation pathways. - Owner: Operations Team + Program Management - Output: L1/L2/L3 escalation model and handoff procedures. - Status: pending - Evidence: support readiness checklist. 4. Compile Phase 14 sign-off package. - Owner: Program Management + Track Leads - Output: consolidated evidence package with approvals. - Status: pending - Evidence: signed phase summary and governance notes. ## 4. Deliverables 1. Fully expanded admin portal operational controls and report builder. pending 2. Merchant onboarding and administration workflows. pending 3. POS/SoftPOS/QR acceptance channel baseline plus wallet payment contract. pending 4. Inward remittance ingestion, wallet crediting, and receipt/notification flows. pending 5. Phase 14 security/compliance/operations evidence package. pending ## 5. Entry and Exit Criteria Entry criteria: - Phase 13 compliance/reporting and notification baselines stable. pending - Merchant and remittance partner integration preconditions available. pending - Security and compliance policy baselines from previous phases available. MET Exit criteria: 1. Admin completion features are live and policy-protected. pending 2. Merchant onboarding and acceptance channels are operationally validated. pending 3. Inward remittance workflows pass end-to-end and reconciliation checks. pending 4. Security/compliance/audit requirements are satisfied for new domains. pending 5. Phase 15 dependencies are unblocked with signed evidence package. pending ## 6. Risks and Mitigations 1. Risk: Merchant onboarding complexity delays approval throughput. - Mitigation: staged onboarding states, automation for document checks, and clear exception queues. - Status: open 2. Risk: QR/POS acceptance failures impact merchant trust. - Mitigation: deterministic retry flows, real-time status feedback, and fallback options. - Status: open 3. Risk: Inward remittance duplicates or mapping errors cause incorrect credits. - Mitigation: strict idempotency keys, pre-credit validation, and exception reconciliation workflows. - Status: open 4. Risk: Expanded admin powers increase security exposure. - Mitigation: ABAC+MFA controls, dual-approval for high-risk actions, and detailed audit monitoring. - Status: open 5. Risk: Support teams are not ready for merchant/remittance incident volume. - Mitigation: runbooks, tabletop drills, and escalation simulation before rollout. - Status: open ## 7. Suggested Sprint Plan (3 Sprints) Sprint A: - Admin completion controls and advanced filters baseline. - Merchant lifecycle model and onboarding baseline. - Remittance adapter contract and metadata schema setup. Sprint B: - Merchant console and acceptance channel core flows. - Remittance credit pipeline and notification/receipt baseline. - Dynamic rules/report builder and compliance hardening. Sprint C: - Acceptance and remittance E2E closure with reconciliation hooks. - Security/compliance/operational hardening and evidence collection. - Phase sign-off package and governance approval. ## 8. Evidence Checklist - [ ] Admin PIN reset/suspend/close control validation report. - [ ] Advanced filter correctness and regression report. - [ ] Custom report builder export validation report. - [ ] Merchant onboarding lifecycle and compliance/risk report. - [ ] Merchant acceptance (POS/SoftPOS/QR) E2E and reconciliation report. - [ ] Wallet payment API/SDK contract conformance report. - [ ] Inward remittance ingestion/crediting integrity report. - [ ] Remittance receipt and notification delivery report. - [ ] Security policy and audit traceability report. - [ ] Data governance and retention compliance report. - [ ] Runbook/tabletop/support readiness evidence. - [ ] Phase 14 sign-off note with owner approvals. ## 9. Deferred Backlog (Explicit TODO) 1. Lending engine and underwriting features remain in Phase 15. 2. Investment provider integrations remain in Phase 15. 3. VAS feature suites remain in Phase 15.