Flinks vs GoCardless Bank Account Data

Flinks

Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.

GoCardless Bank Account Data

UK plus every PSD2 country, up to 24 months of history, one API shape for all of them. No public price and no confirmed free plan.

Flinks

1. Call /GenerateAuthorizeToken with the secret key in flinks-auth-key, then pass the returned token to the Connect iframe or to /Authorize. The token is single-use and expires after 15 minutes.
2. Send the account holder through Flinks Connect in a browser. The API alone cannot complete a first bank login, and sandbox iframes need demo=true.
3. Store the loginId. Call /Authorize with it and MostRecentCached: true for a new requestId each session, because /GetAccountsDetail consumes the requestId.
4. On a 202 from /GetAccountsDetail, poll /GetAccountsDetailAsync every 10 seconds for at most 30 minutes, or ask support to enable webhooks.
5. Route each end user to the instance for their country. A loginId from the Canadian instance is not valid on the US one.

GoCardless Bank Account Data

1. Cache the access token for its 24 hours and use /api/v2/token/refresh/ rather than minting a new pair each run
2. Create the end user agreement before the requisition when you need other than 90 days of history or access
3. Read the per-account rate limit headers; on 429 wait for the account reset time, since some banks allow 4 calls a day
4. Poll /api/v2/accounts/{id}/ until status is READY before asking for transactions
5. Call the REST endpoints directly; the Nordigen SDKs still install but get no fixes