# Improving Developers Experience at Dodo Payments > See how Dodo Payments improved developer experience with framework adaptors, Better-Auth integration, and 50+ app integrations for faster launches. - **Author**: Ananthu Vasudevan - **Published**: 2025-08-25 - **Category**: Resources - **URL**: https://dodopayments.com/blogs/developer-experience-dodo-payments --- [At Dodo Payments](https://dodopayments.com/), we've always believed that a smooth developer experience (DevEx) isn't just a "nice-to-have", it's core to our mission of making payments integration effortless for builders. Over the past couple of months, we've been steadily improving how developers interact with our platform. The result: A more polished, guided integration path. Instead of making engineers weave together raw [APIs and SDKs](https://docs.dodopayments.com/developer-resources/introduction), we now offer framework-specific adaptors and built-in integrations to popular tools. This means that whether you're on React, Nuxt, SvelteKit, or using WordPress, Zapier, HubSpot, or any of dozens of apps, you can connect in minutes, without reinventing the wheel. Here's a look at what we've been working on and why it matters. ## Framework Adaptors & Checkout Flow: Meeting Developers Where They Are To solve this, we created framework-native adaptors for the ecosystems you already use. Now, instead of manually coding each step of the payment flow, you can simply install Dodo Payments' adaptor package and drop in a few components. > A payment integration should take hours, not weeks. If your developers are reading documentation for days before writing the first line of code, the platform is not developer-first. It is developer-hostile. > > \- Ayush Agarwal, Co-founder & CPTO at Dodo Payments For example, our adaptors cover the full checkout flow, link the customer portal into your site, and even wire up [webhook](https://dodopayments.com/glossary/webhooks) endpoints automatically. The common tasks are handled for you: **Checkout flow setup:** create and manage payment links or subscriptions with one API call. **Customer portal integration:** embed Dodo Payments self-service billing portal in your app without hand-rolling OAuth or IFrames. **Webhook handling:** receive and verify payment events out of the box (so you don't have to write signature checks yourself). This saves time, reduces boilerplate, and ensures consistency across projects. We've also structured these packages cleanly with Rollup + TypeScript, so they're lightweight, typed, and easy to extend. ## The list of adaptors we have right now - Nextjs - Better-Auth - Nuxt - Express - Astro - Sveletkit - Hono - Remix - Tanstack - Fastify We'll keep adding to this list over time. By connecting directly with your existing stack, these adaptors eliminate hours of boilerplate coding and research while ensuring consistency across projects. Native integrations can be launched within hours, whereas building custom APIs often takes weeks or even months. With native adaptors, you can move faster and rely on far less custom code. ## Better-Auth Adaptor: Auth Meets Payments, Effortlessly We're particularly proud of our [Better-Auth adaptor](https://docs.dodopayments.com/developer-resources/better-auth-adaptor#better-auth-adapter), a specialized integration that blends authentication and payments into one smooth, type-safe experience. With this plugin: - **Customers are automatically created on sign-up:** when a new user registers in your app, the adaptor immediately creates a corresponding Dodo Payments customer behind the scenes. No extra API calls needed. - **Checkout flows are type-safe and map neatly using product slugs:** You can define products by slug like "premium-plan" instead of hardcoded IDs, and Better-Auth ensures the right Dodo product is used at checkout. The TypeScript types help catch mismatches early. - **Self-service portals are embedded directly in the auth flow:** After login, your users can access their billing portal (to update cards, view invoices, etc.) directly in your app with one component. - **Built-in webhooks with verification:** Events like payments, refunds, or subscription changes automatically. The plugin even verifies Dodo Payments webhook signatures for you, so you can trust the data - **Full TypeScript support ensures end-to-end safety.** From the client code to the server logic, everything is typed. This end-to-end safety means fewer runtime errors and clearer code. This means onboarding a new user instantly provides customer access, checkout capabilities, and secure event notifications, all in a unified, developer-friendly flow. ## External Integrations We recently launched an extensive array of external integrations across categories like messaging, workflow automation, CRMs, email tools, analytics platforms, and more. Each integration delivers: **Real-time notifications**--stay instantly informed about payment events in your tools of choice **Automated workflows**--trigger actions automatically, reducing errors and slashing manual effort. **Better visibility and insights**--with data flowing into your operational dashboards, you gain a clearer, unified view of your payment ecosystem ### Here's the current lineup (as of August 2025) - External integrations: WooCommerce, Framer, Figma, Raycast - Messaging platforms: Slack, Discord, Microsoft Teams - Workflow automation: Zapier, Windmill, Inngest - CRM systems: HubSpot, Close CRM - Email tools: Resend, Loops, SendGrid - Analytics platforms: Segment, Customer.io These integrations come with streamlined setup instructions and examples, making onboarding a breeze **What This Means for Developers** **1\. Time Saved, Code Simplified** Instead of building custom integrations for each tool, you can connect to an existing, supported integration in minutes rather than days. **2\. Consistency Across Stacks** With official integrations, behavior and documentation are consistent across tools. You can rely on predictable outcomes without fumbling through third-party plugins. **3\. End-to-End Visibility** Imagine a sale flows in, the right team is alerted, a CRM is updated, an email confirmation sends, and analytics capture the event, all without writing a line of integration glue code. **4\. Scalable and Secure** Each integration was built with reliability in mind, maintained by our team, with secure defaults, robust documentation, and best practices baked in. ## Automation and Support AI Another focus has been automating developer support. We've been working on custom AI assistants that: - Ground responses in official documentation - Provide precise code snippets instead of vague answers - Work across support channels like Discord and Intercom The goal here is consistency: whether a developer asks a question in the docs, on Discord, or via support tickets, they get the same accurate, actionable answer. ## Looking Ahead Improving DevEx isn't a one-off project, it's an ongoing investment. Over the coming months, we're focusing on: - Expanding adaptor coverage to more frameworks - Integrations with much more 3rd party applications(50+ in plan) At the end of the day, our north star is simple: make it ridiculously easy for developers to build with [Dodo Payments.](https://dodopayments.com/) ## FAQ ### Which Dodo Payments adaptor should I start with for a new app? Start with the adaptor that matches your framework, such as Next.js, Nuxt, Astro, or SvelteKit, because it covers checkout, portal access, and webhook wiring in one flow. That removes most of the boilerplate you would otherwise build manually. ### Does the Better-Auth adaptor create billing customers automatically? Yes. The post explains that when a user signs up, the adaptor creates the corresponding Dodo Payments customer in the background, so you do not need extra API calls for basic customer provisioning. ### Can I map checkout to product slugs instead of hardcoded product IDs? Yes, especially with the Better-Auth adaptor. You can use readable slugs like `premium-plan`, and typed mappings help catch mistakes earlier during development. ### What kinds of third-party integrations are already available? The article lists integrations across messaging, workflow automation, CRM, email, analytics, and external tools like WooCommerce and Framer. These are designed to trigger real-time notifications and automated actions without custom glue code. ### How does Dodo keep support answers consistent across docs and chat channels? The team is building AI support assistants that ground responses in official documentation and provide actionable snippets. The same approach is intended to work across docs, Discord, and Intercom for consistent guidance. --- - [More Resources articles](https://dodopayments.com/blogs/category/resources) - [All articles](https://dodopayments.com/blogs)