Skip to main content

Posts

Featured

Webhooks That Wait: Latency Budgets for Synchronous Events

Most webhooks are polite. A provider sends an event, your server says “got it,” and everything else happens later. Some webhooks are not polite at all. They stop a real transaction and wait for you. If you develop those handlers on a laptop behind a tunnel, you have a new problem: the clock is already running, and the tunnel hop is a slice of it. This guide covers what the budgets are today, how to measure how much of each budget your tunnel consumes, and how to keep a local handler fast enough that you are testing your logic and not your luck. The two budgets that matter right now Stripe Issuing: 2 seconds, and the answer is the decision When a card issued through Stripe Issuing is used, Stripe checks that your Issuing balance has sufficient funds, that the card is active, and that your spending controls allow the purchase. If the authorization survives those checks and you have configured a real-time authorization webhook, Stripe sends an issuing_authorization.request event to ...

Latest Posts

Your CA Got Distrusted Overnight: Auditing Trust Stores for Tunnel Agents and Custom Domains

Your Dev Server’s WebSocket Is Public Now: Cross-Site WebSocket Hijacking Behind a Tunnel

Slack Classic Apps Didn’t Die on November 16: Events API over HTTP vs Socket Mode (and When You Still Need a Tunnel)

Async AI Webhooks on Localhost: OpenAI Batch and Gemini’s Two Webhook Models