Salt Edgevs
Plaid
Plaid: If your users are predominantly in the United States, where Plaid coverage and reliability are stronger
Salt Edge
Independent open banking aggregator covering Europe by PSD2 API and other markets by direct connection
As of 31 August 2026, Salt Edge's pricing is not published; the vendor quotes on request. Salt Edge is one of the few sizeable open banking aggregators not owned by a card network or a payments giant, which matters because the owner decides what data you may use it for. Softwr lists it under APIs. Salt Edge is available on Web, API.
Overview
What Salt Edge does
Salt Edge provides account information and payment initiation services to businesses that need to read bank data or move money on a customer's behalf. Its aggregation product covers thousands of financial institutions across more than fifty countries, returning accounts, balances, transactions and identity data through one API and one consent model. A second product line, the Open Banking Gateway and compliance suite, sells to banks that must publish their own PSD2 or open banking APIs, which is a different business from aggregation and gives the company a hedge against aggregation margins. Ownership is the fact that should change a shortlist. Plaid is independent but US-centric, Finicity is Mastercard, Tink is Visa, and Yodlee sits inside Envestnet. When a card network owns the aggregator, the permitted use cases and the commercial terms are shaped by that network's wider strategy, and several buyers have found data uses restricted or repriced after an acquisition. Salt Edge remains independently owned, is registered as an account information service provider in the United Kingdom and holds PSD2 permissions in the European Union, and its country coverage extends well beyond the regulated open banking markets. That breadth carries a technical caveat buyers should press on. Inside PSD2 markets, connections use banks' regulated APIs, which are stable and legally underpinned. Outside them, coverage often relies on direct connections that are not regulated interfaces, and reliability there depends on the bank not changing its site. If your product promises a fixed refresh cadence to customers, ask Salt Edge which specific institutions on your list are direct regulated APIs and which are not, because the answer determines your support load. Pricing is usage-based and not published.
What people use it for
- A lender operating across several European and non-EU markets that needs one aggregation contract rather than a different provider per country
- A fintech that wants an aggregator not owned by a card network because its use case competes with card products
- An accounting or treasury product that needs bank feeds in markets the large aggregators do not serve
- A bank that must publish PSD2-compliant APIs and would rather buy the compliance layer than build it
Related searches
The honest half
Where it falls short
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Salt Edge.
- Coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
- Pricing is not published and is usage-based, so two providers cannot be compared without running both sales processes, and cost grows with the connected user base rather than with revenue.
- Support and engineering are distributed across Eastern Europe and Canada, and buyers in other time zones report slower turnaround on connection-specific breakages than they get from a domestic provider.
- PSD2 consent rules require customers to reauthenticate periodically, and Salt Edge cannot change that, so any product depending on continuous data must design for consent expiry and the drop-off it causes.
- United States coverage is weaker than Plaid or Mastercard Open Banking, so a company with meaningful US volume ends up running two aggregators and normalising between them.
Cross-shopped
What people choose instead of Salt Edge
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.
- Salt EdgevsStripe
Stripe: If you only need payment collection rather than account data across many banks
- Salt EdgevsWise
Wise: If your requirement is cross-border money movement rather than reading bank data
Pricing
What Salt Edge costs
Taken from the vendor's own pricing page. Prices move, so check before you buy.
Salt Edge Open Banking API
On request
- Account information and payment initiation
- Coverage across 50 plus countries
- Consent management and enrichment
- Free sandbox for development
- Usage-based pricing, quoted
Capabilities
Features
Account information
Accounts, balances, transactions and holder identity across supported institutions
Payment initiation
PSD2 payment initiation in supported European markets
Wide country coverage
Connections beyond the regulated open banking markets, including emerging economies
Open Banking Gateway
Sells banks the compliance API layer they are required to publish
Categorisation and enrichment
Merchant identification and transaction categorisation on retrieved data
Consent management
Records and renews customer consents in line with regulatory requirements
Partner and white label
Reseller arrangements for platforms embedding aggregation in their own product
Sandbox
Fake bank environment for development before production credentials
Answered, with sources
Questions people ask
Each answer names the page it came from, so you can check it rather than take our word for it.
Who owns Salt Edge?
It is independently owned, unlike Tink (Visa), Finicity (Mastercard) or Yodlee (Envestnet), which matters if your use case competes with the owner.
Is all coverage direct bank API?
No. Inside PSD2 markets connections use regulated APIs; elsewhere coverage relies on direct connections whose reliability depends on the bank not changing its systems. Ask for a per-institution answer.
Does it do payments as well as data?
Yes, payment initiation is supported in European markets where PSD2 applies.
What does it cost?
Not published. Pricing is usage-based and quoted, though the sandbox is free.
Keep looking
Where to go from Salt Edge
- Salt Edge alternativesEvery product people weigh against it
- Salt Edge pricingPlans, floors and what the tiers exclude
- Salt Edge badgesWhich rules it meets, and the figure behind each
- All APIs softwareThe full category
- Best APIs softwareThe shortlist, and how it was cut
Best APIs software for
Compare Salt Edge with
- Enable Banking
- TrueLayer
- Ozone API
- Bud Financial
- Tink
- Trustly
- Tribe Payments
- Volt
- Akoya
- Neonomics
- Token.io
- Yapily
- GraphQL Apollo
- GraphQL Playground
- Gravitee
- Hoppscotch
- HTTPie
- Janus Gateway
Other APIs software
European bank API aggregation with a free restricted production tier for your own accounts
Free plan11 researched notesOpen banking payments and data across the UK and Europe, with the largest share of UK variable recurring payments
Pricing on request13 researched notesStandards-compliant open banking API layer for banks and regulators
Pricing on request11 researched notesTransaction enrichment and customer intelligence for banks, built on UK open banking data
Pricing on request13 researched notesEuropean open banking platform for account data and payment initiation
Pricing on request12 researched notesPay-by-bank payments network, majority-owned by private equity firm Nordic Capital
Pricing on request10 researched notesCombined issuer and acquirer processing platform for fintechs, banks and acquirers
Pricing on request10 researched notesAccount-to-account pay by bank across Europe, the UK, Brazil and Australia
Pricing on request11 researched notesBank-owned, token-based open finance network that replaces screen scraping for US financial data
Pricing on request11 researched notesNordic open banking payments and data, now with UK coverage through Ordo
Pricing on request11 researched notesAccount to account pay by bank infrastructure across the UK and Europe
Pricing on request11 researched notesOpen banking API infrastructure for account data and pay-by-bank payments across Europe
Free plan10 researched notesComplete platform for building GraphQL APIs
Free, then $5/million requests10 researched notesGraphQL IDE and documentation tool for building GraphQL APIs
Free plan8 researched notesOpen-source API development ecosystem with web-based REST client
Free plan8 researched notes
Softwr does not host reviews and shows no star rating for Salt Edge, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
More on Salt Edge
Salt Edge alternatives
What people switch to, and what they give up
Salt Edge pricing
Every tier, and where the cost actually lands
Compare Salt Edge
Put it head to head with anything we hold
Salt Edge badge
Its rating, and an embed for your own site
Best APIs software alternatives
European bank API aggregation with a free restricted production tier for your own accounts
Per connected account per month
Digital and AI-native engagement banking platform for customer-facing banking experiences
quote