An error occurred with our connection to Stripe. Request was retried 2 times.

[jellohouse]

Describe the bug

I'm running a nextJS app project on Cloudflare workers. Using the latest Stripe node sdk version 20.

On the production server when I try to create a checkout session from my api route, I see this error.
An error occurred with our connection to Stripe. Request was retried 2 times.

On localhost the exact same code is working perfectly fine.

I double checked my env vars to make sure they're properly passed and correct in production, yet i'm still getting the error.

---

For now what I did is omit the SDK and just use a raw fetch request and it works in production.

---

To Reproduce

1. npm create cloudflare@latest -- my-next-app --framework=next https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/
2. npm i stripe --save
3. Create an api route like "/api/stripe-checkout" that uses the sdk like this
   const session = await stripe.checkout.sessions.create({ ... }) This will cause the error
4. Deploy to Cloudflare workers
5. Call the endpoint

Expected behavior

The Stripe Checkout page should open the same way it does when I'm doing it from localhost.

Code snippets

import { createClient } from '@/lib/supabase/server';
import { NextResponse } from 'next/server';
import { Stripe } from 'stripe';

export async function POST(request) {
  try {
    const supabase = await createClient();
    const stripe = new Stripe(process.env.STRIPE_SECRET_KEY);

    const {
      data: { user },
      error: getUserError,
    } = await supabase.auth.getUser();
    if (getUserError) throw getUserError;

    const session = await stripe.checkout.sessions.create({
      client_reference_id: user.id,
      customer_email: user.email,
      metadata: {
        plan_id: "pro",
        email: user.email,
      },
      line_items: [
        {
          price: "xxxxxxxxxx", //replace with your price id
          quantity: 1,
        },
      ],
      mode: 'subscription',
      success_url: `${process.env.NEXT_PUBLIC_HOST_URL}/premium`,
      cancel_url: `${process.env.NEXT_PUBLIC_HOST_URL}/premium`,
    });

    return NextResponse.json(
      { url: session.url },
      { status: 200 }
    );
  } catch (e) {
    console.log('Some errr', e);
    return NextResponse.json(
      { message: e.message },
      {
        status: 500,
      }
    );
  }
}

OS

macos

Node version

21

Library version

20.0.0

API version

2025-11-17.clover

Additional context

No response

[mbroshi-stripe]

Hi @jellohouse! Thanks for reporting this issue. We're investigating on our end, and I'll circle back once I have updates or if I have any additional questions.

[mbroshi-stripe]

I am unfortunately not able to reproduce your issue. I created a new Cloudflare Page running on Next with almost identical code to your code sample, except that I needed to add

export const config = {
  runtime: "edge",
};

is one difference.

My dependencies are:

• stripe@20.0.0
• Next.js version: 15.5.9

Are you able to log any additional info to help debug your issue?

[jellohouse]

You must try using nextjs on workers (the new method).

Do NOT deploy on pages using next-on-pages which uses edge runtime - this is now deprecated/unrecommended.

As mentioned here https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/ you should now use OpenNext to deploy on cloudflare workers.

[mbroshi-stripe]

Thanks for the clarification. I was able to reproduce on a Cloudflare worker. Have you tried using a fetch-based HTTP client like this:

const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!, {
  httpClient: Stripe.createFetchHttpClient(),
});

When I tried that, it fixed the issue on the Cloudflare worker. There's more info available here: https://blog.cloudflare.com/announcing-stripe-support-in-workers/

[MariuzM]

i had similar issue when trying to upload a file to stripe files, i ended up doing fetch request instead of stripe sdk and that worked

[marcelino-borges]

i had similar issue when trying to upload a file to stripe files, i ended up doing fetch request instead of stripe sdk and that worked

Dude, I was gonna comment exactly this right now lol

I was struggling ages having timeout to create a file using the Files API with NodeJS SDK. No apparent reason. Error saying it timedout and that it tried 2 times.
I managed to do it only when I started to use the HTTP/REST API, instead node SDK (ugly stuff in my code, but at least I can move forward with the integration right now).

[prathmesh-stripe]

@MariuzM @marcelino-borges Are you facing this issue with NextJS on Cloudflare workers. Did you try setting the httpClient to the fetch based HTTP client?

[MariuzM]

@MariuzM @marcelino-borges Are you facing this issue with NextJS on Cloudflare workers. Did you try setting the httpClient to the fetch based HTTP client?

I was using Node.js / Fastify but interesting locally setup it was working fine when i pushed to Prod then it started not working.
I just wrote fetch request and that worked

[prathmesh-stripe]

@MariuzM What kind of environment are you using for prod? I'm trying to see if there is a larger compatibility issue that needs to be addressed with our Node SDK.

[MariuzM]

@prathmesh-stripe there was no issues before so i guess some update in SDK messed it up, I'm using Railway

[prathmesh-stripe]

@MariuzM We did encounter and fix a file encoding issue in Bun recently. What is your current SDK version? And do you remember the SDK version that you were using before?

[MariuzM]

^20.1.0 same before i think but i don’t remember 100%

[prathmesh-stripe]

@MariuzM @marcelino-borges Can you create a separate issue with code sample, framework and environment information so we can reproduce the issue and fix it's root cause in the SDK.

[prathmesh-stripe]

The answer by @mbroshi-stripe should solve the problem.