Introduction to Income

Explore API

Plaid Income (currently US only) helps you verify anyone's income and employment in seconds, facilitating an improved decisioning and underwriting process. You can verify a user's income via three products:

Payroll Income: Retrieve income information from a user-connected payroll account.

Document Income: Retrieve income information via a user-uploaded documents such as a pay stub or W-2 form.

Bank Income: Retrieve income information from a user-connected bank account.

Income is configurable, allowing you to choose at the time of connection which income verification method best suits your user’s needs. The Document Income solution is a natural fallback to the Payroll Income solution, but you are also able to mix and match income verification methods.

Depending on your use case, you may want to enable different income verification methods. For instance, if your use case relies on net income or income deposited in a user’s bank account, you can leverage Bank Income. Additionally, if you plan to use other Plaid products, such as Auth and Balance for payments, you can use Bank Income to verify income in a single Link experience, without requiring your user to go through multiple flows. For use cases that require gross income verification, you may want to use both Payroll and Document Income.

1. Call /user/create to create a user_token that will represent the end user interacting with your application. This step will only need to be done once per end user.
2. (Optional) Call /credit/payroll_income/precheck with the user_token. This endpoint will indicate Plaid's confidence that a user will be able to complete the Payroll Income flow and can increase conversion by customizing the Payroll flow in Link for the specific user. For users where the endpoint returns a low confidence in their ability to connect via Payroll Income, we recommend you launch Link with either Document Income or Bank Income instead.
3. Call /link/token/create. In addition to the required parameters, you will need to provide the following:
   • For user_token, provide the user_token from /user/create.
   • For products, use ["income_verification"]. If using Bank Income, you can also specify additional products.
   • For income_verification.income_source_types, use either payroll (for Payroll and Document Income) or bank (for Bank Income). You can further customize the flows enabled and the amount of data collected via optional parameters; see the API Reference for more details.
   • Provide a webhook URI with the endpoint where you will receive Plaid webhooks.
4. On the client side, create an instance of Link using the link_token returned by /link/token/create; for more details, see the Link documentation.
5. When the user has successfully completed the client-side Link flow, you will be alerted in one of two ways:
   • If using Bank Income, listen for the client-side BANK_INCOME_INSIGHTS_COMPLETED Link event that occurs after onSuccess. This event indicates that a user has completed the full Bank Income flow. If you are using other Plaid products such as Auth or Balance alongside Bank Income, make sure to capture the public_token from the onSuccess callback and exchange it for an access_token. For more details on token exchange flows, see the Token exchange flow.
   • If using Payroll or Document Income, listen for the INCOME: INCOME_VERIFICATION webhook. For more details, see Income webhooks.
6. To retrieve data, call the credit endpoints using the user_token.
   • For Payroll or Document Income, call /credit/payroll_income/get.
   • For Bank Income, call /credit/bank_income/get.

When using Payroll or Document Income, Plaid will asynchronously process the income data and send an INCOME: INCOME_VERIFICATION webhook once processing is complete. If processing was successful, the webhook's verification_status value will be VERIFICATION_STATUS_PROCESSING_COMPLETE. If you attempt to retrieve the income data before it has been processed, you may receive a 400 response with the error code PRODUCT_NOT_READY. Awaiting the webhook before calling /credit/payroll_income/get is strongly recommended.

Processing will usually complete within a few seconds if the user's income was verified via Payroll Income. If the user verified their income via Document Income, processing may take up to 45 minutes.

When using Bank Income, no webhooks are sent; data will be available as soon as the BANK_INCOME_INSIGHTS_COMPLETED event has been emitted by Link.

Income can be tested in Sandbox against test data without contacting Plaid. In order to test Income against live Items in either Development or Production, you will need to first request access by submitting a product access request Support ticket explaining your use case.

Note that in the Sandbox environment, Document Income data will be available instantly. To test that your application properly handles the real-world delayed processing behavior of Document Income, test in the Development environment.

Many users get income deposited into multiple institutions. To help capture a user’s full income profile, you can allow your users to link multiple accounts within the same link session on web integrations.

To enable this flow:

1. When calling /link/token/create set the bank_income.enable_multiple_items option to true.
2. Pass in the onResult callback to the Link Web SDK

Every time the user successfully links an Item by authenticating their account, you will receive an item_add_result through the onResult callback. The onResult callback will be fired once for every added Item, while the onSuccess callback will fire for the final added Item, indicating that the user has exited Link.

While you can access Bank Income data with the user_token, if you are planning to leverage these account connections for other Plaid products (such as Auth, Balance, etc) you should make sure to process the output of the onResult callback, by exchanging the provided public_token for an access_token.

For an example of an app that incorporates Income, see the React and NodeJS-based Income Sample app. This application uses Income and Liability data to help determine whether the user can qualify for financing on a pre-owned hoverboard. It supports the use of Payroll, Document, and Bank Income data.

To learn more about building with Income, see the Income API Reference.

If you have feedback to provide, please let us know in our Developer Feedback repo on GitHub (beta).