Release 4.0

2026-05-22

Summary of changes

Area	What changed
Overall structure	The Knowledge Hub was heavily reorganised into clearer product areas: Platform Overview, Treasury, Payments, Administration, Vitesse Online Guide and API Guide.
Product positioning	Content now presents Vitesse primarily as a “treasury and payments platform” with stronger insurance workflow context (insurers, MGAs, TPAs, brokers, delegated authority).
Treasury model	Major expansion of treasury concepts including prefunded model, funding accounts, payment accounts, fund pooling, and risk sharing.
Payments	Payment concepts were rewritten around “payment flows” (Transactions, Smart Payments, Payee Choice, Vendor Pay) instead of older operational groupings.
Payment coverage	Country/currency coverage was restructured into “Payment coverage by hub” with separate UK Hub and US Hub sections.
Structured data	Addressing and payment validation guidance was modernised around ISO 20022 structured addresses and clearer bank-code requirements.
Administration	User/account administration was split into clearer topics: Users, Roles, Account Access, SSO, Passwords, Identity Clients, and delegated access models.
Delegated access	Significant new detail added around Service relationships, partner accounts, entity structures, and delegated operations.
Insights & dashboards	New operational dashboards were introduced, including Portfolio Overview, Account Health, runway analysis, Top TPA metrics, and treasury insights visualisations.
Payment lifecycle	Lifecycle/state documentation was expanded substantially, separating payment request lifecycle, transaction lifecycle, cheque lifecycle, and processing phases.
Cheques	Cheque documentation became much more detailed, including MFA for eChecks, Positive Pay controls, lifecycle states, branding, and void workflows.
Batch processing	Batch file guidance was rewritten into more structured transaction, recipient, account, and originator field models.
API documentation	API docs were reorganised, and archived legacy content.
API reference	Top level tidy-up. Better structured and organised.
Legacy content	Several older operational topics were either removed, archived, or folded into broader concepts rather than maintained as standalone pages.
Naming consistency	Many topics were renamed for consistency and clarity.
User guidance	The tone shifted from reference-style documentation to more workflow-led guidance with examples, use cases, and operational explanations.
Governance & controls	Stronger emphasis on approvals, separation of duties, payment limits, delegated authority, and auditability throughout the platform.
Customer experience	Recipient-facing journeys were expanded considerably, especially around Getting Started.