> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Accept payments with Stripe

> Accept payments with the Replit Stripe connector or your own Stripe keys. Choose a setup, test checkout, and configure live payments.

export const YouTubeEmbed = ({videoId, title = "YouTube video", startAt}) => {
  if (!videoId) {
    return null;
  }
  let url = "https://www.youtube.com/embed/" + videoId;
  if (startAt) {
    url = url + "?start=" + startAt;
  }
  return <Frame>
      <iframe src={url} title={title} allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowFullScreen></iframe>
    </Frame>;
};

export const Connectors = ({items}) => <div style={{
  margin: "8px 0 20px"
}}>
    <style>{`
      .connectors-list, .connectors-list * { margin-top: 0 !important; margin-bottom: 0 !important; }
      .connectors-row {
        display: flex !important;
        align-items: flex-start !important;
        gap: 10px !important;
        padding: 4px 0 !important;
        min-height: 0 !important;
        height: auto !important;
      }
      .connectors-row img {
        width: 20px !important;
        height: 20px !important;
        max-width: 20px !important;
        max-height: 20px !important;
        margin: 2px 0 0 !important;
        display: block !important;
      }
    `}</style>
    <div className="connectors-list">
      {items.map((item, i) => <div key={item.id} className="connectors-row" style={{
  borderTop: i === 0 ? "none" : "1px solid rgba(130,130,130,0.22)"
}}>
          <img src={`/images/connectors/${item.id}.svg`} alt="" width={20} height={20} />
          <div style={{
  minWidth: 0
}}>
            <div>
              <strong>{item.name}</strong>
              {item.why ? <span style={{
  opacity: 0.72
}}> · {item.why}</span> : null}
            </div>
            {item.auth === "api-key" ? <div style={{
  fontSize: "11.5px",
  lineHeight: 1.35,
  color: "#F26207",
  marginTop: "2px"
}}>
                Not a native connector. Agent will ask for your API key.
              </div> : null}
          </div>
        </div>)}
    </div>
  </div>;

export const AiPrompt = ({children}) => {
  return <CodeBlock className="relative block max-w-full overflow-x-hidden font-sans !whitespace-pre-wrap !break-words" style={{
    overflowWrap: "anywhere",
    wordBreak: "break-word"
  }}>
      <div className="pr-7" style={{
    whiteSpace: "pre-wrap",
    overflowWrap: "anywhere",
    wordBreak: "break-word"
  }}>
        {children}
      </div>
    </CodeBlock>;
};

Accept payments in your app with either the Replit Stripe connector or your own Stripe API keys.
Choose the connector for managed sandbox setup, or use your own keys when you need control over the integration.

## Choose one method per environment

| Method | Setup | Where it lives |
| - | - | - |
| [Replit Stripe connector](#replit-stripe-connector) | Agent sets up a Stripe sandbox, then you connect your live account. Available on paid plans. | **Integrations > Stripe** |
| [Your own Stripe keys](#your-own-stripe-keys) | You manage API keys, the Stripe SDK, and webhook endpoints yourself. | **Secrets** |

Use one method in each environment, not both at once. Combining them in the same environment causes connection conflicts.
You can use different methods across environments, such as the connector's sandbox in development and your own live keys in production.

## Best for

* Founders who run bookings, rentals, or appointments and need deposits that protect their time.
* Builders who want payments working in a sandbox today and live payments without a manual key setup.
* Teams with an existing Stripe account or requirements that need a manually managed SDK and webhook integration.

## Replit Stripe connector

Use this method to take a refundable deposit at booking and charge the balance later, without pasting API keys.

### Connectors

<Connectors
  items={[
{
  id: "stripe",
  name: "Stripe",
  why: "Sandbox checkout, saved payment methods, refunds, and the live account connection",
},
]}
/>

### Before you start

Start from an App with a backend, sign-in, and a database, so each booking can store its payment
status. Then pick the math:

* **Deposit at booking:** a flat amount, such as \$500, or a percentage of the total.
* **Balance later:** the rest of the price, charged to the saved card when the customer arrives.
* **Refund window:** how late a customer can cancel and still get the deposit back. 48 hours is a common default.

### Prompt the agent

<AiPrompt>
  Add deposit and balance payments to this app with the Replit Stripe connector, starting in the
  Stripe sandbox. At booking, take a \[\$500] refundable deposit and save the customer's payment
  method. When the customer arrives, charge the remaining balance to the saved payment method. If
  the customer cancels more than \[48 hours] before the booking, refund the deposit in full. Inside
  that window, keep it. Save the deposit status and the saved-card reference on each booking. Give
  me a test checklist for deposit success, deposit decline, balance charge, and cancellation refund.
</AiPrompt>

Agent proposes the Stripe connector and sets up a Stripe sandbox for you. You don't need to copy
keys from the Stripe Dashboard.

### What to expect

Agent adds checkout, the deposit and balance flows, and the refund rule. Test them in Preview with
Stripe's test card `4242 4242 4242 4242`, any future expiry, and any 3-digit CVC:

1. Make a booking and pay the deposit. Confirm the booking shows the deposit as paid and a card on file.
2. Charge the balance from the booking. Confirm it shows as paid.
3. Cancel a second booking outside the refund window. Confirm the refund in your Stripe sandbox dashboard.
4. Cancel a third booking inside the window. Confirm the app keeps the deposit and explains why.
5. Pay with Stripe's decline test card `4000 0000 0000 0002`. Confirm the booking isn't confirmed.

When the flows work, connect your live Stripe account from the **Publish** pane. Follow
[Go live](/features/monetization/stripe-payments#go-live) on the Stripe Payments page, then make one
low-cost real booking with your own card before you share the app.

### Make it work for you

<AiPrompt>
  Switch to one full payment at booking instead of a deposit and balance.
</AiPrompt>

<AiPrompt>
  Email the customer a receipt after the deposit and after the balance charge.
</AiPrompt>

### Troubleshooting

* **The deposit succeeds but the booking isn't confirmed:** ask Agent to connect the Stripe payment success event to the booking status in the database, then test another booking.
* **Agent asks you to paste Stripe keys or set up a webhook:** tell Agent to use the Replit Stripe connector instead. Mixing the connector and your own keys in the same environment causes conflicts.
* **Publishing asks you to connect a live Stripe account:** the sandbox only takes test payments. Connect your live account from the **Publish** pane, as described in [Go live](/features/monetization/stripe-payments#go-live).
* **You need subscriptions for a mobile app:** use [RevenueCat subscriptions](/features/monetization/revenuecat-subscriptions) instead.

## Your own Stripe keys

Connect Stripe yourself: store your own API keys in Secrets, take payments with the Stripe SDK, and
receive payment events through a webhook. Use this path when you already manage a Stripe account
and want full control over the setup.

<Warning>
  This is a manual setup. You create and rotate the keys, register the webhook, and keep the
  integration working. Replit doesn't manage it. For a setup without API keys, use the
  [Replit Stripe connector](/use-cases/accept-payments-with-stripe#replit-stripe-connector).
</Warning>

### Before you start with your own keys

Copy your test API keys from the Stripe Dashboard and add them to your app's **Secrets**.
Add the webhook signing secret later, when you start the listener described below.

| Secret | Value |
| - | - |
| `STRIPE_SECRET_KEY` | Your secret key (`sk_...`) or restricted key (`rk_...`). This exact name is required. |
| `STRIPE_PUBLISHABLE_KEY` | Your publishable key (`pk_...`), used in the browser. |
| `STRIPE_WEBHOOK_SECRET` | The signing secret (`whsec_...`) from your development listener, or from your live webhook endpoint in production. |

Keep test keys in development. Configure live keys separately in your published app's secrets.

To add a key, select **Tools** in the Project Editor, then **Secrets** under **Setup**.
Select **New Secret**, enter the exact name in **Key**, enter your Stripe key in **Value**, and select **Add Secret**.

<Frame caption="Enter the exact secret name in Key. The example leaves Value empty; enter your own key there.">
  <img src="https://mintcdn.com/replit/2n-A_ptJoYn-gb3a/images/stripe/secret-name-context.png?fit=max&auto=format&n=2n-A_ptJoYn-gb3a&q=85&s=1133c28885534c63747df325de6ba576" alt="Project Editor with Secrets selected under Setup and the new-secret form highlighted, showing STRIPE_SECRET_KEY in Key and an empty Value field" width="2720" height="2040" data-path="images/stripe/secret-name-context.png" />
</Frame>

After completing the webhook setup below, your Secrets list contains the three names with their values hidden:

<Frame>
  <img src="https://mintcdn.com/replit/TBbCBDsd8nVQwxq3/images/velocity/add-payments/stripe-secrets.png?fit=max&auto=format&n=TBbCBDsd8nVQwxq3&q=85&s=80f25ad62982cb96274ab45692f7baff" alt="Replit Secrets pane showing the STRIPE_SECRET_KEY, STRIPE_PUBLISHABLE_KEY, and STRIPE_WEBHOOK_SECRET secrets" width="1280" height="720" data-path="images/velocity/add-payments/stripe-secrets.png" />
</Frame>

### Prompt the agent for manual setup

<AiPrompt>
  Add Stripe Checkout to this app with the Stripe SDK and my own keys. Don't use the Replit Stripe
  connector. Read the secret key from STRIPE\_SECRET\_KEY and the publishable key from
  STRIPE\_PUBLISHABLE\_KEY. Add a webhook endpoint that verifies Stripe signatures with
  STRIPE\_WEBHOOK\_SECRET and marks orders as paid on checkout.session.completed. Tell me the
  endpoint path to register in Stripe, and give me a test checklist.
</AiPrompt>

### Test the manual integration

Agent adds checkout and a webhook endpoint. For development, follow Stripe's
[webhooks quickstart](https://docs.stripe.com/webhooks/quickstart) to install and authenticate the
Stripe CLI in your project's Shell. Ask Agent for your server's local port and webhook path.

Run the listener in that same environment, replacing the example port and path with your app's values:

```sh theme={null}
stripe listen --forward-to localhost:4242/webhook
```

Save the signing secret printed by `stripe listen` as `STRIPE_WEBHOOK_SECRET` in your development
Secrets, then restart your app so it reads the value. Keep both the app and the listener running
while you test in Preview. The listener forwards test events to the development server, so you
don't need a published URL or a public development webhook endpoint yet.

Watch the walkthrough to see the full setup:

<YouTubeEmbed videoId="TW8xaPERcRU" title="Stripe Checkout in Replit" />

Test with Stripe's test card `4242 4242 4242 4242`, any future expiry, and any 3-digit CVC.
Confirm the order shows as paid in your app and the Stripe CLI reports a successful response
from your webhook endpoint.

### Publish with your own live keys

Keep your development test keys and listener secret unchanged. In **Publishing > Adjust settings >
Production app secrets**, set `STRIPE_SECRET_KEY` and `STRIPE_PUBLISHABLE_KEY` to your live keys.
See [Manage production secrets](/core-concepts/project-editor/app-setup/secrets#manage-production-secrets).

Register a separate live-mode webhook endpoint in Stripe using your published app URL plus the
webhook path. Set `STRIPE_WEBHOOK_SECRET` in **Production app secrets** to that endpoint's signing
secret, not the CLI listener's secret, then publish or republish.
If this is your first publish, establish the published URL first, then finish the endpoint and
secret setup and republish before accepting payments.

If development uses the Replit Stripe connector's sandbox and production uses your own keys,
publishing checks `STRIPE_SECRET_KEY`:

* It must hold a live secret key (`sk_live_...`) or a live restricted key (`rk_live_...`). Test keys, publishable keys, and keys stored under other names don't count.
* Without a valid live key, publishing stops with **Connect a live Stripe account before publishing.**
* Products and prices don't sync from the sandbox to your live account. Create them in your live Stripe account yourself.

### Customize the manual integration

<AiPrompt>
  Handle refunds and failed payments from the webhook, and show the status on each order.
</AiPrompt>

<AiPrompt>
  Add a monthly subscription with Stripe Billing, using the same keys and webhook.
</AiPrompt>

### Troubleshoot the manual integration

* **Publishing says "Connect a live Stripe account before publishing":** check that the secret is named exactly `STRIPE_SECRET_KEY` and holds a live key that starts with `sk_live_` or `rk_live_`.
* **Webhook events fail signature checks:** make sure `STRIPE_WEBHOOK_SECRET` matches the endpoint's signing secret, and that you use the live-mode secret in production.
* **The connector and your own keys are both set up in one environment:** remove one of them. To remove the connector, see [Update or remove the Stripe connection](/features/monetization/stripe-payments#update-or-remove-the-stripe-connection).

## Related

<CardGroup cols={2}>
  <Card title="Payments and Stripe help" href="/help/payments-and-stripe">
    Answers about setup methods, required secret names, and publishing errors.
  </Card>

  <Card title="Stripe Payments" href="/features/monetization/stripe-payments">
    How the Stripe connector works, from sandbox to live account.
  </Card>
</CardGroup>