Salt Edge: building around account information APIs
Salt Edge publishes APIs for account information and payment initiation. For bank-data use cases, its account information API gives developers connection, account, and transaction resources to integrate into their own application.
By Synci · Last verified
Account information and payments are separate
Salt Edge’s documentation separates account information services (AIS) from payment initiation services (PIS). If you only need balances and transactions, evaluate the account information product and its access requirements. Do not treat a payment capability as necessary for a read-only data workflow.
The connection lifecycle is part of the integration
The API documents customers, connections, consent, accounts, transactions, and callbacks. An application needs to handle more than its first successful data request: reconnecting, refreshing, revoking access, and responding to failures are also part of the product experience.
- Confirm which integration model and production access terms fit your application.
- Use provider and country information to check coverage for the account-information service.
- Plan server-side credentials, callbacks, and the user’s connection and reconnection screens.
- Test data handling against the banks you intend to support.
Evaluate coverage for the data you need
Check current institution support rather than comparing providers only by a headline bank count. A payment connection and a transaction-data connection answer different questions. Also test account type, currency, history depth, and the behavior of transactions that are still pending.
For Synci, the bank directory is the source of coverage information. Salt Edge’s institution list should not be used as evidence that Synci can connect the same bank.
When Salt Edge is the better fit
A direct Salt Edge integration can fit a team building its own application around the documented connection lifecycle, or a product that needs a separate payment-initiation service. Evaluate those requirements with the provider.
Synci fits a read-only workflow where you want managed connections and destinations already available. It handles account selection and data access for supported apps, while its rules can transform transaction data. Synci does not move money, and this comparison does not imply a Salt Edge provider relationship.
Questions and answers
- Does a bank-data API necessarily let an app move money?
- No. Account information and payment initiation are separate capabilities. Synci’s bank-data destinations and MCP access are read-only.
- Which service should I choose for a personal budget?
- Start with the budget’s supported import or sync methods and your exact banks. Synci can supply data to Actual Budget through SimpleFIN and has destinations for YNAB and Lunch Money. A direct API requires you or the app developer to build the downstream integration.
Sources and verification
Checked on 23 September 2026. Provider details can change; follow the linked documentation for current setup requirements. This guide is published by Synci.
Put your bank data to use.
Check your bank, connect the accounts you need, and choose where to use them.