BitPay added named workstream tagging to the cabinet today. Each card in a program can now be tagged with a workstream identifier - a project name, a team label, a budget code, or any other grouping that maps to the operator's accounting structure.
The cabinet surfaces per-workstream spending breakdowns. Operators running 20 cards across 5 projects can see at a glance: this workstream spent $4,200 last week with 0 disputes; that workstream spent $1,800 with 1 dispute; the other workstream is mostly frozen pending review. The view is built into the cabinet without any third-party reporting tool.
API endpoints added for workstream management. GET /api/workstreams returns all workstreams for the account with aggregate spending. POST /api/workstreams creates a new workstream. PATCH /api/workstreams/:id updates metadata or retires a workstream. Cards can be assigned to workstreams on creation or moved between them via PATCH.
Operators running custom dashboards or downstream reporting tools get clean workstream-level data via the API. The workstream field is searchable, filterable, and exportable - making reconciliation against internal accounting systems straightforward.
