Hey Casper, great question—this is super common when teams first dive into Plaid integration! Let me break down your options clearly:

1. 优先选择：使用Plaid官方的预构建界面（Plaid Link） #

Plaid provides a ready-made, fully functional UI flow called Plaid Link that handles everything related to connecting a user's bank account. This is the recommended approach for most teams because:

• It takes care of all the heavy lifting: bank search/selection, multi-factor authentication (MFA), error handling, and compliance with financial regulations.
• You don’t need to design or build any of the account connection UI yourself—just embed Link into your existing onboarding/registration flow with a few lines of code.
• It’s optimized for user conversion (Plaid has spent tons of time testing what works best for users to successfully link their accounts).

To use it, you’ll generate a link_token via your backend using Plaid’s API, then initialize Link in your frontend (iOS, Android, or web) using their SDK. When the user completes the Link flow, you’ll get back a public_token that you can exchange for an access_token on your backend to start accessing account data.

2. 自定义UI（仅当你有特殊需求时） #

If you need full control over every aspect of the UI (e.g., matching your app’s exact design system down to the pixel), Plaid does let you build a custom flow using their core API endpoints. However, this is way more work:

• You’ll have to design and build all UI components for bank selection, input fields for credentials, MFA prompts, error states, etc.
• You’re responsible for handling all compliance requirements and ensuring the flow meets Plaid’s security standards.
• You’ll need to interact directly with endpoints like /link/token/create, /accounts/get, and various authentication endpoints instead of using the simplified Link flow.

For your current situation—where you’ve already built most of your onboarding/registration UI—Plaid Link is almost certainly the right choice. You can embed it as a step in your existing flow (e.g., right after the user finishes registration) to keep things seamless without reinventing the wheel.

内容的提问来源于stack exchange，提问作者Casper Yonel