How pluggyai/meu-pluggy works
MeuPluggy is documented as a consumer app for connecting financial accounts, reviewing and exporting financial data, and managing third-party consent. Its developer-access flow authorizes a developer application to retrieve data through Pluggy’s API. The repository tree provides no application source, so this is a README-based product map; implementation paths are unavailable, and edges describe only documented relationships.
Components 14
Consumer account data
- MeuPluggy app
- Bank connection
- Account information
- Data backup
- Data export
Consent management
- Consent tracking
Developer access
- Developer portal
- Development app
- MeuPluggy OAuth
Other components
- MeuPluggy user
- Financial institution
- Third-party apps
- Developer
- Pluggy API and SDKs
Connections 16
- MeuPluggy user → MeuPluggy app: signs up
README.md - MeuPluggy user → Bank connection: starts connection
README.md - Bank connection → Financial institution: authorizes access
README.md - Financial institution → Account information: provides data
README.md - MeuPluggy app → Account information: displays
README.md - MeuPluggy app → Data backup: backs up
README.md - MeuPluggy user → Data export: exports data
README.md - MeuPluggy user → Consent tracking: reviews consents
README.md - Consent tracking → Third-party apps: tracks sharing
README.md - MeuPluggy user → Consent tracking: revokes access
README.md - Developer → Developer portal: creates app
README.md - Developer portal → Development app: configures connector
README.md - MeuPluggy user → MeuPluggy OAuth: authorizes account
README.md - Development app → MeuPluggy OAuth: links account
README.md - MeuPluggy OAuth → Pluggy API and SDKs: enables data access
README.md - Pluggy API and SDKs → Account information: provides access
README.md