Commerce infrastructure is catching up to agentic development

Storefronts, checkout flows, and subscription logic are increasingly generated by AI agents working with tools like v0 and the Vercel CLI. That shift puts new pressure on the commerce stack underneath: if the setup and integration steps still require manual key retrieval and environment configuration, the agent's speed advantage evaporates before a single request is served.

Stripe is now generally available on the Vercel Marketplace and in v0, with full support for connecting production accounts. Developers can attach an existing live Stripe account directly to a Vercel project, or import one into their environment, and start accepting real payments immediately—no rebuilding required. The connection flow provisions the necessary environment variables automatically, so moving from test mode to live transactions no longer involves copying API keys or verifying configuration across multiple environments.

vercel integration add stripe # provisions Stripe account
vercel integration guide stripe # guides agents through the setup process

The Vercel Marketplace install command creates a new Stripe account instantly, letting you begin coding within seconds. General availability also expands beyond the earlier beta's Sandbox-only support to include live ecommerce storefronts, SaaS subscriptions, usage-based billing, and invoicing. For teams already in production, the key distinction is that going live is now a single integration between project and payment provider rather than a separate configuration step that lives outside the development workflow.

Key management that defaults to secure

Simpler connections only matter if they don't weaken security. To support production traffic, Vercel and Stripe built a new set of key management APIs that orchestrate the entire credential lifecycle. Instead of asking developers to manually retrieve and paste API credentials, the integration performs a cryptographic key exchange and stores the provisioned keys as environment variables scoped to the appropriate Vercel environment—preserving the intended separation between development, preview, and production while reducing the surface area for human error.

Stripe distinguishes between two key types, each with its own handling rules:

  • Secret keys (STRIPE_SECRET_KEY): restricted to server-side code such as API routes or Server Actions, and never exposed client-side or committed to version control.
  • Publishable keys (NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY): safe for client-side use; they identify your Stripe account but cannot perform sensitive operations.

From working app to live revenue in one workflow

With the integration in place, the path from a functioning application to actual revenue stays inside the same build-and-deploy loop you already use. A minimal example—creating a Checkout Session—is enough to stand up a first online store on Vercel and Stripe.

import Stripe from "stripe"
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY)
const session = await stripe.checkout.sessions.create({
    ui_mode: 'embedded',
    redirect_on_completion: 'never',
    line_items: [
      {
        price_data: {
          currency: "usd",
          product_data: { name: "T-Shirt" },
          unit_amount: 40_00,
        },
        quantity: 1,
      },
    ],
    mode: 'payment',
  })

Install Stripe from the Vercel Marketplace or v0, connect your account, and environment variables are ready before you write any payment code. Additional details are available in the changelog and documentation.