Liberapay is a production web application for recurrent, voluntary donations. It runs as a Python/PostgreSQL monolith built on the Pando/Aspen 'simplates' framework, where filesystem routes are `.spt` files mixing request handling, Python logic, and template/JSON/CSV output. Users can be individuals, organizations, teams, or communities; they receive tips, maintain funding goals, manage payouts, and interact through profiles, widgets, invoices, and admin tools. The system integrates Stripe (cards and SEPA Direct Debit) and PayPal for payins, schedules automatic renewals, groups tips into payments, and runs a weekly 'payday' batch process that settles funds to recipients and records transfers. Entry points include the WSGI app (`app.py` -> `liberapay.main:website`), cron jobs (`liberapay/cron.py`, `liberapay/payin/cron.py`), payment webhooks (`/callbacks/stripe`), and numerous `.spt` HTTP routes. The data model lives in PostgreSQL with custom composite types for currency amounts, triggers, constraints, and a large migration history in `sql/migrations.sql`. Core money flows are: user sets tip -> `scheduled_payins` -> provider charge -> `payin_transfers` -> payday settlement / payout. External dependencies include Stripe, PayPal, AWS SES/S3, Sentry, Fixer.io exchange rates, and a set of OAuth identity providers (GitHub, GitLab, Twitter, Twitch, Mastodon, etc.). There is no data_research character: the analytical views and exports are operational features of a transactional platform. The codebase is actively maintained but shows moderate technical drift: it relies on niche frameworks (Pando/Aspen), vendored Bootstrap 3, legacy Mangopay remnants in migrations, and many VCR-recorded integration tests that may become stale as external APIs evolve. Its strongest engineering exists in currency handling, encrypted fields, OAuth abstraction, and database-level money types, though the custom web framework and heavy raw SQL make most of the codebase difficult to reuse outside this project.