stripebizumupirefundsinvoluntary churncross-border payments

Stripe's Nov 18 Release Gave Bizum and UPI Refunds a Reference Number. One of Those Two Rails Still Can't Run a Subscription.

Stripe extended refund tracing to Bizum and UPI on Nov 18. Bizum can't bill a subscription at all on Stripe, and UPI gives you 7 days to fight a dispute.

XY
21 November 2026 · 8 min read

A subscriber in Madrid cancels and wants their money back. Another in Bangalore does the same thing the same week. Until November 18, 2026, both support tickets ended the same way on your side: Stripe's dashboard said the refund succeeded, and you had nothing else to hand either customer to go check for themselves. No trace number, no reference, nothing their own bank app could match against. Stripe's latest release gives you one for both — the same reference and reference_status fields it added for Klarna, PayPal, and Afterpay/Clearpay back on October 28. But the two rails underneath that identical API field are nothing alike, and the differences matter a lot more than the refund-tracing fix does.

Key stat
7 days
How long you get to submit evidence on a disputed UPI payment. A Bizum dispute gives you 40.
Source: Stripe payment method documentation, Bizum and UPI dispute process pages

Start with what actually shipped, because it's genuinely useful and it's also the smallest part of this story. Stripe's Refund object carries a destination_details hash, one entry per payment method. For cards, it's carried an Acquirer Reference Number or similar trace code for years. Local bank-transfer methods got it earlier in 2026. Klarna, PayPal, and Afterpay/Clearpay joined on October 28. Bizum and UPI joined on November 18 — reference gives you the ID the payment provider assigned the refund, reference_status tells you whether it's pending, available, or unavailable yet. Our earlier breakdown of the Klarna/PayPal/Afterpay version covers the mechanics of that field in detail, and none of it changed here — same two fields, same three states, same webhook events (refund.updated, refund.failed) carrying the update. What's worth a second post isn't the field. It's that Bizum and UPI are such different rails that the exact same fix lands completely differently on each one.

Bizum can't bill a subscription at all. UPI can.

This is the part a lot of teams expanding into Spain or India miss until it's too late to plan around. Stripe's own payment-method support tables list Bizum's usability as single-use, full stop — recurring payments unsupported, no Stripe Billing integration, no Invoicing, no Customer Portal. It only shows up through Checkout Sessions or Payment Links, one transaction at a time, capped at €5,000. If a Spanish subscriber is paying you through Bizum on any kind of schedule, you — or they — are manually triggering a fresh payment every cycle, because there is no mandate, no saved card, no token Stripe can charge off-session. UPI is the opposite case entirely: it supports recurring billing natively through UPI AutoPay e-mandates, plugs directly into Stripe Billing, Invoicing, and the Customer Portal, and is capped at ₹15,000 per automatic charge rather than per transaction overall.

That split changes what a Bizum or UPI cancellation even means operationally. A UPI subscriber canceling is the same shape of event as a card subscriber canceling — an active mandate stops renewing, and (as we've covered separately for UPI Autopay's much higher failure-driven revocation rate) the mandate itself can die independently of anyone actually deciding to leave. A Bizum "cancellation" is really just a customer declining to make next cycle's manual payment — there's no subscription object to cancel in the Bizum sense, because Stripe never let you build one on top of it.

PropertyBizum (Spain)UPI (India)
Recurring billing on StripeNot supported — single-use onlySupported via UPI AutoPay e-mandates
Stripe Billing / Invoicing / PortalNoneFull support
Transaction cap€5,000 per payment₹100,000 per payment; ₹15,000 per AutoPay charge
Refund submission window395 days from payment60 days from payment
Refund processing timeUp to 5 minutesUp to 7 business days
Dispute submission window120 days from purchase90 days from purchase
Evidence response deadline40 calendar days7 calendar days
Final decision issued within90 days of your evidence30 days of dispute creation

Source: Stripe payment method documentation for Bizum and UPI, as of the 2026-11-18 Endive API version.

The refund-window gap is the one that catches teams off guard

Bizum gives you 395 days from the original payment to submit a refund — more than a full year. UPI gives you 60. If your refund policy is written as a single global number, say "we refund within 30 days of cancellation" or "full refund any time in year one," it's trivially compliant on Bizum and can quietly become unenforceable on UPI if a billing dispute, a support backlog, or a slow internal approval drags past the two-month mark. Our piece on refund policy as a retention lever makes the broader case that a no-refund stance just redirects money out through chargebacks instead of support tickets — UPI's 60-day cap is a sharper version of that same risk, because once the window closes, a Refunds API call against that payment simply won't work anymore, policy or no policy.

Refund submission window, as a share of Bizum's 395-day cap
Bizum100%
SEPA Direct Debit (no-questions refund right)14%
UPI15%

Source: Stripe Bizum/UPI refund documentation (395 and 60 days); SEPA Core Direct Debit Rulebook's 56-day no-questions-asked refund right, as cited in our SEPA Direct Debit piece, shown here as a share of Bizum's window for scale.

The dispute clock is the part that can actually cost you money

A missed refund window is annoying. A missed dispute deadline is a loss by default. Bizum gives you 40 calendar days to assemble and submit evidence once a dispute opens — tracking ID, shipping date, proof of purchase for intangible goods, or a record of a refund you already issued. UPI gives you 7. Not 7 business days — 7 calendar days, and Stripe's own guidance for UPI specifically says to submit everything in a single response, because there's no second chance to supplement it afterward the way there sometimes is on other rails. If your dispute workflow routes evidence requests through a support queue that checks in a couple of times a week, that process might be perfectly fine for a Bizum case and still blow through a UPI deadline without anyone noticing until the automatic loss lands.

This is exactly the kind of gap our research into what evidence actually wins a dispute found matters most for digital products: proof of a full refund, specifically, moved win rates by 63 percentage points in Stripe's own million-dispute study. A refund reference you can now actually produce for a UPI payment is a genuinely stronger piece of evidence than "our system shows status: succeeded" — but only if someone pulls it and attaches it inside a 7-day window, not a 40-day one.

What to actually change this week

  • Split your refund and dispute SLAs by payment method, not by region. "Spain" and "India" aren't the right grouping — "Bizum" and "UPI" are, because the clocks attached to each are different enough that a single regional SLA will be wrong for one of them.
  • Route UPI disputes to a same-day alert, not a weekly queue. A 7-calendar-day evidence window doesn't survive a support process built around Bizum's 40 or a card chargeback's 120. If you haven't separated UPI dispute handling from everything else, this release is a reasonable forcing function to do it.
  • Don't quote a Bizum subscriber a renewal date your billing system can't enforce. If Bizum shows up anywhere in your checkout for a subscription product, confirm with your own integration whether that charge is actually a Stripe Billing subscription (it isn't, by Stripe's own documentation) or a manually triggered Payment Link — because the churn risk of a "subscription" that depends on the customer remembering to pay again is completely different from one that renews on its own.
  • Surface the new reference in UPI support macros specifically. Given the 7-day dispute clock, having a concrete reference to hand a confused, canceling UPI subscriber before they escalate to their bank is worth more here than on almost any other rail Stripe supports.
  • Watch reference_status, not just refund status, the same way our Klarna/PayPal/Afterpay piece recommends. A refund that says succeeded with a reference_status still sitting at pending is not yet something a customer's bank app can confirm — treat it as in-flight in your support tooling until the reference actually clears.

What this release doesn't touch

Coverage is still partial everywhere it's always been partial. Alipay, WeChat Pay, GrabPay, and a long list of other Stripe-supported methods still carry no reference field in destination_details at all — Bizum and UPI just moved off that list, nobody else did. And the reference fix changes nothing about the structural asymmetry between the two rails: Bizum staying single-use means every SaaS business taking it needs a plan for subscribers who simply stop manually paying, which is a different flavor of cross-border churn than a declined card or a failed mandate — there's no decline event to dun against, just silence. UPI's 7-day dispute window isn't going anywhere either; Stripe added traceability, not more time.

None of this is a reason to avoid either rail if your subscriber base is actually in Spain or India — both are now mainstream enough that skipping them costs you signups you'd otherwise win. It's a reason to stop treating "payment method support" as a checkbox and start treating each rail's refund window, dispute window, and billing-automation support as three separate numbers that need their own operational answer. Our churn calculator is a quick way to see how much of your reported churn by region is actually arriving as a dispute rather than a clean cancellation — a split that tends to look worse wherever the underlying rail gives support teams the least time to respond. Closing that gap before a subscriber ever has to escalate, with a cancellation flow that captures the request properly in the first place, is the problem CancelFlow exists to solve.

Frequently asked questions

What did Stripe's November 18, 2026 release change for Bizum and UPI refunds?+

It added bizum and upi objects inside destination_details on the Refund object, each carrying a reference and a reference_status field (pending, available, or unavailable). That's the same tracing pattern Stripe shipped for Klarna, PayPal, and Afterpay/Clearpay refunds on October 28, 2026. Before November 18, a Bizum or UPI refund came back with only an overall status — pending, succeeded, failed, or canceled — and no trace number a customer's own bank could use to independently confirm the money moved.

Can I use Bizum to bill a recurring SaaS subscription on Stripe?+

No. Stripe's own payment method support table lists Bizum's usability as single-use, with recurring payments explicitly unsupported, and Bizum has no integration with Stripe Billing, Invoicing, or the Customer Portal at all. It only works through Checkout Sessions or Payment Links, paid once at a time. Any Bizum revenue you see from a subscriber is either a one-off purchase or a renewal you re-collected manually — never an automatic recurring charge.

How long do I actually have to respond to a Bizum or UPI dispute on Stripe?+

Far less time on UPI than on Bizum. A Bizum dispute gives the customer's bank up to 120 days from the purchase date to open a case, and once it's opened you get 40 calendar days to submit evidence, with Stripe issuing a decision within 90 days of that submission. A UPI dispute can be opened within 90 days of purchase, but you only get 7 calendar days to submit your evidence afterward, and the customer's bank decides within 30 days. Both are full disputes, not transaction-level chargebacks you can partially contest — you either win the whole amount back or lose it.

How long does a Bizum or UPI refund actually take to complete?+

Bizum refunds are asynchronous but fast — Stripe's docs say up to 5 minutes, and the money goes straight back to the bank account linked to the buyer's Bizum phone number. UPI refunds are also asynchronous but much slower: up to 7 business days. Neither can be canceled once submitted, and if either fails, Stripe pulls the money back into your Stripe balance and you're responsible for getting it to the customer through a different method.

Try CancelFlow

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.

Start free trial →
← All postsHome