Plaid Production Readiness

1. Complete all integration requirements in sandbox
2. Apply for development access to test with real banks
3. Verify integration works with real institutions in development
4. Complete the production access application
5. Address any review feedback from Plaid
6. Migrate configuration and deploy to production

Planned content:

• Sandbox to development migration checklist
• Development to production application requirements
• Plaid production access application walkthrough
• Compliance checklist (privacy policy, ToS, data handling)
• Technical requirements (webhook HTTPS, OAuth redirect, error handling)
• Environment variable management across environments
• Load testing and rate limit planning
• Monitoring and alerting setup for production
• Launch day checklist

Key References

• Production access
• Going live checklist
• Plaid Dashboard

Example Interaction

User: "My Plaid integration works in sandbox. What do I need to do to go live?"

Agent:

1. Walks through the development access application
2. Lists technical requirements (HTTPS webhook, error handling, update mode)
3. Provides compliance checklist (privacy policy, data retention, user consent)
4. Shows environment migration steps
5. Notes: "Production approval typically takes 1-2 weeks. Start the application early."

MCP Usage

Common Pitfalls

1. Skipping development - test with real banks in development before applying for production
2. Missing error handling - Plaid reviews require proper ITEM_LOGIN_REQUIRED handling
3. No webhook HTTPS - production webhooks require HTTPS endpoints
4. Incomplete privacy policy - must disclose Plaid data usage to end users

See Also

• Plaid Sandbox Testing - complete sandbox testing first
• Plaid Security Best Practices - security requirements for production
• Plaid Error Handling - required error handling for approval