Implementation Guide

Access to the implementation must be restricted to Plaid IP addresses only
The implementation should have the resources to support potentially very large, periodic request volumes: up to N × 24 requests/day where N is the expected number of connected accounts, requesting transaction periods of typically previous 7 days
Identify components of your infrastructure that handle authentication. Plaid recommends that you secure the Plaid Exchange API using an OAuth v2.0 authorization server.

Assemble the list of account types the implementation should be expected to support, and map them to the Plaid account types
Identify data sources for all of the required elements on account and transaction models

Auth: ensure that depository accounts have a valid transfer_codes entry for the payment networks available in your region (e.g. the ACH in US)
Auth: ensure that transfer_codes correctly indicate institutional support for debit and credit transfers

Partners must implement features in order of complexity and depth, according to the following roadmap:

Feature	Phase I	Phase II	Phase III
Authentication	Implements single-factor authentication.	Implements multifactor authentication.
Accounts	Implements basic metadata for all account types.	Implements extended metadata for all account types.
Identity	Returns `BasicIdentity` for account owner relationships.	Returns `FullIdentity` for account owner relationships. Non-owner relationships are modeled.
Transactions	Implements basic metadata for all transaction types.	Implements extended metadata for all transaction types.
Notification		Sends new transactions and new account notifications. Sends link and unlink application notifications.	Implements and proactively presents in-app Plaid consent UX. Sends new item notifications.
Acquisition		Implements in-app UX permitting users to view and control account links, including referral to Plaid-powered apps.	Implements account opening and funding interface.