GoCardless Bank Account Data

GoCardless Bank Account Data is a consent-led API that retrieves bank-account information through PSD2 connections. It is aimed at businesses and developers building services that need balances, account identity and transaction data in structured JSON. It is a strong fit for EEA-focused products needing established open-banking controls, but bank request caps and paid-only verification can be decisive drawbacks.

Overview

Customers choose a supported financial institution, approve a GoCardless-hosted consent screen and authenticate in the bank’s own interface. The API then returns account-holder names, account numbers or IBANs, transaction records and current and available balances. End-user consent remains central to every connection, so this suits products that need a compliant user-authorised data flow rather than credential-based collection.

GoCardless says it does not store or process end-user credentials when a bank uses GoCardless to collect them. It encrypts data in transit and at rest, has held ISO 27001 certification since 2016, and is authorised by the UK Financial Conduct Authority under the Payment Services Regulations 2017. Technical support is provided through its support team.

Key features

Account and transaction data

Services can request as much as 24 months of transaction history, with continuous access lasting up to 90 days. Returned transactions can include dates, counterparties, descriptions and amounts, while account responses include identifiers and both balance types. Refreshes are on demand, although the connected bank has the final say: some institutions may permit only four API calls per account each day. That is adequate for periodic financial overviews, but restrictive for products expecting frequent synchronisation.

Developer integration

The Bank Account Data API responds in JSON and requires an authorization token created with a Bank Account Data portal user secret. GoCardless supplies a quickstart guide and directions for importing the API schema into Postman, giving development teams a practical starting point. Integration still requires handling institution selection, consent and bank authentication flows, so it is better suited to teams comfortable with API-based financial services than to no-code users.

Verification and coverage

Account Information is offered in EEA countries subject to PSD2 where GoCardless operates as an authorised AISP. Regional eligibility therefore matters before implementation. New accounts are non-verified by default, and account verification is available only to paying customers; businesses that need verified ownership checks must budget for a paid arrangement rather than relying on a basic connection.

Pricing

GoCardless uses paid, custom pricing, with rates supplied on request. That model can suit organisations requiring negotiated support or volume terms, but it prevents a straightforward cost comparison and provides no self-serve free tier. The paid status also matters for verification, which is not offered to non-paying customers. Businesses should confirm regional coverage, expected request volume and verification requirements during the sales process, especially where bank limits could constrain usage.

Platforms

The service is delivered through an API and web-based tools. JSON responses, portal credentials, quickstart documentation and Postman schema import support an engineering-led implementation rather than a standalone end-user application.

Who it's for

GoCardless positions the service for businesses ranging from small companies to enterprises that need account information and transaction history from bank connections. It is particularly appropriate for EEA products that can work within PSD2 consent journeys and tolerate bank-controlled refresh frequencies. It is less suitable for a consumer app needing global coverage, constant polling or free account verification, and less suitable for teams seeking published, predictable pricing.

Pros and cons

Pros

• Useful financial dataset: Up to 24 months of transactions plus account identifiers and current and available balances support budgeting, underwriting and reconciliation workflows.
• Consent-focused connection: Users authorise access through their bank, while GoCardless says it does not handle credentials for institutions that collect them through GoCardless.
• Developer-ready delivery: JSON responses, token-based authentication, a quickstart guide and Postman schema instructions shorten the path to integration.
• Established security and oversight: ISO 27001 certification, encryption and UK FCA authorisation provide meaningful assurance for financial-data integrations.

Cons

• Bank-imposed throttling: Some banks may allow only four calls per account per day, limiting near-real-time refresh use cases.
• Paid-only verification: New accounts are unverified by default, and verification requires a paying account.
• Regional constraint: Account Information coverage is tied to PSD2 EEA markets where GoCardless is an authorised AISP.
• Opaque cost at the outset: Pricing is custom and supplied on request, with no published free plan.

Alternatives

For broader payment operations, compare Payment Processing Software or Bank Connectivity Software. Businesses focused on mandate-based collections can review Direct Debit Processing Software, while ACH-specific workflows belong in ACH Payment Processing Software.

Plaid is worth considering when a paid platform with a trial option and Android, iOS, web and API support better matches your rollout. Choose OpenACH if free, GPL v3.0 open-source deployment and self-hosting are priorities. Nickel offers a free web plan with three active users and a $25,000 transaction limit, making it a lower-commitment option for smaller payment operations. Paymentus is an enterprise billing and payment platform with Android, iOS, web and API access. ACH Processing Company is another paid API and web option. ACHPAY.AI charges $0.35 per contact, capped at $5.00 per transaction, and includes a free trial. Rotessa suits users processing more than 250 transactions monthly at 35¢ per transaction. Authorize.net offers a $25-per-month all-in-one plan with 2.9% plus 30¢ per transaction.

Verdict

Choose GoCardless Bank Account Data when your product needs consented EEA bank data in JSON, substantial transaction history and a supported developer workflow. Its principal strengths are the breadth of returned account data and mature security posture. Look elsewhere if you need global reach, frequent polling beyond bank quotas, free verification or transparent published pricing.