<p>We’ve shipped a powerful upgrade to our Stripe payments integration, designed specifically for merchants processing <strong>high volumes of refunds at scale</strong>.</p><p>This release focuses on <strong>speed, visibility, and control</strong>—so refunds no longer feel like an operational bottleneck as your transaction volume grows.</p><div data-type="horizontalRule"><hr></div><h3>🚀 What’s New</h3><h4>1. High-Throughput Refund Processing</h4><p>Refunds are now optimized for bulk and peak-load scenarios. Whether you’re handling mass cancellations, subscription reversals, or dispute resolutions, refunds are processed reliably—even during traffic spikes—using Stripe’s scalable payment infrastructure.</p><p>Powered by <strong>Stripe</strong>’s asynchronous APIs, this ensures refunds don’t block checkout, billing, or reporting workflows.</p><div data-type="horizontalRule"><hr></div><h4>2. Asynchronous Refund Lifecycle</h4><p>Refund creation and settlement are now fully asynchronous:</p><ul><li><p>Initiate refunds instantly</p></li><li><p>Track progress through webhook events</p></li><li><p>Handle partial, full, and multi-currency refunds without polling</p></li></ul><p>This decoupled flow improves system resilience and prevents timeout-driven failures in high-volume environments.</p><div data-type="horizontalRule"><hr></div><h4>3. Granular Refund Status &amp; Metadata</h4><p>Each refund now exposes richer state and metadata:</p><ul><li><p>Pending, succeeded, failed, reversed</p></li><li><p>Processor-level failure reasons</p></li><li><p>Custom merchant metadata for reconciliation and audits</p></li></ul><p>This makes it significantly easier to debug issues, automate workflows, and support finance teams.</p>

Smarter Refund Handling for High-Volume

Shad

<h2>New Developer API to Identify Who Cancelled a Payment</h2><p>We’re introducing a <strong>new developer-facing API enhancement</strong> for Stripe payments that brings <strong>full transparency into payment cancellations</strong>.</p><p>Merchants and developers can now <strong>programmatically determine who cancelled a payment</strong>—whether it was the customer, your application, an admin user, or an automated system.</p><p>This update is designed for teams operating at scale, where understanding <em>why</em> and <em>by whom</em> a payment was cancelled is critical for analytics, compliance, and customer support.</p><div data-type="horizontalRule"><hr></div><h3>🚀 What’s New</h3><h4>1. Cancellation Actor Attribution</h4><p>Every cancelled payment now includes a clear <strong>cancellation source</strong>, powered by <strong>Stripe</strong>’s enhanced event model.</p><p>You can distinguish between:</p><ul><li><p><strong>Customer-initiated cancellations</strong> (e.g. checkout abandonment)</p></li><li><p><strong>Merchant / admin cancellations</strong></p></li><li><p><strong>System-triggered cancellations</strong> (timeouts, rule-based automation)</p></li><li><p><strong>API-driven cancellations</strong> from backend services or jobs</p></li></ul><p>This removes ambiguity from cancellation analytics and support workflows.</p><div data-type="horizontalRule"><hr></div><h4>2. New Cancellation Metadata in Payment Objects</h4><p>Payment and intent objects now expose additional structured fields:</p><ul><li><p><code>cancellation_reason</code></p></li><li><p><code>cancelled_by</code> (actor type)</p></li><li><p><code>cancelled_at</code> (timestamp)</p></li><li><p>Optional developer-defined metadata</p></li></ul><p>This makes cancellation data <strong>queryable, auditable, and automation-friendly</strong>.</p><div data-type="horizontalRule"><hr></div><h4>3. Enhanced Webhook Events for Cancellations</h4><p>Cancellation-related webhook events now include actor context:</p><ul><li><p><code>payment_intent.canceled</code></p></li><li><p><code>payment.canceled</code></p></li></ul><p>Each event contains reliable attribution data, enabling:</p><ul><li><p>Accurate funnel analysis</p></li><li><p>Customer-facing explanations</p></li><li><p>Automated recovery or retry flows</p></li></ul><p>All events follow Stripe’s idempotent and retry-safe guarantees.</p><div data-type="horizontalRule"><hr></div><h4>4. Improved Debugging &amp; Support Workflows</h4><p>With explicit cancellation attribution, teams can now:</p><ul><li><p>Instantly answer <em>“Who cancelled this payment?”</em></p></li><li><p>Reduce back-and-forth between support and engineering</p></li><li><p>Identify UX friction vs system-level failures</p></li><li><p>Build internal dashboards for cancellation trends</p></li></ul><p>This is especially valuable for high-volume SaaS, marketplaces, and subscription platforms.</p><div data-type="horizontalRule"><hr></div><h3>🧠 Why This Matters</h3><p>At scale, cancellations are not just drop-offs—they’re <strong>signals</strong>.</p><p>This update helps merchants:</p><ul><li><p>Separate user intent from system behavior</p></li><li><p>Improve checkout and payment UX</p></li><li><p>Strengthen audit trails for compliance</p></li><li><p>Make data-driven decisions on payment recovery</p></li></ul><p>When you’re handling millions of transactions per day, clarity beats guesswork.</p>

Getting Started

Changelog

Smarter Refund Handling for High-Volume

Developer API to Identify Who Cancelled a Payment