GoCardless Bank Account Data vs Yapily

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.

Yapily

llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.

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

Yapily

1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch
2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty
3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation
4. Check the error source field first; USER and INSTITUTION failures won't clear on retry
5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days