วีดีโอ

We don't provide OAuth webhook authentication, but you can authenticate webhooks using the instructions here plaid.com/docs/api/webhooks/webhook-verification/ . In addition, the Plaid API is designed so that any information received via a webhook is non-sensitive and can be verified by calling an endpoint, so webhook verification is purely optional.

Absolutely, Plaid has a number of integration partners who can build your Plaid integration for you. See plaid.com/partner-directory/ and click on "Consulting" to see some of our integration partners.

Plaid Income will only provide an end user's income information with their consent, so it isn't a good fit for use cases where the end user is trying to hide income. Income is designed for cases where the end user is trying to show that they do have income, such as cashflow underwriting loan applications, or tenant screening.

As of June 2024, the Development environment no longer exists -- to simplify the development process, Plaid replaced the Development environment with the ability to test with real data for free directly in Production. To get access, apply for Production. For more details, see plaid.com/docs/sandbox/#testing-with-live-data-using-limited-production

No.

@@PlaidInc ok

Currently, selfie and documentary checks can be performed only on mobile devices, so to perform an IDV check without a mobile device, you would have to do a data source only check.

Plaid does not provide an official PHP client library. You can use the community-supported PHP client library (github.com/TomorrowIdeas/plaid-sdk-php), create your own client library using the Plaid OpenAPI specification file (github.com/plaid/plaid-openapi), or you can make direct POST requests to the Plaid API without using a client library.

:-D for a repo with an example app using embedded search, see the Transfer QuickStart github.com/plaid/transfer-quickstart

Plaid access tokens do not expire. For more details, see plaid.com/docs/quickstart/glossary/#access-token.

Plaid access tokens do not expire, although in the Sandbox environment, after 30 days, they may enter an error state that can be fixed by using update mode. See plaid.com/docs/quickstart/glossary/#access-token and plaid.com/docs/link/update-mode/ for more details.

@@PlaidInc Thank you so much

If you're having trouble with the OAuth redirect URI, you can remove it from the .env file; it is not necessary to set an OAuth redirect URI for desktop web use cases.

@@PlaidInc Thanks, I'll try that, in the meantime I've emailed support to ask too. Not sure if the API has exactly what we need.

TH-cam isn't the easiest channel for troubleshooting an issue like this -- can you file a support ticket so that the support team can look up the logs and see exactly what happened in the session? Thank you!

Good catch! Since this video was made, the Quickstart switched from using the older /transactions/get endpoint (which uses date ranges) to the newer /transactions/sync (which uses a cursor), because /transactions/sync is much easier to use for managing transaction updates in a real-world use case.

There are some things you need to do! If you're having trouble with the OAuth handoff on mobile, see the OAuth section of the Plaid on iOS tutorial: th-cam.com/video/9fgmW38usTo/w-d-xo.htmlfeature=shared&t=2608

Probably! Googling suggests a couple of possible fixes, including using yarn instead of npm, blowing away node_modules, and forcibly lowering the version of ajv-keywords specified in the package.json file to 3.x.x. If none of that helps, please open an issue on the GitHub repo for the Quickstart where we can dig into this in more depth.

@@PlaidInc Thanks so much. I blew up the old repo and started fresh from the github. I used yarn to install node_modules for the front end, but still used npm for the node server. Didn't modify package.json, and was able to get this back on track per the video. Appreciate the prompt response!

The button was temporarily removed but is now back! (It might take a day or two from the time you see this comment for the button to re-appear.) It has been moved to the editor, next to the "Publish changes" button.

@@PlaidInc thanks! i saw that it was also the the URL so just used that

You can allow users to add or remove accounts on an Item via Update Mode. However, there is no way to delete the transactions subscription from the Item without deleting the entire Item.

Fixed! Thanks for pointing this out.

Your legal entity name, if you don't have a separate legal entity, would just be your name. Using or not using Hosted Link has no impact on whether you need to provide this information. If you meant the legal entity *identifier* (LEI), you can get one from one of the organizations listed here: www.gleif.org/en/about-lei/get-an-lei-find-lei-issuing-organizations . While you are not strictly required to provide an LEI, in the future, it may be necessary to have an LEI to obtain data from certain institutions, so we generally recommend providing an LEI to avoid any disruptions in connectivity. Since you are using Plaid for personal access to your own data rather than a commercial use case, it may make sense for you to proceed without an LEI at this point, and only apply for one later if you find it becomes necessary.

Going.Plaid is a community-supported library and Plaid support can't help with support or troubleshooting for issues specific to that library. For any Going.Plaid questions, you can open an issue on the GitHub repo at github.com/viceroypenguin/Going.Plaid/issues

Plaid Link is the entire Plaid-owned UI that is used for end user interaction, including the Plaid-hosted username and password pane, but also many other pages such as the consent pane, the account select pane, any product-specific panes required for flows such as micro-deposit based verification or identity verification, etc. For institutions that use OAuth, the institution-owned OAuth page is launched from within Plaid Link, and the end user is returned to Plaid Link after the institution's OAuth flow is complete.

@@PlaidInc what is the pros and cons in using the plaid-hosted username and password pane vs the OAuth?

If an institution has an OAuth connection available for Plaid to use, Link will automatically use OAuth; if it does not, Link will use the Plaid-hosted username and password field.

@@PlaidInc how secure is the plaid-hosted username and password field?

It is highly secure. For more concrete details on Plaid's information security program, see plaid.com/safety and security.plaid.com/.

sandbox btw

The instructions should more or less just work for many Windows users, but if they don't, we recommend using WSL, Cygwin, or something similar.

To get the public token without using callbacks, you can use the /link/token/get endpoint. See plaid.com/docs/api/link/#linktokenget for more details.

Plaid doesn't have official support for Flutter, but there is a community-supported Flutter package you can use: github.com/jorgefspereira/plaid_flutter

Plaid Statements returns the statement PDF exactly as provided by the financial institution. If the bank includes copies of checks written as part of the account statement PDF, then the check copies will be included. If the bank doesn't do this, then it won't.

If you're talking about the data in the video, Todd either used different test Items when demonstrating the /transactions/sync and /transactions/recurring/get endpoints, or didn't show all the results from every /transactions/sync call. In real life, the transaction_ids for /transactions/recurring/get will always match up to transaction_ids that have been or will be returned by /transactions/sync.

@@PlaidInc If that works irl then great, but while I've been testing in sandbox mode they don't seem to match up. For example, in sandbox mode, one of the SparkFun transaction id's that I get from /transactions/sync ends with 8ZP3, but that's not in the array of transaction id's from /transactions/recurring/get. The transaction id's that I see from the SparkFun recurring transaction ids array end in NnQm, nqoK, and oMJ9

We weren't able to reproduce this behavior via internal testing -- I recommend checking to make sure you are using the same access token for both endpoints and that the transaction is associated with the account id used in the call for /transactions/recurring/get. If you do end up seeing this behavior in real life (non-Sandbox) behavior, please file a support ticket via the Plaid Dashboard.

There is no official support for Expo - it is recommended you eject from Expo to use the Plaid SDK, or use Hosted Link (plaid.com/docs/link/hosted-link/).

Typically a few business days; potentially longer if you're applying for a product that has special compliance requirements, like Transfer. We recommend checking your spam folder, or, if it's been more than 2-3 weeks, contacting sales: plaid.com/contact/

Typically in a real app you would not use client side storage for persistent storage of transactions data. First, transactions data returned by the transactions endpoints can include PII and sensitive information, which must always be stored securely. See ofdss.org/#documents for recommendations on how to securely handle data from the API. Secondly, in many real world use cases for transactions it doesn't make sense to store this data on the client side, as you'll typically want to persistently associate this data with an end user across devices and often perform some kind of server-side processing or analysis of this data.

@@PlaidInc that makes sense, thakn you!

There was a bug in which users who needed to enable MFA were not getting appropriate error messages. It should now be resolved. Enabling MFA should allow you to proceed.

Routing number is common in the US, not specific to Plaid. In the US, the combination of a bank-specific routing number and an account number together is used to send money domestically, sort of similarly to how an IBAN would be used in Brazil when making a wire transfer.

For an app just for yourself, with no other users, you can have a minimal frontend, using something like Hosted Link (plaid.com/docs/link/hosted-link/) or the locally hosted frontend that comes with the Postman collection (github.com/plaid/plaid-postman?tab=readme-ov-file#making-api-calls-with-real-data-in-production). Once you've obtained a public token that you can exchange for an access token, the process of making API calls is basically the same regardless of whether you have multiple users or just one user. Note that, starting in late 2025, it's anticipated you'll need to refresh your access token annually using update mode.

⁠@@PlaidIncis there a tutorial out there for a hosted link? I’m very new to programming and I’m having issues following this video on windows, but I also just want an inexpensive way to automate only my finances.

There is no tutorial currently available for Hosted Link. If you're having trouble with building your own app, you can also try one of the great Plaid-powered financial management apps out there, like Rocket Money, YNAB, Albert, or Copilot: plaid.com/discover-apps/