Complete Tink Link initialization with the transactions:read scope and obtain a Tink user access token via the authorization code exchange flow
Fetch raw transactions from the Tink Transactions API; the response includes a categories field with Tink's taxonomy code and a merchant object with enriched merchant name, MCC, and logo URL when available
Subscribe to the transaction:updated webhook event to receive enrichment updates asynchronously — Tink may enrich a transaction after initial fetch as its enrichment pipeline processes the data
Map Tink's category taxonomy to your own PFM category hierarchy; store the mapping table versioned so future taxonomy changes can be re-applied to historical data
For transactions where merchant enrichment is absent (common for P2P payments and bank fees), implement a fallback rule set based on transaction description pattern matching
Aggregate categorized transaction data by time period to compute budget and spending trend metrics; use Tink's account balance history endpoint to validate that your transaction aggregation matches the account's reported balance
Known gotchas
Tink enrichment quality varies significantly by market; UK and Nordic markets have higher enrichment coverage than newer markets — do not assume uniform merchant data availability across all connected markets
Tink's category taxonomy versions are market-specific; a category code valid in Sweden may not exist in the UK taxonomy — always scope your category mapping table by market
Tink transaction IDs are stable within a connection but may be regenerated if the user re-authenticates and Tink re-imports transactions; implement a deduplication strategy using transaction date, amount, and description rather than relying solely on Tink transaction ID
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp