# Adds refund reference tracking for Bizum and UPI

## What’s new

Adds the [bizum](https://docs.stripe.com/api/refunds/object.md?api-version=2026-11-18.endive#refund_object-destination_details-bizum) and [upi](https://docs.stripe.com/api/refunds/object.md?api-version=2026-11-18.endive#refund_object-destination_details-upi) properties to [destination_details](https://docs.stripe.com/api/refunds/object.md?api-version=2026-11-18.endive#refund_object-destination_details) on the [Refund](https://docs.stripe.com/api/refunds/object.md?api-version=2026-11-18.endive) object for [Bizum](https://docs.stripe.com/payments/bizum.md) and [UPI](https://docs.stripe.com/payments/upi.md) payments. These read-only properties include [reference](https://docs.stripe.com/api/refunds/object.md?api-version=2026-11-18.endive#refund_object-destination_details-bizum-reference) and [reference_status](https://docs.stripe.com/api/refunds/object.md?api-version=2026-11-18.endive#refund_object-destination_details-bizum-reference_status). They appear in responses when you [create](https://docs.stripe.com/api/refunds/create.md?api-version=2026-11-18.endive) or [retrieve](https://docs.stripe.com/api/refunds/retrieve.md?api-version=2026-11-18.endive) a Refund. They also appear in [refund.updated](https://docs.stripe.com/api/events/types.md?api-version=2026-11-18.endive#event_types-refund.updated) and [refund.failed](https://docs.stripe.com/api/events/types.md?api-version=2026-11-18.endive#event_types-refund.failed) events.

The `reference` property contains the refund reference ID assigned by the payment method provider. The `reference_status` property indicates whether the reference is `pending`, `available`, or `unavailable`. These properties use the same refund reference pattern already supported for payment methods such as Klarna, PayPal, and Afterpay Clearpay.

## Impact

Use the `reference` and `reference_status` properties in `destination_details` to retrieve reference information for Bizum and UPI refunds through the API, without contacting Stripe support. Share the `reference` with your customer so they can trace the refund with their bank, including when the refund fails.

## Changes

#### REST API

| Parameters | Change | Resources or endpoints |
| --- | --- | --- |
| `bizum`, `upi` | Added | [Refund.destination_details](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### Ruby

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `bizum`, `upi` | Added | [Refund::DestinationDetail](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### Python

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `bizum`, `upi` | Added | [Refund.DestinationDetail](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### PHP

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `bizum`, `upi` | Added | [Refund.destination_details](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### Java

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `bizum`, `upi` | Added | [Refund.destination_details](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### Node.js

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `bizum`, `upi` | Added | [Refund.destination_details](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### Go

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `Bizum`, `UPI` | Added | [RefundDestinationDetails](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

#### .NET

| Parameters | Change | Resources or methods |
| --- | --- | --- |
| `Bizum`, `Upi` | Added | [Refund.DestinationDetails](/api/refunds/object?api-version=2026-11-18.endive#refund_object-destination_details) |

## Upgrade

#### REST API

1. [View your current API version](https://docs.stripe.com/workbench/guides.md#view-api-versions) in Workbench.
2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
   - If you don’t use an SDK, update your [API requests](https://docs.stripe.com/api-versions.md#how-versions-are-specified-in-requests) to include `Stripe-Version: 2026-11-18.endive`
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Ruby

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Ruby SDK to [v21.1.0](https://github.com/stripe/stripe-ruby/releases/tag/v21.1.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Python

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Python SDK to [v17.1.0](https://github.com/stripe/stripe-python/releases/tag/v17.1.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### PHP

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your PHP SDK to [v23.1.0](https://github.com/stripe/stripe-php/releases/tag/v23.1.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Java

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Java SDK to [v34.2.0](https://github.com/stripe/stripe-java/releases/tag/v34.2.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Node.js

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Node SDK to [v23.2.0](https://github.com/stripe/stripe-node/releases/tag/v23.2.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Go

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Go SDK to [v87.2.0](https://github.com/stripe/stripe-go/releases/tag/v87.2.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### .NET

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your .NET SDK to [v53.2.0](https://github.com/stripe/stripe-dotnet/releases/tag/v53.2.0)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

## Related changes

- [Allows updating the capture method on payment links](https://docs.stripe.com/changelog/endive/2026-11-18/payment-links-update-capture-method.md)
- [Adds funding source details for Link payments on the Charge object](https://docs.stripe.com/changelog/endive/2026-11-18/adds-card-details-for-link-payments-to-the-charge-object.md)
- [Adds support for car rental and lodging industry metadata](https://docs.stripe.com/changelog/endive/2026-11-18/car-rental-and-lodging-industry-metadata.md)
- [Adds a fingerprint property for PayPay payments](https://docs.stripe.com/changelog/endive/2026-11-18/fingerprint-property-paypay-payments.md)
