Founder Identity Verification: Inside the Plaid and Meow Integration

The Plaid identity verification step is the single human-touch moment in the agentic formation flow. Everything else runs through the AI agent. The identity step does not, by design.

This post covers what Plaid Identity Verification captures, why the verification step lives outside the LLM context, how the token exchange architecture keeps the founder's personally identifiable information away from the model, what the flow looks like for international founders without a US SSN, and how the captured data maps to the FinCEN beneficial ownership reporting framework.

Why the Identity Step Lives Outside the LLM

When I formed my Delaware LLC inside Claude (covered in the LLC walkthrough), the agent asked me four questions and then handed me off to Plaid for the beneficial owner verification. The handoff was deliberate.

The AI agent on Claude, ChatGPT, Cursor, or Gemini is a useful interface for everything that does not require my SSN, my driver's license, or my biometric data. The agent can read documentation, file forms, prepare stock purchase agreements, and submit applications to the IRS and to the partner bank. The agent should not be in possession of my SSN.

Two reasons.

The first is regulatory. The partner bank's Customer Identification Program (CIP) requirements come from the USA PATRIOT Act and the implementing regulations at 31 CFR Section 1020.220. The bank must verify the customer's identity through a specific set of data points (legal name, date of birth, residential address, government-issued ID number) and must retain that data for five years after account closure. The verification process needs to happen in a system the bank controls or contracts for, not in an LLM context window governed by different terms.

The second is security. An LLM is not a secure store for PII. The model's context window can be persisted in logs, can leak into model fine-tuning if mishandled, and is accessible to the conversation's participants in ways that PII data should not be. Keeping the SSN out of the model's context is the right default.

Plaid sits between the LLM and the founder's PII. The agent calls Plaid's Identity Verification API; Plaid handles the actual data collection and the bank's CIP requirements; Plaid returns a verification token to the agent. The agent uses the token to confirm verification status. The agent never sees the underlying data.

What Plaid Identity Verification Captures

The Plaid Identity Verification flow captures four data sets, in this order.

Document verification. The founder takes a photo of a government-issued ID. Plaid supports US driver's licenses, US state IDs, US passports, and international passports for non-US founders. The image is captured on the founder's phone or webcam. Plaid runs OCR on the document, validates that the document matches the expected template for the issuing authority, and extracts the name, date of birth, document number, and address.

Selfie capture. The founder takes a selfie. Plaid uses biometric matching to confirm that the person in the selfie matches the photo on the ID. The selfie capture step prevents the use of stolen or photographed-from-screen IDs.

Identity attributes. The founder provides the SSN (for US founders) or the equivalent national tax identifier (for non-US founders). Plaid validates the SSN against the issuing-authority records and against database checks for synthetic identity flags.

Address verification. The founder provides the current residential address. Plaid validates the address against the standard databases (USPS for US addresses, equivalent national mail registries for international addresses).

All four data sets are captured on the founder's device, transmitted over TLS to Plaid's systems, and stored in Plaid's compliant environment. None of the data passes through the LLM context window.

The Token Exchange Architecture

The handoff between the LLM and Plaid is a token exchange.

The agent calls Plaid's Identity Verification API with an empty request (the agent does not have the founder's identity data to populate the request). Plaid returns a verification link and a verification token reference. The agent surfaces the link to the founder.

The founder completes the verification on their device. Plaid stores the captured data in its own systems and sends a webhook back to the partner bank's compliance systems with the verification token reference and the verification status.

The bank's compliance systems run their CIP checks against the verified data, return a pass-or-fail status, and notify the agent with the result. The agent surfaces "verification complete" to the founder and proceeds to the next step in the formation flow.

The agent's only knowledge of the verification is the token reference, the pass-or-fail status, and the timestamp. The underlying SSN, driver's license, and selfie never enter the agent's context. The LLM never holds them.

This is the structural answer to the question "what happens to my data when an AI agent handles my company formation?" The data does not go through the agent. The agent is the orchestrator. The data sits with the regulated systems that need it. The architectural pattern is the same one covered in the Meow MCP server post: the agent calls the API; the regulated systems do the work that needs regulating; the model holds tokens, not secrets.

The International Founder Path

The default Plaid Identity Verification flow assumes a US founder with a US SSN. The international founder path runs through a variant of the same flow.

For non-US founders, Plaid Identity Verification accepts international passports as the document verification step. The selfie capture and the address verification work the same way, with the address validated against the founder's country of residence.

The SSN-equivalent step varies by country. For founders forming a US entity from outside the US, the formation flow accommodates two paths.

First, founders who already hold a US Individual Taxpayer Identification Number (ITIN) can provide it in the SSN field. The flow treats it equivalently for the CIP check.

Second, founders without an ITIN can complete the formation with passport verification and address verification only. The partner bank's CIP review handles the case-by-case decision on whether passport verification is sufficient for the operating profile. For most international founders forming a US C Corp or LLC with the agent-first flow, the passport-only verification is acceptable.

The ITIN itself is applied for separately through IRS Form W-7. The Meow agent does not apply for the ITIN on the founder's behalf; the application is a separate workflow with an IRS Acceptance Agent or a Certifying Acceptance Agent. A dedicated post in the same Batch 3 series covers the full international founder path for forming a Delaware C Corp from outside the US (including the ITIN versus SSN considerations for the responsible party on the EIN application and the partner-bank compliance constraints for non-resident founders).

What Happens If Verification Fails

Common verification failures and what the agent does with each.

Document image quality failure. The captured ID photo is blurry, glare-affected, or partially obscured. Plaid surfaces a retry prompt. The founder retakes the photo. Most quality failures clear on retry.

Selfie mismatch. The biometric matching score between the selfie and the ID photo is below the confidence threshold. Plaid surfaces the failure status; the agent surfaces a retry prompt. Recurring mismatch routes the verification to manual review with Plaid's compliance team.

SSN validation failure. The SSN provided does not match the authoritative records or trips a synthetic identity flag. Plaid surfaces the failure status; the agent routes the founder to the partner bank's compliance team for manual review.

OFAC or sanctions hit. The founder's identity matches a person on the OFAC Specially Designated Nationals list or on a related sanctions database. The verification blocks immediately. The agent surfaces the block status; the founder works with the partner bank's compliance team directly.

Address verification failure. The provided address does not validate against the postal authority. Plaid surfaces a retry prompt with the closest matched address as a suggestion. Most address failures clear on retry with the corrected address.

The agent does not retry failed verifications silently. Every retry surfaces to the founder and counts against the partner bank's verification attempt limit.

FinCEN Beneficial Ownership Reporting

The data captured in Plaid Identity Verification maps to the data points that a US entity may need to report to FinCEN under the Corporate Transparency Act.

The FinCEN Beneficial Ownership Information (BOI) Report framework requires certain US entities to disclose their beneficial owners (any individual who owns 25 percent or more of the entity, or who exercises substantial control over the entity) to FinCEN. The disclosure includes legal name, date of birth, current residential address, and an identifying number from an acceptable government-issued ID.

The Plaid Identity Verification flow captures these same data points as part of the partner bank's CIP review. For entities subject to BOI reporting, the captured data is available to populate the BOIR; the Meow agent does not file the BOIR on the founder's behalf, but the data is in hand.

The applicability of the BOI reporting requirement to any specific entity depends on the entity's classification, its size, and the prevailing regulatory enforcement guidance. The Meow agent does not provide tax or legal advice on BOI reporting; the founder's counsel handles that determination.

Privacy and Data Handling

Plaid retains the verification data per its Identity Verification data handling and retention policy. The partner bank retains the data per CIP requirements (the regulations at 31 CFR Section 1020.220 require retention for five years from account closure). The Meow agent retains the verification token reference and the pass-or-fail status; it does not retain the underlying PII.

Plaid's data handling is governed by Plaid's privacy policy and by the regulatory regime that applies to Plaid as a covered financial entity. The partner bank's data handling is governed by the bank's privacy policy and by the federal banking regulations (Gramm-Leach-Bliley Act, Bank Secrecy Act, USA PATRIOT Act).

The LLM context window never holds the SSN, the driver's license image, the selfie, or the date of birth. The LLM holds the verification token reference and the verification status. The conversation transcript, the model's logs, and any downstream uses of the conversation data do not contain the founder's PII.

Frequently Asked Questions

Does the AI agent see my SSN? No. The AI agent on Claude, ChatGPT, Cursor, or Gemini never receives the SSN, the driver's license image, the selfie, or any other PII. Plaid Identity Verification handles the data collection and stores it in Plaid's compliant environment. The agent receives a verification token reference and the pass-or-fail status only.

What does Plaid Identity Verification capture? The flow captures document verification (a photo of a US driver's license, US state ID, US passport, or international passport), a selfie matched against the document photo, the SSN or equivalent national tax identifier, and the founder's current residential address. The verification runs on the founder's device and sends the data over TLS to Plaid.

Can I form a US entity without a US SSN? Yes. Plaid Identity Verification accepts international passports for document verification. Founders without a US SSN can complete the flow with passport verification and address verification, and the partner bank's CIP review decides whether the verification is sufficient for the operating profile. The ITIN, if needed, is applied for separately through IRS Form W-7.

What happens if the verification fails? Common failures (image quality, selfie mismatch, address mismatch) surface as retry prompts. Recurring failures route to Plaid's compliance team for manual review. SSN validation failures and OFAC hits route to the partner bank's compliance team directly. The agent does not retry failed verifications silently.

Does this satisfy FinCEN beneficial ownership reporting? The data captured in Plaid Identity Verification covers the same data points that an entity may need to report to FinCEN under the Corporate Transparency Act (legal name, date of birth, residential address, government-issued ID number). The Meow agent does not file the BOI Report on the founder's behalf; the founder's counsel handles the BOIR determination and filing.

How long does Plaid retain my verification data? Plaid retains the verification data per its Identity Verification data handling policy. The partner bank retains the data per Customer Identification Program rules (31 CFR Section 1020.220 requires five years from account closure). The Meow agent retains only the verification token reference and the pass-or-fail status; it does not retain the underlying PII.

Can I use the same Plaid verification for multiple entities? Yes. The Plaid identity verification carries forward from the first entity on a Meow operator profile. The operator's verified profile is reused for subsequent entities; the agent does not re-prompt for SSN, driver's license, or selfie data on additional entities under the same profile.

Try It Yourself

Open Claude. Add the Meow MCP server.

claude mcp add --transport http meow https://mcp.meow.com/cli

Paste the formation prompt. Pick your entity type and state. When the agent reaches the beneficial owner question, complete the Plaid identity verification on your phone. The verification step takes the founder's attention; everything before and after runs on the agent.

If you would rather start with the dashboard instead of the terminal, apply at meow.com. The identity verification step is the same on both paths.

Banking services are provided by Grasshopper Bank, N.A., Member FDIC.