NetDania: market-data APIs, charts, NetStation and broker-interface technology

NetDania supplies market-data, visualisation and trading-interface technology to financial institutions, alongside a public-facing financial-information site. The current institutional presentation sits in United Fintech’s Capital Markets division. This profile concerns NetDania’s own products, not all the products belonging to other companies in the wider group.[10]

A brokerage can purchase one layer without replacing every other system. For example, a new client chart may use an existing price source, while a new data infrastructure project may leave the client interface unchanged. A sound specification identifies the component being replaced and the downstream decisions that depend on it.

The feed module describes normalised, timestamped multi-asset data, including FX, equities, commodities, crypto, fixed income and money markets. It also lists FX-options volatility surfaces. REST and WebSocket access are described alongside FIX and other streaming connectivity. The catalogue includes both delayed and live exchange prices, so real-time status must be checked instrument by instrument.[6]

Displaying an exchange price, an OTC indicative rate and a broker’s executable quote in the same layout can obscure a material difference. The application should preserve source, delay and unit information. A data-feed integration can be technically successful even when its symbol mapping or commercial use is wrong.

No current public all-inclusive enterprise cash tariff was established for the researched package. NetDania’s disclosure describes broker/institutional white-label use under software subscription contracts. A public app or information page should not be used as the price or licence for a bank’s or broker’s enterprise deployment.[1]

For a public brokerage website, the important distinction is often internal use versus display to external users. Request explicit rights for display, non-display analytics, derived calculations and onward redistribution as relevant. A subscription fee alone does not tell the customer which of those uses has been licensed.

The hosting module describes private, hybrid and fully managed cloud deployments, with load balancing, failover, redundancy and monitoring. It also describes entitlement, lineage, encryption and audit controls. Those are vendor-stated capabilities; the public page did not provide an independently inspected certification report or customer-specific availability commitment.[5]

A staged implementation should first reconcile a known instrument set between the source and destination. Check price scale, currency, timestamp, timezone, historical adjustments and session boundaries. Then test interruptions and restoration. That separates content errors from distribution errors before adding a larger instrument universe.

The trading-technology layer should be tested with the selected broker backend. A white-label interface is not automatically a replacement for risk, account and payment systems. A migration needs to preserve customer account identity and the authoritative record of orders, trades and balances.[4]

The public support form asks for a product as well as a subject. A broker should use a contracted production escalation route for a live incident rather than assume a general consumer form has the necessary priority. No public response-time guarantee was established from that form.[8]

For data incidents, keep the source, symbol, field, timestamp, received value and expected value together. A screenshot alone may not identify which feed produced the number. The provider and broker need enough evidence to distinguish stale data, a normalised-field issue, incorrect mapping and a genuine source-market change.

NetDania’s public-site disclaimer describes it as a technology supplier and says users of its broker integrations must already be customers of a supported broker. It also says website prices may come from OTC sources or market makers and may be indicative rather than suitable for trading decisions. These public-site limitations should not be mistaken for a specification of every contracted institutional feed.[1]

No custody, brokerage or investment-management permission is inferred from the NetDania interface. The institution serving the end customer must be identified separately. Likewise, an external content partnership does not by itself grant a buyer permission to redistribute that partner’s material.

NetDania’s published legal material identifies NetDania Creations ApS and CVR 27976670 among the group entities. The footer lists Holmens Kanal 7, Copenhagen, while a privacy section retains a different address and phone. Use the signed agreement and current supplier confirmation for legal notices rather than silently treating every historic contact block as current.[9]

United Fintech’s Capital Markets site places NetDania alongside other operating businesses. The shared navigation can expose products from those other firms; that is not sufficient evidence that NetDania itself supplies all of them. This profile keeps the scope on the pages specifically attributed to NetDania.[10]

Operator

NetDania Creations ApS and relevant NetDania group contracting entity; confirm in the agreement

Service scope

NetDania spans market-data distribution, charting, terminals and trading interfaces. The profile distinguishes public-site content from enterprise licences and explains integration, hosting, support and supplier-identity boundaries.

Customer types

Banks and brokers; FX and market-data firms; Financial application and analytics teams

Delivery

Hosted; API; Hybrid; Managed service

Pricing publication

Quote only

Platforms

NetStation; Financial charts and components; Market Data Solutions

Implementation

Product-specific feed, component or interface integration; private, hybrid and managed hosting are described.

Support

Public product support form and institutional enquiry routes; production response obligations require the customer contract.

Permissions and regulatory scope

Technology provider, not the customer’s broker or custodian. Data display and redistribution require appropriate permissions.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10

NetStation’s named content relationships include MT Newswires, Trading Central and FXStreet. The service combines news and analytics with charting, data and the ability to use a client’s own data sources. The licence should specify which of those components is actually included.[7]

For a long-term data project, record the export and replacement requirements at the start. Historical series, watchlists, layouts, symbol mappings and audit records may have different portability rights. A future vendor change should not depend on a user manually copying values from a screen.