Migrate from Transactions to Plaid Consumer Report

This guide will walk you through how to migrate from accessing bank data with Plaid's Transactions product to generating Base Reports with Plaid's Consumer Report product.

The CRA Base Report includes account balance, account ownership, and transaction data, and is designed for use cases that require FCRA-compliant consumer reporting, such as tenant screening, income verification, and credit decisioning.

While the Transactions product gives you historical transaction data, the CRA Base Report enhances this by:

• Supporting FCRA-compliant usage
• Bundling additional data (identity, balance, account metadata) in a single report
• Managing the explicit consumer consent and disclosures required for underwriting use cases in the US

If your use case involves evaluating the financial standing of US-based end users for underwriting, credit, or leasing, you should use the CRA Base Report instead of Transactions.

1. Update your Plaid SDK to the latest version. Minimum required versions:
   • Python: 23.0.0
   • Go: 26.0.0
   • Java: 24.0.0
   • Node: 25.0.0
   • Ruby: 29.0.0
2. Confirm you have access to Plaid Check products in Production. If not, request access via the Dashboard.

When using Plaid Check products, you must create a user before initializing Link. This allows Plaid to associate multiple Items with a single user.

1. Call /user/create before /link/token/create
   • Include consumer_report_user_identity.
   • All fields are required except last_4_ssn.
   • Store the user_id and user_token in your database.
2. Update your /link/token/create call:
   • Remove the transactions object (if present) from the call.
   • Include the user_token from /user/create.
   • Replace transactions with cra_base_report (and any other CRA products) in the products array.
   • Add a cra_options object with days_requested (min 180).
   • (Optional) Include consumer_report_permissible_purpose to begin report generation immediately.
   • (Optional) To allow multi-institution linking, set enable_multi_item_link to true.

1const request: LinkTokenCreateRequest = {
2  loading_sample: true
3};
4try {
5  const response = await plaidClient.linkTokenCreate(request);
6  const linkToken = response.data.link_token;
7} catch (error) {
8  // handle error
9}

1. If you didn't include consumer_report_permissible_purpose in the /link/token/create call, you will need to manually trigger report generation by calling /cra/check_report/create, specifying a webhook, days_requested quantity, and consumer_report_permissible_purpose. If you did include consumer_report_permissible_purpose, the report will be automatically generated once the Link session has successfully completed and this step is not necessary.

2. Update your webhook listener endpoints, adding listeners for Plaid Check.

   • Upon receiving the CHECK_REPORT_READY webhook, call product endpoints such as /cra/check_report/base_report/get or (if using) /cra/check_report/partner_insights/get.

   • Upon receiving the CHECK_REPORT_FAILED webhook, call /user/items/get to determine why Items are in a bad state. If appropriate, send the user through update mode to repair the Item.

1. If you're still using other Plaid products like Auth or Balance, continue retrieving and exchanging the public token. Otherwise, it's no longer needed.

This Google Sheet highlights the correspondences between Transactions and CRA Base Report schemas.

There is no way to directly migrate an existing Transactions-enabled Item to Plaid Check. Instead, you must delete the old Item using /item/remove and prompt the user to go through the Link flow again, using a Link token that is enabled for Plaid Check.

If you are ready to migrate all Items, use /item/remove to delete the Transactions-enabled Items, and prompt your users to return to your app to re-add their accounts using the new Plaid Check-enabled flow. You can also perform this process in stages, disabling only a percentage of Items at a time.

The most conservative gradual migration strategy is to not delete the Transactions-enabled Item until it is in an unhealthy state that requires user interaction to fix (e.g. ITEM_LOGIN_REQUIRED). At that time, instead of sending the Item through update mode, delete the Item using /item/remove and prompt your users to re-add their accounts using the new Plaid-Check enabled flow.

Depending on your use case and business, you may want to leave existing Transactions-enabled Items in place and perform a gradual migration, as described above. Do not remove Transactions logic unless you are no longer using any Transactions-enabled Items.

1. Remove handling for Transactions webhooks, including SYNC_UPDATES_AVAILABLE, INITIAL_UPDATE, HISTORICAL_UPDATE, DEFAULT_UPDATE, RECURRING_TRANSACTIONS_UPDATE

2. Remove calls to /transactions/ endpoints such as /transactions/get, /transactions/sync, or /transactions/recurring/get, as well as any handling for transactions-specific logic, such as transactions updates and pagination.

3. Remove handling for the TRANSACTIONS_SYNC_MUTATION_DURING_PAGINATION error.

4. If you have existing Transactions-enabled Items you will no longer be using, call /item/remove to delete these Items so you will no longer be billed for Transactions.