George

**Judgement:** A focused, powerful automation tool for George (Erste Bank / Sparkasse Austria) users who need programmatic access to account, transaction, and portfolio data. Very suitable for technically proficient users with this specific bank; not applicable outside that ecosystem. **What it does well:** - Automates login/logout and fetches accounts, transactions, and portfolios via Playwright. - Provides JSON output ideal for scripts, integrations, and financial workflows. - Supports advanced flows like data carrier upload and signing (e.g., payment batches). - Manages session state locally with restrictive permissions and encourages explicit logout to reduce residual auth risk. **Key risks / limitations:** - Limited to George (Erste Bank / Sparkasse Austria); not a general banking connector. - Depends on George’s web UI; layout or flow changes can break automation and reduce reliability. - Requires handling highly sensitive banking credentials; misconfigured environments, shared machines, or weak OS security can still expose data despite the tool’s restrictive permissions. - Playwright and browser setup may be non-trivial for non-technical users. **Recommended scenarios:** - Developers, power users, or small businesses using George who want automated, scriptable exports of balances, transactions, and portfolios into their own tools. - Automated payment workflows using George’s data carrier interface (upload + sign) where manual web interaction is currently a bottleneck. - ETL or data-pipeline contexts where JSON output from online banking must be periodically fetched and processed under controlled, secure conditions.