Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The short answer: Apps Script Content Service redirects its response to a one-time script.googleusercontent.com URL, while Stripe treats a webhook response in the 3xx range—including 302—as a failed delivery. Stripe’s documented workaround is to register the redirect-resolved URL as the endpoint destination. But Google describes that URL as one-time, so do not assume it will remain suitable for later retries; verify its persistence or use a stable HTTPS receiver that returns 2xx without redirecting.
Why Apps Script returns 302 and Stripe retries
An Apps Script web app handles an incoming HTTP POST through doPost(e); the request body is available as e.postData.contents. When a script returns raw content through Google’s Content Service, Google redirects that content to a one-time URL at script.googleusercontent.com for security. Google’s general guidance for an HTTP client consuming Content Service is to follow the redirect.
Stripe’s webhook behavior is different: Stripe considers 3xx responses delivery failures. Its guide says a successful delivery is indicated by a 200 response and advises endpoint handlers to return a successful 2xx response quickly. So the fact that a browser or ordinary HTTP client can follow the redirect does not mean Stripe will treat the original webhook attempt as successful.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsGoogle’s Apps Script Content Service documentation describes the redirect as one-time; Stripe’s webhook guide documents 3xx as failure and recommends changing the registered destination to the URL resolved by the redirect.
#1 Best Overall
How to diagnose the 302
- Check the delivery in Stripe Workbench. Open the webhook endpoint, then its Event deliveries view. Inspect the attempt’s HTTP status and any scheduled next retry. Stripe identifies 302 and other 3xx responses as redirect failures.
- Inspect the first response from the registered URL. Send a POST to the exact URL configured in Stripe and examine the initial status and
Locationheader. Do not rely only on a browser view that may follow redirects automatically. If the first response is 302, note the redirect target. - Decide whether that target is dependable. Stripe’s documented workaround is to use the resolved URL as the endpoint destination. However, Google calls the Content Service destination one-time and does not establish in the cited documentation that a captured URL is a durable endpoint for subsequent deliveries. Confirm that it remains valid for later attempts rather than assuming it will.
Choose a fix that fits the reliability you need
| Approach | Endpoint behavior | Signature and response requirements | Operational trade-off |
|---|---|---|---|
| Keep Apps Script and register the redirect-resolved target | Can avoid registering the original URL that returns 302, if the resolved target works for Stripe. Google describes the Content Service target as one-time, so long-term stability is not established. | The handler still needs access to the unmodified request body and the Stripe-Signature header to verify deliveries, then must return 2xx promptly. |
Least architectural change, but requires confirming that the target continues to work across retries and future deliveries. |
| Use a stable HTTPS webhook receiver | Register a publicly accessible HTTPS URL that accepts POST without redirecting. | Verify the signature against the raw body and return 2xx promptly; queue slower work if needed. | Requires choosing and operating another receiver, but gives you a stable endpoint under your control. |
| Use a cloud event destination | Stripe names Amazon EventBridge and Azure Event Grid as event-consumption alternatives. | Choose an integration that meets your event validation and acknowledgement needs. | Moves delivery into cloud event infrastructure; suitability depends on your architecture and is not established just by Stripe listing the options. |
For a production integration, a stable, publicly accessible HTTPS receiver that returns 2xx without redirecting is the safer default when you cannot establish that the Apps Script-resolved target remains valid. Stripe documents HTTPS requirements, raw-body signature verification, and prompt acknowledgement in its webhook guide and signature verification guide.
Preserve signature verification and handle retries safely
Stripe signature verification requires the raw request body, the Stripe-Signature header, and the endpoint’s signing secret. Verify the body before parsing or transforming it: parsing and reserializing the JSON can change the bytes and cause verification to fail. Acknowledge valid events promptly with 2xx, and move slow follow-up work to asynchronous processing when appropriate.
Rank #2
Do not design the handler around exactly-once or ordered delivery. Stripe says events can arrive more than once and are not guaranteed to arrive in the order they were generated. Track processed event IDs so duplicate deliveries do not repeat side effects, and avoid assuming one event will always precede another. See Stripe’s guidance on webhook best practices.
How long Stripe retries and what to check afterward
Stripe documents automatic retries for failed live deliveries for up to three days with exponential backoff. Sandbox deliveries receive three retry attempts over a few hours. These are Stripe-documented behaviors checked on 2026-10-07 and may change. Workbench’s Event deliveries view shows delivery status and pending future delivery times.
After correcting the endpoint, inspect later attempts and confirm they receive 2xx. A successful manual resend does not cancel the automatic retry schedule, according to Stripe, so continue monitoring pending attempts rather than assuming a resend cleared them. Stripe’s current webhook delivery guidance covers status and retry behavior.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
