# Hacktoberfest 2025: Build the Future of Billing & Payments with Dodo Payments > Join Dodo Payments for Hacktoberfest 2025: contribute to Billing SDK, Storefront, Customer Portal, adapters, docs, and earn exclusive swag. - **Author**: Ayush Agarwal - **Published**: 2025-09-29 - **Category**: Resources - **URL**: https://dodopayments.com/blogs/hacktoberfest-2025-dodo-payments --- October is for open source. This Hacktoberfest, we're inviting developers, writers, and designers to help shape the Dodo Payments ecosystem. Our [Billing SDK](https://billingsdk.com/), [Customer Portal](https://github.com/dodopayments/dodo-customer-portal), [Storefront](https://github.com/dodopayments/dodo-store-front), framework adapters, plugins, developer demos and [documentation](https://docs.dodopayments.com/introduction). Whether you ship a one-line fix or a full new adapter, your contributions will power thousands of SaaS and AI products around the world. Contributions can be small or large, experimental or production-grade. Every improvement, clearer docs, a new example, a bugfix in an SDK helper lowers integration friction for teams building on top of [Dodo Payments](https://dodopayments.com/). ## Hacktoberfest Projects: Billing SDK, Customer Portal, Storefront, Adapters, Checkout Demos,, and Docs Dodo Payments makes it easier for SaaS, AI, and digital businesses to launch and scale globally: [subscriptions, one-time charges](https://dodopayments.com/blogs/one-time-vs-subscription-saas-pricing), [usage-based](https://dodopayments.com/blogs/implement-usage-based-billing) and outcome-based billing, tax handling, payment methods, checkout flows, and more. For Hacktoberfest we're focused on plumbing, examples, and docs that make the developer experience better and faster: > We designed Dodo's API for the solo developer building at midnight. If you need a team of payment engineers to integrate, we have failed at our job. > > \- Ayush Agarwal, Co-founder & CPTO at Dodo Payments - **Billing SDK:** Modern, typed client libraries and helpers so teams can integrate Dodo quickly and idiomatically. - **Customer Portal:** Merchant-facing portal for subscriptions, invoices, license keys, and billing profile. - **Storefront:** Customer-facing storefront for product listings and checkout hand-off to Dodo; built with Next.js, shadcn/ui, and Tailwind. - **Adapters & Plugins:** Drop-in integrations for popular frameworks, CLIs, and tooling. - **Checkout Demos:** Realistic, copy-pasteable examples that show one-time, subscription, and metered flows. - **Docs & Guides:** Crisp, friendly documentation and migration guides that remove friction for developers and operators. ### Repositories (pick one or many) - Billing SDK: [https://github.com/dodopayments/billingsdk](https://github.com/dodopayments/billingsdk) - Customer Portal: [https://github.com/dodopayments/dodo-customer-portal](https://github.com/dodopayments/dodo-customer-portal) - Storefront: [https://github.com/dodopayments/dodo-store-front](https://github.com/dodopayments/dodo-store-front) - Docs: [https://github.com/dodopayments/dodo-docs](https://github.com/dodopayments/dodo-docs) - Framework Adapters: [https://github.com/dodopayments/dodo-adapters](https://github.com/dodopayments/dodo-adapters) - Checkout Demo: [https://github.com/dodopayments/dodo-checkout-demo](https://github.com/dodopayments/dodo-checkout-demo) - Dodo Payments Migrate: [https://github.com/dodopayments/dodo-migrate](https://github.com/dodopayments/dodo-migrate) ## Rewards: Dodo "Tracks" Swag for Hacktoberfest Contributors Major contributors will receive limited Dodo "Tracks" swag packs: t-shirts, caps, and stickers. We'll share the design preview on our socials and this post soon. ### How we pick recipients (transparent and fair) - **Impact:** Is the contribution used by developers or merchants right away? - **Completeness:** Are there tests, docs, and examples? - **Collaboration:** Was the contributor responsive in reviews and helpful in discussion? - **Scope:** Multiple small PRs or one large, well-scoped PR, both count. We'll also maintain a Hall of Fame and give shout-outs across our channels. \[Swag preview will appear in the repo and our social channels.\] ## Starter Issues & High-Impact Contribution Ideas **1) billingsdk** - Add a typed method or enum for a recently added API field. - Improve retry/backoff and idempotency helpers. - Add framework-agnostic examples (Node/TS, Python, Go, PHP). - Strengthen error types and SDK exceptions. - Improve tree-shakeability and reduce bundle size. - Add CI checks (lint, typecheck, tests) and coverage badges. **2) dodo-customer-portal** - Improve subscription actions UX (upgrade/cancel) with optimistic updates and a11y. - Add robust invoice download states (loading, retry) and error boundaries. - Expand `next-intl` message coverage and add basic locale tests. - Add license key filters and search in the list view. **3) dodo-store-front** - Optimize product grid LCP with skeletons and Next/Image WebP sources. - Improve SEO/OG metadata and social share images. - Strengthen a11y and keyboard navigation for product cards and quantity control. - Add Shadcn UI polish (focus states, pagination, empty states) and loading fallbacks. **4) dodo-adapters** - Create a new adapter: Astro, Remix, Nuxt, SvelteKit, Flask, FastAPI, Laravel. - Add SSR-friendly helpers and middleware for webhooks and session handling. - Provide example apps per framework with auth + checkout wiring. - Write migration notes for each framework version. **5) dodo-checkout-demo** - Expand the demo to show one-time, subscription, and usage flows. - Add multi-currency and local payment methods toggles. - Improve UI/UX and accessibility (a11y). - Add Docker Compose for one-command local runs. - Seed data & a playground mode for quick testing. **6) dodo-migrate** - Import/migration scripts from [Stripe](https://dodopayments.com/blogs/stripe-billing-dodo-payments), [Paddle](https://dodopayments.com/blogs/paddle-alternatives), [Lemon Squeezy](https://dodopayments.com/blogs/top-5-alternatives-to-lemon-squeezy), etc. - Normalization and mapping helpers for common billing models. - Checklists and dry-run/diff modes. - Unit tests and large sample datasets (anonymized). **💡Tip:** We will label issues with `hacktoberfest`, `good first issue`, and `help wanted` across repositories. If you have an idea, open an issue first. We'll help scope it. ## How to Participate: 5 Simple Steps to Contribute **Choose a repo & find an issue** Pick one of the repositories listed above (Billing SDK, docs, adapters, checkout demo, ingestion blueprints, or dodo-migrate) and scan open issues. Look for labels like **hacktoberfest**, good first issue, or help wanted. 2. **Claim the issue and outline your approach.** Comment to say you'll work on it and add a 1-2 sentence plan so maintainers can confirm scope. 3. **Fork -> branch -> run locally.** Feature/ then follow the repo README to install and start the project. 4. **Implement code or docs and add tests.** Make focused commits, follow CONTRIBUTING.md, and include at least one test or docs snippet. 5. **Open a PR using the template.** Use the template, link the issue, explain what you changed and how to test it. ### If you get stuck Comment on the issue or ping the **#hacktoberfest** thread and a maintainer will help. ## Local Setup & Contribution Standards Each repo includes a README with prerequisites and local run instructions. - Use conventional commits **(**`feat:` **,**`fix:` **,**`docs:` **,**`chore:` **,**`refactor:` **)**. - Run lint, typecheck, and tests before pushing. - Add or expand unit tests and include at least one docs snippet per feature. - Keep PRs focused, large features are welcome but split logically. - Respect the repo's license and Code of Conduct. ## Hacktoberfest 2025 Timeline & Key Dates **Oct 1-31, 2025 (local time):** Hacktoberfest contribution window. - **Early November:** Swag selection & Hall of Fame updates. - **Mid November:** Swag shipping begins. We'll post updates in the repos and our community channels as work progresses. ## Community & support - Dedicated `#hacktoberfest` thread in our discord server (details in each repo README). Joining link - [https://discord.gg/bYqAp4ayYh](https://discord.gg/bYqAp4ayYh) - Maintainer office hours; schedule announced in issues/Discussions. - For security-related reports, follow each repository's `SECURITY.md`. ## Ready? Get Started: Contribute to Dodo Payments This Hacktoberfest Hacktoberfest is the best time to improve the building blocks millions of developers rely on. Pick a repo, grab an issue, and start a PR. 🔗 One more time: - [https://github.com/dodopayments/billingsdk](https://github.com/dodopayments/billingsdk) - [https://github.com/dodopayments/dodo-customer-portal](https://github.com/dodopayments/dodo-customer-portal) - [https://github.com/dodopayments/dodo-store-front](https://github.com/dodopayments/dodo-store-front) - [https://github.com/dodopayments/dodo-docs](https://github.com/dodopayments/dodo-docs) - [https://github.com/dodopayments/dodo-adapters](https://github.com/dodopayments/dodo-adapters) - [https://github.com/dodopayments/dodo-checkout-demo](https://github.com/dodopayments/dodo-checkout-demo) - [https://github.com/dodopayments/dodo-migrate](https://github.com/dodopayments/dodo-migrate) See you in the PRs and in the Hall of Fame. ## FAQ ### Which Dodo Payments repositories are best for first-time Hacktoberfest contributors? The post recommends starting with issues labeled `hacktoberfest`, `good first issue`, or `help wanted` across repos like Billing SDK, docs, adapters, and checkout demos. These are typically scoped to be more approachable while still useful to the ecosystem. ### Can non-code contributions count for this Hacktoberfest campaign? Yes. The announcement explicitly invites writers and designers in addition to developers, and highlights docs, examples, and UX improvements as high-impact contribution areas. ### How does Dodo Payments decide who receives Hacktoberfest swag? Swag selection is based on impact, completeness, collaboration quality in reviews, and scope of contribution. The criteria are listed to keep selection transparent and fair. ### What should I include in my pull request to increase acceptance chances? Follow the repo template, link the issue, explain what changed, and include clear test or verification steps. The post also emphasizes running lint, typecheck, and tests before pushing. ### Where can I get help if I am blocked while contributing? You can comment directly on the issue or use the dedicated `#hacktoberfest` Discord thread mentioned in the article. Maintainers also share office-hour updates in issues and discussions.