A timeout does not prove a payment failed. Laravel may stop waiting after a payment provider has received the request and begun processing it; if the application then sends a new payment operation, the customer can be charged twice. The fix is to keep one durable payment attempt, retry it only with the same provider idempotency key and unchanged parameters, and reconcile its eventual status with the provider.
Why a timed-out payment can still succeed
A payment request and its response are separate events. The provider can receive and process a payment-creation request while its response is delayed or lost. Laravel then reaches its timeout and reports a connection problem, but that describes what the application observed—not whether the provider completed or rolled back the payment.
As an Amazon Associate I earn from qualifying purchases.
- Your application sends a payment-creation request.
- The provider receives it and may process it.
- The response does not arrive before Laravel’s timeout, so the client raises a connection exception.
- A user action, application retry, or queue retry sends another request.
- If that second request is treated as a new payment rather than the same logical attempt, it may create another charge.
The Stripe PHP SDK README, in “Custom Request Timeouts,” warns: “We do not recommend decreasing the timeout for non-read-only calls (e.g. charge creation), since even if you locally timeout, the request on Stripe’s side can still complete. If you are decreasing timeouts on these calls, make sure to use idempotency tokens to avoid executing the same transaction twice as a result of timeout retry logic.” This is Stripe-specific guidance; other providers may have different retry and idempotency behavior.
Free tools Windows power users keep installed
One-click scans. No signup required.
What Laravel’s timeout and retry behavior means
Laravel 13.x documents a 30-second default response timeout for its HTTP client. When a configured timeout is exceeded, the client throws IlluminateHttpClientConnectionException. The separate connectTimeout setting controls how long the client waits to establish a connection; its documented default is 10 seconds. These are framework defaults, not universal payment-provider recommendations. Laravel 13.x HTTP client documentation.
#1 Best Overall
- With Square Terminal, you can ring up sales, accept payments, and print receipts, all with one device. Use it at the counter or ring up customers anywhere in your store.
- Accept all major credit and debit cards and pay one low rate with no hidden fees and no long-term contracts.
- Process chip cards in just two seconds.
- Get your money as soon as the next business day.
- Use it cordlessly with the built-in battery, designed to last all day.
Laravel’s retry() method can repeat requests and accepts an attempt limit, delay, and optional callback for deciding whether to retry. But the method does not make a payment-creation request safe to repeat. Add the provider’s idempotency mechanism and preserve the same logical operation and parameters. Laravel also documents that a connection problem can still throw ConnectionException, including when retry exceptions are otherwise suppressed. Laravel 13.x HTTP client documentation.
Keep three outcomes distinct in application logic:
- Transport exception: Laravel did not receive a usable response in time. The payment outcome may be unknown.
- HTTP error response: The provider returned an HTTP status such as 4xx or 5xx. Laravel’s HTTP wrapper does not automatically throw for those responses; inspect the response or explicitly call methods such as
throw(). - Confirmed payment failure: The provider’s response or later status information establishes that the payment failed.
An HTTP error response is not automatically equivalent to a confirmed payment failure either; interpret it according to the provider’s documented response semantics.
Rank #2
- Use the, easy-to-use, and customizable POS to get started.
- Accept contactless payments, chip cards, Apple Pay, and Google Pay from anywhere, with improved connectivity, extended battery life, and enhanced security. Pay one low rate for every tap or dip.
- No long-term commitments or contracts, no monthly fees- and with offline payments, keep taking payments for up to 24 hours.
- Safely and securely accepts payments anywhere. Plus, get data security, 24/7 fraud prevention, and payment-dispute management at no extra cost.
- Use the, easy-to-use, and customizable POS to get started.
Make a retry the same payment attempt
Before contacting the provider, create and persist a local payment-attempt record with a stable identifier and enough state to resume or reconcile it. Generate a high-entropy idempotency key for the attempt, then reuse that key and the original request parameters when retrying with Stripe. Do not create a fresh key just because the first response timed out: a new key can make the retry look like a new payment.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Stripe says idempotency lets clients retry safely without accidentally performing the same operation twice. For a repeated request with the same key, Stripe returns the first request’s stored status code and response body, including when the first result was an error. The parameters must match the original request; reusing the key with different parameters is rejected. Stripe recommends a high-entropy random key such as a v4 UUID, allows keys up to 255 characters, and cautions against putting sensitive personal data in a key. Stripe idempotent requests.
Rank #3
- With Square Handheld, you can accept payments, take tableside orders, or scan barcodes anywhere. With a slim design and comfortable grip, the POS is easy to carry in your palm or pocket. Square Handheld is designed to withstand water splashes and dust. Add an optional protective case for accidental drops. A long-lasting battery and offline payments let you keep selling.
- Slim, pocketable, and lightweight so you can accept payments wherever your customers are.
- Take tableside orders, bust lines, or use the built-in barcode scanner, all with one sleek device.
- A battery that can power through your shift and offline payments let you keep selling, even if your internet is down.
- Accept all major credit and debit cards and pay one simple rate with no hidden fees and no long-term contracts required.
Stripe stores an idempotent result once endpoint execution begins. It does not store a result if validation fails before execution or if a concurrent-request conflict prevents execution; its documentation says those cases can be retried. Stripe accepts idempotency keys on POST requests; GET and DELETE requests do not benefit from them. Stripe idempotent requests.
Conceptually, a direct API integration should follow this order:
Rank #4
- The Clover Compact and Clover Mini /Station sync with each other through the Clover Dashboard and cloud-based network. This allows you to manage transactions, track sales, and access business data across both devices seamlessly. Plug in, not battery/mobile. Requires New Processing account through Powering POS. (US, PR, USVI). CANNOT be used with a different Processor. Rate match guarantee. Contact us for questions
- Persist a local attempt before making the provider request. Keep its local ID, intended amount and currency, and current state together.
- Derive or store one high-entropy provider idempotency key for that attempt.
- Send the request with that key and the exact intended parameters.
- If the call times out, mark the attempt as unknown or pending reconciliation—not failed—and do not start another logical payment for the same purchase.
- If retrying, resend the same operation with the same key and parameters, subject to the provider’s documented behavior.
- Update the local state only from an appropriate provider response or verified provider event.
This describes the safety properties the integration needs; the exact request construction and response fields depend on the Stripe API operation and the Laravel integration in use.
Keep local recovery durable beyond Stripe’s key retention
An idempotency key is not a permanent payment ledger. Stripe may remove keys automatically after they are at least 24 hours old. If a key has been pruned, reusing it can result in a new request. Persist the local payment-attempt identifier and status, and reconcile an old ambiguous attempt before deciding to create a new one. Stripe idempotent requests.
Best Value
- A complete countertop point of sale — Combine dual responsive touchscreens, built-in POS software, and durable hardware for a fast, reliable checkout experience.
- Serve customers faster — Run smoothly through busy shifts, complex menus, and big orders with high-speed processing, memory, and responsive touchscreen displays.
- Accept every way they pay — Take all major cards at one simple rate, with no hidden fees or long-term contracts. Receive funds as soon as the next business day.
- Handle real-world demands — Resist everyday spills, dust, and wear with a durable, IP54-rated design.
- Stay reliable through every rush — Maintain strong connectivity and consistent performance through your busiest hours.
This is why local state matters even when provider idempotency is in place. The provider key helps make near-term retries safe; your database preserves the relationship between a purchase, its logical attempt, and its eventual outcome for longer-term recovery. Define an explicit operational path for unresolved attempts rather than allowing a retry job or customer action to silently create a replacement payment.
Reconcile payment status with provider evidence
A browser error, queue retry, or Laravel timeout is not a payment status. Use the provider’s documented status lookup or verified event flow to determine what happened before marking an attempt failed or initiating a replacement.
For Laravel Cashier integrations
Laravel Cashier 13.x documents Stripe webhook endpoint configuration, signature-verification middleware when configured with the webhook secret, and dispatching webhook events to application listeners. Its payment documentation covers PaymentIntent use. Follow the documented Cashier flow for the installed version, configure signature verification, and use verified provider events to reconcile local state. Laravel Cashier 13.x documentation.
For webhook event handling
Do not assume a webhook delivery is unique or exactly once. Store provider event IDs or equivalent operation identifiers and, where appropriate, enforce uniqueness in the database so repeated processing cannot apply the same state transition twice. Confirm the precise delivery and event behavior for the provider and Cashier version you deploy; the Cashier documentation establishes configuration, verification, and event handling, not a universal exactly-once guarantee.
Choose timeout and retry behavior deliberately
Do not lower a timeout merely to make a slow payment call feel faster. A shorter wait can increase the number of ambiguous outcomes without changing what the provider does after receiving the request. Select timeouts and retry policies for the actual provider, network, and deployment environment, then ensure any retry of payment creation is protected by stable idempotency and durable attempt state. Neither Laravel’s defaults nor Stripe’s documentation establishes one timeout value that suits every application.
Quick Recap
- Retry only when the operation is still the same payment attempt.
- Do not treat a connection exception as proof the payment failed.
- Do not change request parameters while reusing an idempotency key.
- Do not let a new browser submission or queue job create a second attempt while the first remains unresolved.
- Reconcile status through provider evidence and retain local state for unresolved attempts.
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.
