This document describes Plaid Sequencing, a feature that enables multiple Plaid products to be requested and executed within a single, automated workflow. It explains how each step—such as Identity Verification, Income Verification, and Bank Auth/Assets—is defined, including the conditions for success or failure that determine the next step in the sequence.
The document also highlights how sequencing improves efficiency, ensures the most relevant financial data is collected, and provides fallback options to handle verification failures, creating a smooth and streamlined experience for both businesses and end users.
What is Plaid Sequencing
Plaid Sequencing allows you to combine multiple Plaid products within a single verification workflow, rather than triggering each service separately. This creates a smoother user experience and ensures that the required information is collected in the most efficient way.
For example:
You may first request Identity Verification. Once the user’s identity is confirmed, the workflow can automatically guide them to connect to their payroll provider. If payroll data is not available, the user can then be prompted to connect their bank account so the system can retrieve the necessary account details.
This step-by-step approach ensures that the strongest and most relevant data source is used first, while still providing fallback options to complete verification when the primary source is unavailable.
In short, Plaid Sequencing helps streamline verification by intelligently chaining multiple data-collection steps into one guided process.
How to Configure?
Metadata Update
Name: Plaid Configuration
-
Go to Setup → Search for Custom Metadata
-
Click on Manage against Plaid Configuration Metadata.
-
Create a new entry for Product_Sequencing and add the below JSON in the Mapping JSON (bankconnect__Sequencing_Order__c) field.
This JSON defines the sequence of steps a customer must go through when connecting with Plaid.
Each step requests a specific Plaid product (e.g., Identity, Income, Assets).
Based on success or failure, the sequence decides which step should run next.
{
"sequence": [
{
"order": 1,
"product": "Identity_Verification",
"success": 2
},
{
"order": 2,
"product": "Income_Verification",
"incomeSource": "Bank",
"incomeDuration": 30,
"fail": 3
},
{
"order": 3,
"product": "Auth;Assets",
"assetDuration": 60,
"assetPDF": true
}
]
}
|
Step |
Product(s) |
Order |
Next Step on Success |
Next Step on Failure |
Additional Settings |
Description |
|---|---|---|---|---|---|---|
|
1 |
Identity_Verification |
1 |
2 |
N/A |
N/A |
Verifies the customer’s identity (name, DOB, address). If successful, proceeds to Step 2. |
|
2 |
Income_Verification |
2 |
N/A |
3 |
incomeSource: BankincomeDuration: 30 days |
Verifies income using bank data for the past 30 days. If it fails, proceeds to Step 3. |
|
3 |
Auth;Assets |
3 |
N/A |
N/A |
assetDuration: 60 daysassetPDF: true |
Verifies bank account ownership and retrieves asset information. Generates a PDF report of assets. |
This table clearly shows the sequence, products, decision points, and additional parameters for each step in the workflow.
Sample Workflow Summary (Business Description)
-
Identity Verification is attempted first.
✅ If it succeeds → move to Income Verification. -
Income Verification attempts to verify the customer’s income using bank data.
❌ If it fails → move to Bank Auth + Assets Verification. -
Auth + Assets collects account validation and asset balance information.
If enabled, a PDF asset report will be generated.
This decision-based workflow ensures the business retrieves the best available customer financial information while gracefully handling failures.
Update Embedded URL
The embedded verification URL must include the following parameter at the end:
&sequencing=true