Match a fintech product's pricing requirements to its actual display, valuation and storage workflows.
An indicative dashboard, portfolio valuation and trading application need different freshness and field guarantees. Define the use case and explain stale or unavailable values in the interface instead of presenting every quote as a live executable price.
Confirm display rights, retention and redistribution scope for the selected sources. Plan API caching and request limits around the product's traffic pattern, and avoid retaining history beyond the agreed dataset permissions.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Instrument scope | Identify the exact underlying, source identifier, quote currency and intended use. |
|---|---|
| Consumer workflow | List trading platforms, charts, risk tools and applications that need the output. |
| Delivery contract | Agree protocol, quote fields, timestamps, source status and recovery behaviour. |
| Production review | Confirm source rights, integration ownership, test evidence and commercial scope. |
For your instrument universe, define who consumes the prices and what each system needs to reconstruct a usable quote. An application dashboard, broker platform and historical process can require different delivery rules even when they share one normalized instrument model.