Bank Connectivity
Who can be connected: the institution catalog, the aggregator subscription, and the registrations behind them.
11 steps · 9 questions · 4 screens on this shelf
The screens on this shelf
Records
Bank Channels
The institutions that can be integrated, and what each of them actually supports. A bank that does not offer a channel cannot be configured for it.
Open
Records
Bank Catalogue
Which banks can be connected and how: a sign-in on the bank’s own site, the bank’s own download service, or through the aggregator. Where a bank offers a sign-in, its authorization and token endpoints belong here — they come from the developer portal with the client credentials.
Open
Records
Bank Aggregators
The subscription that reaches banks on this company’s behalf — Plaid, Tink, TrueLayer or Salt Edge. Put the client id and secret here and the aggregator becomes the default route in Connect a Bank; the secret is sealed on the way in and never comes back out. Without a row here the platform uses its own sandbox and says so on every screen.
Open
Records
Bank Data Recipients
What a bank, or an aggregator network, issued this company so it can be signed in to: a client id, a client secret and the redirect URI it declared. The secret is sealed on the way in and never comes back out. Without a row here a bank can still be reached by download credential or through the aggregator.
Open
Progress is kept in this browser only — it is not sent anywhere and nobody else can see it.