M5-11 Credits/Vouchers Mechanism for Verification¶
Milestone: M5 — Disclosure and Verification
SOW Reference: NFR5 (and referenced in the M5/M6 milestone description in Appendix 2)
Requirement Clarity: ⚠️ Blocking — mechanism not specified in the SOW. The original v3 requirements doc (Appendix 1, "Run Presentation Verification if requested") describes a specific mechanism: use credits from either the Relying Party's account or the platform's pooled credits (available for up to 12 months to encourage adoption); call the Registrar to transfer credits to the Velocity Network treasury, receiving a voucher; use that voucher to call the Credential Agent for verification. The SOW's Appendix 1 (FR3) doesn't mention credits or vouchers at all — it only appears as a bare line item in the Appendix 2 milestone description. Get the mechanism re-confirmed and written down before building it.
Dev Status: ❌ Not started — payment.module.ts is an empty stub with no controllers/providers
Overview¶
Implement the credit/voucher mechanism that pays for verification calls to the Credential Agent, per the original design: platform-pooled credits (time-limited) or organisation-purchased credits, exchanged for a Velocity Network voucher via the Registrar.
Backend Tasks¶
- Confirm the mechanism still matches the original v3 doc's design, or get an updated spec
- Implement credit balance tracking per organisation (and a platform-wide pool)
- Implement the Registrar credit-transfer-for-voucher call
- Use the voucher when calling the Credential Agent for verification (M5-08)
Frontend Tasks¶
- Show credit balance to org admins
- Handle the "out of credits" case gracefully in the verification flow
Dependencies¶
- M5-08 verification integration — verification calls consume credits.
- M1-01 requirements sign-off — this is one of the named items to resolve early.
- M5-14 general payment/invoicing capability — a distinct NFR5 requirement; do not conflate the two when scoping the
paymentmodule.
Acceptance Criteria¶
Not currently defined in SOW Appendix 3 — needs to be written once the mechanism is confirmed.
Existing Reference Material¶
- Original v3 High-Level Requirements doc, Appendix 1, "Run Presentation Verification if requested" (not present in this repo — held by Curo/NeuralRays as the RFP-era document)