DriveWealth and Plaid have partnered to allow for a quick and seamless integration between Plaid bank accounts and DriveWealth's money movement APIs. Partners utilizing our ACH pull functionality to fund brokerage accounts can utilize banking tokens already configured at Plaid.

Getting started


Get Plaid API keys

To utilize this integration, you'll need to have a Plaid sandbox account already configured.

Sign up on

Existing Plaid customers can immediately utilize the combined integration, just by enabling it in the Integrations section of the Plaid dashboard:


Obtaining processor tokens

Communication between Plaid and DriveWealth occurs using processor tokens. These are identifiers that contain banking details and are securely scoped to allow only DriveWealth to view. You may be familiar with other types of tokens issued by Plaid that you use in your product today:

Token type


Public token

Temporarily stores details about a customer's banking relationship, for use in transit between their device and your infrastructure.

Access token

Stores details about a customer's banking relationship, for use from your infrastructure. Typically, a public token from Plaid Link is immediately converted into an access token, which is then stored.

Processor token

Allows DriveWealth to access details for a single bank account.

After a customer connects their bank using Plaid Link, a processor token can be generated at any time:

curl \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": "PLAID_CLIENT_ID",
    "secret": "PLAID_SECRET",
    "access_token": "ACCESS_TOKEN",
    "account_id": "ACCOUNT_ID",
    "processor": "drivewealth"
  }' \
  -X POST \

# Response - this processor token should be sent to DriveWealth
  "processor_token": "processor-sandbox-0asd1-a92nc",
  "request_id": "[Unique request ID]"

Note that the account ID specified above will grant DriveWealth access to view only that individual bank account. As an example, if a customer logs in to Plaid Link using their Chase credentials, and has 4 checking accounts eligible for funding, you'll need to have the customer first specify just one of those accounts to use.

Processor token best practices

  • Continue to store only access tokens, not processor tokens
  • Don't generate processor tokens if a customer is not planning to fund a DriveWealth-supported brokerage account