Overview
Give trusted consumers a contextual finance view through ContextResolver while publishing canonical finance and change events.
Problem
Other applications need current financial context and change signals without copying PayStream-owned state.
Solution
Resolve PayStream EntityRefs, relationships, timelines, permissions, presentation and available actions, then publish canonical finance events and velaxe.context.changed invalidations as records change.
How it works
Authorize the context consumer, resolve the required finance entity, retrieve relationships and timeline, execute permitted actions through PayStreamRuntime, and subscribe to canonical business or context-change events.
Who is this for
Integration Engineer
Operations Administrator
Expected outcomes
- Source-authoritative finance context
- Canonical change events for connected workflows
Key metrics
Security impact
- Finance EntityRefs, relationships, timeline entries, presentation metadata, permissions, available actions, event records, and change-subscription state · PII: depends on the finance entity and relationships resolved
Compliance
- Workspace permissions, trusted execution, resource authorization, Core secrets, finance audit, and app-scoped grants.
Availability & next steps
Enterprise