Skip to main content
Every project built on pre.dev can take payments without creating a Stripe account, pasting keys, or registering webhooks. pre.dev Payments is powered by Stripe: your workspace gets a Stripe account behind pre.dev, the build agent uses the ordinary Stripe SDK, and pre.dev delivers Stripe’s events to your app, including the live sandbox while you build.

What you get

How it works

Your app talks to Stripe through api.pre.dev with the workspace’s pre.dev key. pre.dev forwards each request to Stripe scoped to your workspace’s connected account and forwards the response back. The Stripe SDK needs two options, which the build agent sets from environment variables that are already there:
That is the whole integration. See from a pre.dev app for the variables and webhooks for event delivery.

Test mode and going live

While you build, payments run in Stripe test mode on an account pre.dev created for your workspace. Checkout accepts Stripe’s test cards and nothing is charged. To take real money, connect a Stripe account you own once from Integrations → API Keys → Payments, then switch any project from test to live in its Connections tab. See go live.

Bring your own Stripe account

If you already have a Stripe account, paste your own sk_… key as STRIPE_SECRET_KEY in the project’s environment variables. pre.dev then drops its host override and your app talks to Stripe directly with your key. Webhooks for your own account are yours to register in the Stripe dashboard.

Not available through the built-in key

Account management, application fees, and Stripe products that need a platform-level agreement (Radar, Sigma, Issuing, Treasury, Terminal) return a 403 with an explanation. Everything an app normally does to take money is available.