Skip to content

M5-14 General Payment / Invoicing Capability

Milestone: M5 — Disclosure and Verification SOW Reference: NFR5 Requirement Clarity: 🟡 This is a distinct requirement from M5-11 and should not be conflated with it. NFR5 says: "we will need to include the ability of the platform to take and process payments... the partner should plan for and include this mechanism within the estimated effort, however for the MVP if manual processing is sufficient, this can be deferred." This is about the platform being able to charge Staffing Companies for using the service generally (e.g. subscription fees) — separate from [M5-11]'s specific mechanism for paying Velocity Network for verification API calls. Confirm with Curo whether manual/offline invoicing is acceptable for MVP (in which case this task may require little or no platform development) or whether in-platform payment processing (e.g. Stripe) is expected now. Dev Status: ❌ Not started — payment.module.ts is an empty stub; unclear whether it's meant to cover this requirement, M5-11's mechanism, or both

Overview

Determine and, if needed, build the platform's capability to take payment for its services from Staffing Companies, distinct from the Velocity-specific credits/vouchers mechanism in M5-11.

Tasks

  • Confirm with Curo: is manual/offline invoicing (outside the platform) acceptable for MVP?
  • If yes: no platform development needed for this item — document that decision
  • If no: scope and build in-platform payment processing (e.g. Stripe integration)

Dependencies

Acceptance Criteria

Not explicitly defined in Appendix 3 — depends on the MVP-scope confirmation above.

Existing Reference Material

None — this requirement isn't reflected in any existing implementation doc.

Blockers & Risks

  • Needs decision: whether this requires any MVP development at all.