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 API reference separates account information services (AIS) from payment initiation services (PIS). The AIS resources include customers, connections, consent, accounts and transactions.
Authentication, callbacks and testing
- API request examples authenticate with App-id and Secret headers.
- Success and failure callbacks identify the customer and connection, so an application can follow the result of a connection attempt.
- A consent-status callback reports when consent expires or is revoked, allowing applications to respond without polling its status.
- Fake providers in the test country XF let applications exercise connection flows. Live clients can include these sandboxes in provider-list requests with include_sandboxes.
Check the institutions you need
Use Salt Edge’s country and provider resources to check its account-information coverage. For a Synci connection, use Synci’s bank directory.
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.
Building an app for your users?
For consumer apps that need bank and brokerage data, Synci also offers a managed route. Synci Managed apps connect your users’ bank and brokerage accounts through a Synci-hosted portal. Your users do not need a Synci account.
Register users from your backend through the Managed Users API and receive transactions and connection events by webhook. Managed apps are priced per active connection, with no provider application, AISP licence or bank integration work on your side.
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 25 September 2026. Provider details can change; follow the linked documentation for current setup requirements.
Synci is not affiliated with, endorsed by, or connected to Salt Edge. All product names and trademarks are the property of their respective owners.
Put your bank data to use.
Check your bank, connect the accounts you need, and choose where to use them.