Platform

One protocol across financial providers.

DataLink separates a reusable financial account connection from every permission to use it—keeping the product consistent while providers retain control.

How a connection works

Provider differences stop at the Financial Provider Adapter boundary. Partners use DataLink’s canonical models and never need to understand a bank’s native API.

1

Request

An approved institution identifies itself, the purpose, exact scopes and duration.

2

Authorize

The customer continues to their bank or wallet, authenticates and makes the final decision.

3

Connect

DataLink establishes a stable verified connection without collecting financial credentials.

4

Access

Only information covered by the active permission is retrieved, normalized and audited.

Connection lifecycle

Pending verification→Action required→Verified→Reconnect

Connections retain a stable identity through reverification and reconnection where appropriate. Disconnecting stops future use while preserving required audit evidence.

Canonical capabilities

account.identity

Verify the account holder and account identity.

transactions.read

Retrieve transaction history for an approved period.

income.summary

Return a deterministic recurring-income summary.

cashflow.summary

Return documented cash-flow indicators.