Skip to main content

Overview

Instead of having to build your own architecture to manage Plaid linkage and transactions, you can leverage Tight’s proven architecture to communicate directly with Plaid on your behalf. Once configured, Tight’s Plaid integration provides:
  • A seamless UX for your users to connect and manage their bank connections
  • Intuitive UX to walk your users through fixing connection issues on their own
  • Webhook handling to process newly available transactions in real-time
  • Automatic transaction categorization, with full double-entry accounting

Create a Plaid Team

If you haven’t done so already, Tight can introduce you to Plaid to get your team registered quickly. Once you have access to the Plaid Dashboard, be sure to enable Account Select so that your users can select which bank accounts to link to their accounting platform.

Securely sharing your Plaid keys

In your Plaid Dashboard, to view your API keys, click on Team Settings -> Keys. Use the Configure Plaid API to securely share your keys. Once complete, the Tight Embedded UI will automatically allow your users to link their bank accounts and start syncing bank transactions.

Connect your user’s Plaid accounts

There are three primary ways to connect your users’ Plaid accounts to their company in Tight:
  1. Embedding Tight’s Financial Overview, which includes all onboarding tasks, including Plaid linkage
  2. Embed Tight’s Banks & Integrations page, which includes Plaid linkage as well as any other native integrations you choose to enable
  3. Or, if you already handle Plaid linkage in your UX, you can programmatically link the user’s Plaid accounts

Go Live in Production

Before allowing users to link accounts in production:
  1. Request Production access, then complete your application profile, company profile, and security questionnaire. Some financial institutions require this information for OAuth connections. See Plaid’s Launch in Production checklist for the complete set of launch recommendations.
  2. Open the Data Transparency Link Customization. For each Link customization your app uses, select one to three use case descriptions that accurately explain how your app uses financial data, then publish the changes. For example, apps that use Tight for bookkeeping and tax features can select Do business accounting and tax preparation.
If Data Transparency Messaging is enabled but a Link customization has no published use case, Plaid rejects production Link requests with the INVALID_LINK_CUSTOMIZATION error.

Get access to bank statements [Optional]

Before enabling Plaid Statements in production, submit a Plaid support ticket and explicitly request direct access for Chase. Wait for Plaid to confirm access before enabling Statements for your production users.