How to Integrate Replit with Stripe Connect

Open your Replit project and click the Agent icon in the left sidebar to open the Agent chat panel. Type /stripe and press Enter. The Agent detects the /stripe command and begins the native Stripe setup workflow. It will ask you a few questions: what kind of payment you want to accept (one-time, subscription, or marketplace), what currency and price points to use, and whether you want a hosted Stripe Checkout page or a custom payment form. Answer these prompts in plain English — for example, 'One-time payment, $49, USD, hosted checkout page.' The Agent then automatically provisions a Stripe sandbox environment linked to your Replit workspace. It generates and stores STRIPE_PUBLISHABLE_KEY, STRIPE_SECRET_KEY, and STRIPE_WEBHOOK_SECRET in your Replit Secrets (visible by clicking the lock icon in the sidebar). You do not need to log in to Stripe or copy any keys manually at this stage — the sandbox credentials are provisioned programmatically.

After the Agent finishes setup, it generates several files in your project. For a Node.js project you will see a server.js (or index.js) with two key routes: a POST /create-checkout-session endpoint that creates a Stripe Checkout session server-side, and a POST /webhook endpoint that receives and verifies Stripe event notifications. The checkout route uses the official stripe Node.js library, reads your STRIPE_SECRET_KEY from process.env, and creates a session with your configured price and redirect URLs. The webhook route uses express.raw() before express.json() — this ordering is critical because Stripe signature verification requires the raw request body before it is parsed. The Agent also generates a frontend page with a checkout button that calls your /create-checkout-session endpoint. Review these files carefully. Common things to customize: the success_url and cancel_url (they default to your Replit development URL — update them to your deployment URL before going live), the product name and description, and the database write that happens on checkout.session.completed.

1// server.js — auto-generated structure (review and customize)
2const express = require('express');
3const stripe = require('stripe')(process.env.STRIPE_SECRET_KEY);
4const app = express();
5
6// Webhook route MUST be before express.json() middleware
7app.post('/webhook', express.raw({ type: 'application/json' }), (req, res) => {
8  const sig = req.headers['stripe-signature'];
9  let event;
10  try {
11    event = stripe.webhooks.constructEvent(
12      req.body, sig, process.env.STRIPE_WEBHOOK_SECRET
13    );
14  } catch (err) {
15    return res.status(400).send(`Webhook Error: ${err.message}`);
16  }
17
18  if (event.type === 'checkout.session.completed') {
19    const session = event.data.object;
20    // TODO: update database, unlock access, send confirmation email
21    console.log('Payment succeeded for:', session.customer_email);
22  }
23
24  res.json({ received: true });
25});
26
27app.use(express.json());
28
29app.post('/create-checkout-session', async (req, res) => {
30  const session = await stripe.checkout.sessions.create({
31    payment_method_types: ['card'],
32    line_items: [{ price: process.env.STRIPE_PRICE_ID, quantity: 1 }],
33    mode: 'payment',
34    success_url: `${process.env.APP_URL}/success?session_id={CHECKOUT_SESSION_ID}`,
35    cancel_url: `${process.env.APP_URL}/cancel`,
36  });
37  res.json({ url: session.url });
38});
39
40app.listen(3000, '0.0.0.0', () => console.log('Server running on port 3000'));

With the sandbox credentials in place, run your Replit app and click the checkout button on your frontend page. You will be redirected to Stripe's hosted checkout page. Use Stripe's test card number 4242 4242 4242 4242 with any future expiry date and any 3-digit CVC to complete a test payment. After the card is submitted, Stripe redirects to your success_url and fires a checkout.session.completed webhook event to your /webhook endpoint. In Replit's console output you should see 'Payment succeeded for: [your test email]' printed. You can also verify the event in your Stripe Dashboard under Developers > Events — look for the checkout.session.completed event and confirm the webhook delivery status shows 200. Test multiple scenarios: a successful payment, a declined card (use 4000 0000 0000 0002), and a cancelled checkout. Check that each scenario routes correctly to your success or cancel pages and that your database updates happen only on genuine payment success events.

Before going live, deploy your app to a Replit Reserved VM. This is important specifically for webhook reliability. If you use Autoscale Deployment, your server scales to zero when no traffic arrives for several minutes, causing a cold start delay on the first webhook after idle. While Stripe retries webhook deliveries multiple times over 24 hours, a cold start can cause the initial webhook to arrive while the server is still starting up, which may result in a 503 or timeout response and trigger a retry. For payment processing, receiving webhooks without delay and without retry complexity is worth the small additional cost of a Reserved VM (starting around $6/month). To deploy: click the Deploy button in the Replit toolbar, select Reserved VM, choose the machine size appropriate for your traffic, and click Deploy. Copy the deployment URL shown after deploy completes (format: https://your-app-name.replit.app) and update your STRIPE_WEBHOOK_SECRET registration in the Stripe Dashboard to point to your deployment URL's /webhook endpoint. Also update success_url and cancel_url in your checkout session code to use the deployment URL, not the development URL.

1# .replit deployment config — ensure port binding is correct
2# [[ports]]
3# internalPort = 3000
4# externalPort = 80
5#
6# [deployment]
7# run = ["node", "server.js"]
8# deploymentTarget = "cloudrun"

Going live with real payments requires one additional step beyond swapping test keys for live keys. Replit's native Stripe integration uses the Stripe Marketplace app called 'Replit Integrated Payments' to manage the connection between your Replit workspace and your live Stripe account. In your Stripe Dashboard, navigate to the App Marketplace and search for 'Replit Integrated Payments.' Install the app and authorize it to access your Stripe account. Once installed, the app provisions your live STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY and links them to your Replit deployment. Back in Replit, click the lock icon to open Secrets and verify that the live keys (starting with sk_live_ and pk_live_) have been injected. Also retrieve your live webhook signing secret from Stripe Dashboard > Developers > Webhooks > your deployment endpoint > Signing secret, and update STRIPE_WEBHOOK_SECRET in Replit Secrets. Redeploy your app one final time to ensure all production secrets are loaded. Run a final end-to-end test with a real card for a small amount to confirm the live flow works, then refund the test charge from your Stripe Dashboard.