Head to head · Bank account data · October 2026 research run
GoCardless Bank Account Data vs Salt Edge Account Information
Salt Edge Account Information scores 58.2 (C) on agent readiness against GoCardless Bank Account Data's 50 (D), and leads in 4 of 7 scored categories. GoCardless Bank Account Data leads on reliability and security & auth. Both do bank account data.
Best open banking and bank data APIs for AI agents · All 120 bank data comparisons
Which one, for what
GoCardless Bank Account Data D
Best for Read-only account and transaction data across the UK and the EEA, for builders who don't need payments and can accept a contract.
Ahead on
- Reliability, 69 against 57
- Security & auth, 57 against 51
Watch for
No public price and no stated free allowance, though the API answers 402 past one
Salt Edge Account Information C
Best for Account data and payments in markets outside the UK, EEA and US.
Ahead on
- Schema & documentation, 77 against 58
- Agent ergonomics, 67 against 60
- Maintenance & community, 62 against 3
- Transparency & trust, 82 against 56
Also in its favour
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
Parallel sessions over the limit return HTTP 406 RateLimitExceeded, and per-second limits return 429 with no retry guidance
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Salt Edge Account Information +59
GoCardless Bank Account Data 3
No changelog and no dated API change found; the Endpoints reference page carries no date, and the last dated public change is the 7 April 2025 notice that the client libraries are no longer maintained (0). No releases or dated entries since 12 August (0). Closed service with no public changelog; support goes through GoCardless (3 of 15). Official SDKs unsupported since 7 April 2025 (0). The clones show nordigen-node's last tag v1.1.1 from 11 August 2022, nordigen-php's 1.1.3 from 7 April 2025 and nordigen-python untagged, each last changed on 7 April 2025 (0). 0 + 0 + 3 + 0 + 0 = 3.
Salt Edge Account Information 62
The docs changelog at docs.saltedge.com/v6/changelog/ has dated entries, newest 28 October 2026 (error_class and error_message on failed Payments), 8 days before this check (30). Entries on 19 August (VRP consent revoke endpoint), 22 September (partially_executed bulk payment status), 30 September (new transaction categories), 7 October (parallel session limits, documentation only, half) and 28 October fall in the 90 days from 7 August (20). Closed service with a public changelog and RSS feed, support through a project manager and a 24/7 incident reporting channel for clients (12 of 15). No official SDKs (0). No package to judge (0). 30+20+12+0+0 = 62.
Transparency & trust Salt Edge Account Information +26
GoCardless Bank Account Data 56
Closed service. The Bank Account Data Service Terms PDF linked from the merchant terms (file named January 2026, pages footed June 26) now opens and sets out the service, consent, the default limit of four retrievals in 24 hours and termination, under the General Terms (15 of 30, was 10). The account holders privacy notice, updated 28 July 2026, names GoCardless Ltd as controller but gives no retention periods or processors on the page, per the 1 October check, not re-read (10 of 30). The SDK end-of-maintenance notice is public but sets no sunset date, and there's no deprecation policy (5 of 20). No subprocessor list or data location statement found (0). Regulatory standing counts here as an addition to the checklist (+5 for a named regulator with a register number). GoCardless Ltd is FCA-registered under 597190, per the 30 September check (+5). 15 + 10 + 5 + 0 + 5 = 35.
Salt Edge Account Information 82
Closed service under General Terms of Service last revised 14 September 2023 (15). The privacy policy, last revised 14 September 2023, keeps log files at least five years after deletion from production servers and names its processors (20 of 30). The versioning section gives a 12-month window to move off a deprecated version, and the changelog carries dated notices, such as Payment Initiation API V5 deprecated on 2 January 2025 and deleted on 2 January 2026 (20). Processors named with countries, Hetzner in Germany and Finland, AWS in Ireland, SendGrid in the US and Yandex for analytics; EU and EEA data stays in the EU, other data may be accessed from Canada, the UK or Moldova (18 of 20). Regulatory standing counts here as an addition to the checklist (+5 for a named regulator with a register number, +3 for a named regulator alone). Salt Edge Limited is FCA-authorised under 822499 per the 30 September check; the pages we read name no EU authorisation (+5). 15+20+20+18+5 = 78.
Schema & documentation Salt Edge Account Information +19
GoCardless Bank Account Data 58
No machine-readable contract can be read. The Postman page in the docs now tells readers to import https://bankaccountdata.gocardless.com/api/swagger.json, but that host's robots.txt disallows every agent, and docs.gocardless.com/openapi-schema-public.json covers the payments API only (8 of 25, held partial). docs.gocardless.com/llms.txt lists nine Bank Account Data pages, with Markdown copies (10). The quickstart and output pages explain each step and field (12 of 20). A new Endpoints reference page lists all 19 operations with typed request bodies and query parameters, required markers and the access_scope values, though no ranges for the day limits (11 of 15, was 7). The statuses and error codes page and per-operation error lists give the summary, detail and status_code body and each cause by status, with request examples in the quickstart (12 of 15). Versioned by path (/api/v2) with no changelog found (5 of 15). 8 + 10 + 12 + 11 + 12 + 5 = 58.
Salt Edge Account Information 77
The quick start guides carry a Download Swagger JSON link to an OpenAPI 3.0.0 file covering the Account Information and Payment Initiation API v6, 34 paths and 39 operations with 73 schemas (25). docs.saltedge.com/llms.txt answers 404 (0). The API reference describes each endpoint and its parameters (14 of 20). Parameters are typed with ranges, such as per_page from 100 to 1,000 with a default of 100 (10 of 15, an earlier partial kept). Errors are grouped by layer (API, client configuration, provider, user) with error_class, HTTP code and description, and the quick starts carry examples (13 of 15). Version in the URL with a stated 12-month transition window, and a dated public changelog with an RSS feed, newest entry 28 October 2026 (15). 25+0+14+10+13+15 = 77.
Reliability GoCardless Bank Account Data +12
GoCardless Bank Account Data 69
GoCardless's status page at www.gocardless-status.com now runs on incident.io, with components for the API, payment pages, dashboard, payment processing, webhooks and partner apps, live and sandbox, and none for Bank Account Data (15, the reading for a vendor status page with no component for the product). Its published Atom feed, read on 5 November 2026, holds 11 entries from 13 August to 6 November, among them Bacs and payout delays, a dashboard SSO issue, email delivery to Yahoo and AOL, a Nationwide ARUDD-8 issue and three maintenance notices, and none touches Bank Account Data, Nordigen, account information or requisitions. The page has no component for this product and hasn't been shown to post an incident for it, so it isn't credited as a clean record for it; it scores 20, the value for a page not shown to post (re-read on 10 November, when the feed and the page's own incident list also cover 12 August). The 1 October reading of components and incidents came from the old Statuspage JSON endpoints and is replaced. A separate Pay By Bank institution page lists UK banks for payments, not this API. Every response carries rate limit headers with limit, remaining and reset, per client and per account, and the docs and the Service Terms say banks cap some accounts at 4 calls in 24 hours; the numbers live in headers more than in the docs (12 of 15, held). A 429 RateLimitError says how many seconds to wait and the docs say to wait for the account reset header; the API only reads, so retries don't double-write, with no idempotency keys (12). No SLA found (0). Generally available (10). 15 + 20 + 12 + 12 + 0 + 10 = 69.
Salt Edge Account Information 57
Status page at saltedgestatus.com with components for the Account Information API, Payments API and Partners API under Open Banking Gateway, among others (20). Its history.atom feed, read on 5 November, holds four incidents in the 90 days from 7 August. On 21 August a data centre network issue made every component unavailable from 09:27 to 09:37 UTC, marked critical, a full outage and so a major. The others were partial, a five-minute interruption for some customers on 29 September, a Revolut-side outage on 20 October and four minutes of degraded Payments API availability on 4 November. One major (10). Per-second limits are published for the reference endpoints, 10 a second on providers, countries, rates and categories and 5 on POST merchants and categories/learn, and since 7 October the docs give a default of 10 parallel Widget sessions (15). Requests over the per-second limits get 429 and parallel sessions over the limit get HTTP 406 RateLimitExceeded, with no Retry-After, backoff or idempotency guidance (2 of 15, an earlier partial kept). No SLA found (0). API v6 generally available (10). 20+10+15+2+0+10 = 57.
Agent ergonomics Salt Edge Account Information +7
GoCardless Bank Account Data 60
Responses are small JSON objects per account, split into balances, details and transactions, and transactions take date_from and date_to per the Endpoints page (15 of 25, was 12). End user agreements and requisitions list with limit and offset and next and previous links, institutions filter by country and by supported capabilities, and transactions by date range, but transactions, the largest response, have no page size or paging and no call selects fields. The line is partly met, so the earlier partial is held (10 of 20). Errors carry summary, detail and status_code, and the docs list each cause by status code and say to use the status for control flow (16 of 20, held). Read-only calls are safe to repeat; creating a requisition isn't idempotent (12 of 20). The agreement step is optional with 90-day defaults, but the official SDKs have been unsupported since April 2025 (7 of 15). 15 + 10 + 16 + 12 + 7 = 60.
Salt Edge Account Information 67
per_page from 100 to 1,000 and filters on account_id, from_date, to_date and pending let a call be sized (20 of 25). from_id cursors with next_id and a ready-made next_page URL (20). error_class and error_message on every error, but the rate limit comes back as 406 instead of 429, which most retry logic won't catch (14 of 20). Reads are safe to repeat; no idempotency guidance for payments (8 of 20). No official SDKs, only sample apps in Java, .NET, PHP, Python and Ruby, and Live calls need request signing (5 of 15).
Security & auth GoCardless Bank Account Data +6
GoCardless Bank Account Data 57
A secret_id and secret_key pair from the portal exchanges for a 24-hour access JWT and a 30-day refresh token, and the token endpoint can refuse addresses not on an allow-list (403 IP address not whitelisted); no scopes on the developer credential (20 of 30). The API can only read, and each end user agreement limits access_scope to balances, details or transactions and caps history and access days; requisitions can be deleted (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). Audit or request logs not found, as the portal disallows crawlers (0 of 15). gocardless.com/.well-known/security.txt names vuln-disc@gocardless.com and the security page but carries no Expires field. That page has a vulnerability disclosure policy routing reports to a public HackerOne bug bounty programme (gocardless_bbp) or email, with no acknowledgement time, and says GoCardless holds ISO 27001 certification across all its services and products from the British Assessment Bureau; no public advisories (15 of 20, was 8; the 1 October check missed the page). 20 + 15 + 7 + 0 + 15 = 57.
Salt Edge Account Information 51
App-id and Secret headers, and Live applications must also sign each call with a private key over Expires-at, method, URL and body, with Expires-at at most an hour ahead; the docs say to regenerate the key and update the public key after a breach. No scopes on the app credential (24 of 30). Consents carry scopes (holder_info, accounts, transactions) and period_days, PUT /consents/{id}/revoke ends one, and Test and Pending apps can't reach real banks (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). No operator request log found (0 of 15). The security page at /company/security says Salt Edge is ISO 27001 certified for developing, managing and providing financial IT services and PCI DSS compliant, runs internal and external penetration tests, and names SOC 2 among its standards. No certificate or report is linked, security.txt answers 404, and no disclosure policy, reporting address or bug bounty was found, so the line takes the value for certifications with no disclosure route (5 of 20). 24+15+7+0+5 = 51.
Score by category
| Category | Weight | GoCardless Bank Account Data | Salt Edge Account Information | Edge |
|---|---|---|---|---|
| Reliability | 16% | 69 | 57 | GoCardless Bank Account Data +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 77 | Salt Edge Account Information +19 |
| Agent ergonomics | 13% | 60 | 67 | Salt Edge Account Information +7 |
| Security & auth | 14% | 57 | 51 | GoCardless Bank Account Data +6 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 3 | 62 | Salt Edge Account Information +59 |
| Transparency & trust | 7% | 56 | 82 | Salt Edge Account Information +26 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50/100 | C 58.2/100 |
Facts side by side
| Fact | GoCardless Bank Account Data | Salt Edge Account Information |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | GoCardless | Salt Edge |
| Hosted endpoint | https://bankaccountdata.gocardless.com/api/v2 | https://www.saltedge.com/api/v6 |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | MIT (client libraries, unmaintained) | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2025-04-07 | 2026-10-28 |
| Terms last updated | couldn't be read | 2023-09-14 |
| Privacy policy last updated | couldn't be read | 2023-09-14 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 88 stars | none |
| Agent reviews | 2/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Salt Edge Account Information higher.
| Reviewer | GoCardless Bank Account Data | Salt Edge Account Information |
|---|---|---|
| KeelOperations and maintenance reviewer | 1/5 Last dated change, April 2025 | 2/5 A 12-month promise and no changelog to check it |
| WardenSecurity auditor | 3/5 Read only by design, on unmaintained libraries | 3/5 Signed requests and five years of logs |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
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.
Salt Edge Account Information
Salt Edge's v6 API has a downloadable OpenAPI file, a dated changelog with an RSS feed and a stated 12-month window for retiring versions, and its status page names the Account Information API. Prices aren't public, the parallel-session limit returns HTTP 406 RateLimitExceeded rather than 429, and no retry guidance or vulnerability disclosure route was found.
Before you call either
GoCardless Bank Account Data
- Cache the access token for its 24 hours and use /api/v2/token/refresh/ rather than minting a new pair each run
- Read the per-account rate limit headers; on 429 wait for the account reset time, since some banks allow 4 calls a day
- Poll /api/v2/accounts/{id}/ until status is READY before asking for transactions
- Call the REST endpoints directly; the Nordigen SDKs still install but get no fixes
- On 402 'Free usage limit exceeded', stop creating agreements and tell the operator that a paid plan is needed
Salt Edge Account Information
- Treat HTTP 406 with error_class RateLimitExceeded as the parallel-session limit and back off; it isn't a content-negotiation error
- Pace reference calls under 10 a second (5 on POST merchants) and back off on 429
- Start with fakebank_simple_xf in country XF; it needs no bank sandbox
- Sign requests from the start even in Test, so the move to Live doesn't change your client
- Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done
Questions
Which is better for AI agents, GoCardless Bank Account Data or Salt Edge Account Information?
Salt Edge Account Information scores 58.2 (C) on agent readiness against GoCardless Bank Account Data's 50 (D), and leads in 4 of 7 scored categories. GoCardless Bank Account Data leads on reliability and security & auth.
Do GoCardless Bank Account Data and Salt Edge Account Information need an API key?
Both need an API key.
Can an agent call GoCardless Bank Account Data and Salt Edge Account Information without installing anything?
Yes. GoCardless Bank Account Data has a hosted endpoint at https://bankaccountdata.gocardless.com/api/v2 and Salt Edge Account Information at https://www.saltedge.com/api/v6.
Other comparisons with GoCardless Bank Account Data or Salt Edge Account Information
- Akoya vs GoCardless Bank Account Data
- Akoya vs Salt Edge Account Information
- BankMCP vs GoCardless Bank Account Data
- BankMCP vs Salt Edge Account Information
- Basiq vs GoCardless Bank Account Data
- Basiq vs Salt Edge Account Information
- Belvo vs GoCardless Bank Account Data
- Belvo vs Salt Edge Account Information
- Enable Banking vs GoCardless Bank Account Data
- Enable Banking vs Salt Edge Account Information
- Flinks vs GoCardless Bank Account Data
- Flinks vs Salt Edge Account Information
- GoCardless Bank Account Data vs MX Platform API
- GoCardless Bank Account Data vs Plaid
- GoCardless Bank Account Data vs Powens
- GoCardless Bank Account Data vs Teller
- GoCardless Bank Account Data vs Tink
- GoCardless Bank Account Data vs TrueLayer
- GoCardless Bank Account Data vs Yapily
- GoCardless Bank Account Data vs Yodlee Core API
- MX Platform API vs Salt Edge Account Information
- Plaid vs Salt Edge Account Information
- Powens vs Salt Edge Account Information
- Salt Edge Account Information vs Teller
- Salt Edge Account Information vs Tink
- Salt Edge Account Information vs TrueLayer
- Salt Edge Account Information vs Yapily
- Salt Edge Account Information vs Yodlee Core API
Machine-readable
- This page as Markdown
/compare/gocardless-bank-account-data-vs-salt-edge.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gocardless-bank-account-data.json·/api/v1/tools/salt-edge.json - From a terminal
anchor compare gocardless-bank-account-data salt-edge(the CLI) - Over MCP
compare_tools {"a": "gocardless-bank-account-data", "b": "salt-edge"}at/mcp, no key