Select Actions to adjust the guide

Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.

Action

Scope(s)

Loading actions...

Dynamic Guide URL

Scopes Selected


          
            Separator

1. Pick a Sandbox Institution

Plaid Sandbox simulates real banks. Each simulated bank has an ID prefixed with `ins_`. The institution you pick here determines which kinds of accounts (checking, savings, credit, etc.) the resulting Item will contain.

For most use cases, pick one of these Sandbox institutions. Copy its institution ID (for example `ins_109508`) — you will paste it into the Institution ID field in StackOne Hub in a later step.

**`ins_109508`** — First Platypus Bank
**`ins_109509`** — First Gingham Credit Union
**`ins_109510`** — Tattersall Federal Credit Union
**`ins_109511`** — Tartan Bank
**`ins_109512`** — Houndstooth Bank

The full list of Sandbox institutions — including which products each one supports — is in the Plaid Sandbox institutions docs. The institution you pick must support every product in your Products list, otherwise the mint call will fail.

2. Enter the Sandbox bank account credentials

The Sandbox Username and Sandbox Password fields are the simulated bank account login used to authenticate against the Sandbox institution — NOT your Plaid Dashboard login. Plaid pre-populates a sample bank account for every project and exposes its credentials in the Dashboard.

In the Plaid Dashboard at dashboard.plaid.com, expand the Developers section in the left sidebar, then click Sandbox and open the Credentials tab. The page shows the username and password for your sample bank account. Copy both values into the Sandbox Username and Sandbox Password fields here.

For other simulated bank accounts and credentials that exercise specific scenarios (locked accounts, MFA prompts, insufficient permissions, etc.), see the Plaid Sandbox test credentials reference and use those values if you want to test error paths.

3. Pick the Products to enable (optional)

A Plaid product represents a group of API (e.g., transactions, identity, auth). The products you pick are enabled on the Sandbox Item StackOne mints, which determines which actions in this connector will work with the resulting access\_token.

**If you leave this field blank default product list will use, the default product list includes `statements`** — and `statements` always requires the Statements Start Date and Statements End Date below. Either fill those date fields, OR explicitly type a product list that does not include `statements` (e.g., `transactions auth identity`).

Enter one or several products, space-separated. Examples: `transactions`, `transactions auth`, `transactions auth identity`.
Leave the field blank to use the default set of 7 products: `transactions auth identity investments liabilities assets statements`. The other enabled products (`income`, `enrich`, `balance`) are NOT in the default — see the next step for why, and type them explicitly if you need them.
The institution you select must support every product you list, otherwise Plaid will reject the mint call.
If the list includes `statements` (or you leave the field blank, since the default contains `statements`), you must also fill the Statements Start Date and Statements End Date — both are required, you cannot provide only one. Without them Plaid returns: *"Statements product requires a Statements object to be passed in."*

Enables actions: Create Asset Report, Download Statement, Enrich Transactions, Filter Asset Report, Get Asset Report, Get Asset Report PDF, Get Auth, Get Bank Income, Get Bank Income PDF, Get Credit Sessions, Get Employment, Get Identity, Get Investment Holdings, Get Investment Transactions, Get Liabilities, Get Payroll Income, Get Payroll Income Risk Signals, Get Recurring Transactions, Get Transactions, List Statements, Refresh Asset Report, Refresh Statements, Refresh Transactions, Remove Asset Report, Sync Transactions

Pick only the products that back the actions you intend to run.

Only the following Plaid products are turned on for the sandbox account. Any product NOT in this list cannot be used as a value of `initial_products` (sandbox\_create\_public\_token) or `products` (create\_link\_token) until it is enabled in Plaid Dashboard → Account → Products. Actions that depend on a disabled product are marked `releaseStage: preview` and have not been live-tested. Per-action availability is enforced by each action's `requiredScopes`.

The list below shows the products that must be passed in `initial_products` to mint an access\_token with that capability. Items without a tag are included by default when you leave the Products field blank; items tagged (opt-in) are enabled but must be typed explicitly.

Assets
Auth
Identity + Identity Match (Identity Match is a sub-product available on any Item with `identity` enabled)
Income (bank + payroll)
Investments + Investments Refresh + Investments Move + Investments Auth (refresh/move/auth are endpoints on top of an Item with `investments` enabled)
Liabilities
Statements (requires Statements Start Date and End Date below)
Transactions + Recurring Transactions + Transactions Refresh (recurring/refresh are endpoints on top of an Item with `transactions` enabled)

These products are also enabled on the sandbox account but must NOT be typed in the Products field — they are not valid `initial_products` values.

Balance — auto-included on any Item. Call `/accounts/balance/get` on any existing Item to get fresh balances. Plaid will reject the mint call if you type `balance` in the Products field.
Enrich — stateless. Call `/transactions/enrich` directly with your own transaction data — no Link flow, Item, or access\_token required.

4. Statements dates (only if Products includes `statements`)

These two date fields apply only when your Products list includes `statements` — either explicitly typed (e.g., `transactions statements`) or by default (the Products field, when left blank, defaults to all seven products and that default list contains `statements`).

Format both dates as `YYYY-MM-DD`. Do not use future dates — a future-dated range causes the mint to fail, so the account may not connect. Use a historical range, e.g., Start Date `2025-01-01`, End Date `2025-12-31`.
End Date must be on or after Start Date.
Both dates must be provided together — providing only one will cause Plaid to reject the mint call. StackOne sends `options.statements` to Plaid as soon as either field is filled (and `statements` is in your Products list), and Plaid requires both `start_date` and `end_date` to be valid.
If your Products list does not contain `statements` (e.g., you typed `transactions auth`), the date fields are ignored — StackOne does not send `options.statements` to Plaid in that case, regardless of what you put here.
If you leave Products blank (default = all seven products, which includes `statements`) you must fill both dates here, otherwise the connect will fail with a Plaid error about missing `options.statements`.

Linking the Account from the Hub

Use one of the three Linking Account Methods to access the Hub. Fill out the following fields using details from your provider:

Institution ID
Sandbox Username
Sandbox Password
Products (Optional)
Statements Start Date (Optional)
Statements End Date (Optional)

Click Connect
If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.
Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.