The elevator pitch was always clean: tell an AI what app you want, watch it appear, send someone the link. Simple enough. What Stockholm's Lovable hadn't cracked—at least not until mid-April—was the messier question of what happens when you actually want to charge for the thing you just built in a chat window.
That gap has now closed, perhaps more completely than even the platform's founders anticipated. Lovable, the so-called "vibe coding" startup that raised a $330 million Series B in December 2025 at a $6.6 billion valuation, now lets users embed payments, configure pricing tiers, and launch paid products in the same conversational thread where they're building the software itself. No toggling between dashboards. No hunting for Stripe API documentation at 2 a.m. Just describe what you need, and the platform scaffolds the checkout flow.
Whether that simplicity holds under real-world pressure is another matter entirely.
Payments as Part of the Conversation
The feature, which quietly rolled out in mid-April according to Lovable's documentation and community channels, integrates both Paddle and Stripe directly into the chat interface. A user can type something like "add three subscription tiers at $9, $29, and $99 per month," and Lovable generates the checkout pages, customer portals, database schemas with row-level security, and webhooks to track payment events.
Choose Paddle, and you get merchant-of-record infrastructure across more than 150 countries—useful if you're launching globally and don't want to navigate VAT compliance yourself. Choose Stripe, and you have more flexibility for subscriptions, one-time purchases, and invoices. Pick one per project; there's no mixing providers. Digital goods work immediately. Physical products require Lovable's separate Shopify connector, introduced last October with the same conversational setup.
There's no additional fee from Lovable for the privilege—users pay standard processor rates—and products sync automatically to live environments when published. The frictionless pitch is evident: founders testing MVPs or side projects don't need to wire up payment infrastructure manually, a process that typically involves reading developer docs, setting environment variables, and praying the webhook endpoints don't break in production.
For a platform already processing what the company claims are 100,000 new projects daily, payments represent more than a feature—they're a threshold. Projects that can collect revenue cross over from prototype to business. That distinction matters, especially for a company positioning itself as the last piece of software infrastructure anyone will need.
The Bigger Gambit
Lovable's payments layer follows a pattern the company introduced in March: pushing the chat interface beyond code generation to handle adjacent operational tasks. Users now generate invoices, pitch decks, and analytics dashboards in the same session where they're adjusting UI components or debugging edge cases. The framing—"from idea to investor-ready" in a single conversation—felt like hyperbole until the payment rails went live. Now it's at least plausible.
Still, the integration requires some trust in what's happening under the hood. Setup runs through Lovable's connector system. For Stripe, users link their Supabase backend (Lovable's default database choice), paste in a Stripe secret key via an encrypted field, then describe payment flows in plain language. Lovable handles the rest: generating Supabase Edge Functions for checkout logic, creating database access controls, rendering storefronts or pricing pages.
Before accepting real transactions, Lovable runs compliance checks—scanning for privacy policies, terms of service, refund disclosures. Products created in sandbox mode sync to live dashboards on publish, though the documentation warns that manual edits in Stripe or Paddle can cause ID mismatches. Discounts don't auto-sync, a detail that might trip up founders who expect everything to stay perfectly aligned.
There's also a built-in payment dashboard inside Lovable, webhook handling for events like successful charges or failed renewals, and sandbox testing that doesn't require connecting external accounts. The abstraction is deliberate: users shouldn't need to understand what a webhook is, let alone configure one.
That's either liberating or terrifying, depending on your appetite for control.
The Competitive Field Is Crowding
Lovable isn't pioneering this alone. Replit, which raised its own mega-round last year and courts a similar audience of non-traditional developers, added Stripe Integrated Payments in November. Replit's Agent can configure subscriptions and sync transactions to a database, though the feature is oddly limited to Free and Core tiers—Teams accounts don't get access. Bolt, another AI code generator, rolled out Stripe support in 2025 with a similar "payments made easy" message, though community feedback suggests users often fall back on manual Payment Links and custom webhook setups when things get complicated.
Cursor, the AI-powered code editor that's found an audience among professional developers, doesn't offer native payment infrastructure at all. Users integrate Stripe themselves or lean on templates—closer to traditional development workflows than the zero-to-launch platforms Lovable and Replit are assembling.
The real differentiation isn't just that Lovable added payments. It's how the feature fits into what the company calls its "single conversation" thesis. TechCrunch noted in December 2025 that Lovable planned to "flesh out infrastructure needed—like databases, payments, hosting—to build full-fledged applications." The payments rollout, alongside earlier launches like domain purchasing and email capabilities, suggests the company is methodically checking boxes.
Whether the vision scales depends partly on adoption velocity—and the numbers Lovable has disclosed are, if accurate, staggering. The company said in December 2025 it had hit 25 million projects in its first year, with 6 million daily visits and 200 million monthly visits to Lovable-built sites. Bloomberg reported $200 million in annual recurring revenue as of November 2025. A Stripe case study claims Lovable reached $400 million ARR within 14 months—though that figure is vendor-reported, lacks a clear recent date of confirmation, and hasn't been independently verified.
Security Tensions
Payments introduce risk, especially for a platform that automates so much of the underlying architecture. Lovable has already faced scrutiny on this front. In May 2025, Semafor reported that misconfigurations in some Lovable-built apps left user data exposed, prompting the company to add automatic security checks.
Lovable has since tightened its posture. In March, the company launched penetration testing via Aikido, offering dynamic scans that generate audit-ready reports for $100 per test. On April 13—the same day the payments feature went live in community channels—Lovable published a guide titled "How to build a safe, scalable business on Lovable," covering role-based access controls, error handling, and production hygiene.
The compliance checks tied to payments are part of that effort. But the chat-driven model means users may not fully understand what's being generated beneath the abstraction layer. That creates tension: for founders comfortable trading control for speed, the opacity is the point. For those who want to audit every line of backend logic, the platform may feel like a black box.
What's Actually at Stake
Lovable's underlying bet is that the market for software creation is shifting—from people who want to learn to code to people who want to ship products. Payments represent a gate. Startups that can't accept money don't graduate from side project to sustainable business. By collapsing that step into the same interface where the product gets built, Lovable lowers the activation energy for monetization in a way that could appeal to SaaS entrepreneurs, no-code builders, and founders testing ideas without technical co-founders.
The timing aligns with the company's December 2025 fundraise—a $330 million Series B led by CapitalG and Menlo Ventures at that $6.6 billion valuation, with participation from Nvidia, Salesforce, Databricks, and others. Fortune reported that CEO Anton Osika is positioning Lovable as infrastructure for a world where describing software replaces writing it. The payments feature is a tangible step in that direction, turning what was primarily a prototyping tool into something closer to a full-stack platform.
Replit and Bolt are moving in parallel. The question now isn't whether AI code generators will support payments—it's whether the conversational interface can handle the edge cases, compliance nuances, and international complexity that come with real revenue. Lovable's answer, for now, is Paddle for global coverage and Stripe for flexibility, both wrapped in chat.
What remains to be seen is how far that abstraction stretches before founders need to drop into code—or whether, for a growing segment of users, they never have to at all. The wager is considerable. So is the valuation riding on it.
