# Adds RTP and FedNow as US bank transfer network types for cash balance transactions

## What’s new

Adds `rtp` and `fednow` to the [network](https://docs.stripe.com/api/cash_balance_transactions/object.md?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer-network) property under [funded.bank_transfer.us_bank_transfer](https://docs.stripe.com/api/cash_balance_transactions/object.md?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer) on the [Cash Balance Transaction](https://docs.stripe.com/api/cash_balance_transactions/object.md?api-version=2026-10-28.endive) object. These values represent The Clearing House Real-Time Payments (RTP) network and the Federal Reserve’s FedNow instant payment service. Previously, `network` returned only `ach`, `domestic_wire_us`, or `swift`.

This additive change extends an open enum on a response property. The new values appear only when the upstream banking partner classifies the transfer as an RTP or FedNow payment. Existing transactions aren’t affected.

## Impact

If your integration reads the `funded.bank_transfer.us_bank_transfer.network` property on [Cash Balance Transactions](https://docs.stripe.com/api/cash_balance_transactions/object.md?api-version=2026-10-28.endive) and doesn’t handle unknown enum values, update it to accept `rtp` and `fednow`. For more information about funding with bank transfers, see [Customer balance payments](https://docs.stripe.com/payments/customer-balance.md).

## Changes

#### REST API

| Values | Change | Enum |
| --- | --- | --- |
| `fednow`, `rtp` | Added | [CustomerCashBalanceTransaction.funded.bank_transfer.us_bank_transfer.network](/api/cash_balance_transactions/object?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer-network) |

#### Ruby

This change doesn’t affect the Ruby SDK.

#### Python

| Values | Change | Enum |
| --- | --- | --- |
| `fednow`, `rtp` | Added | [CustomerCashBalanceTransaction.Funded.BankTransfer.UsBankTransfer.network](/api/cash_balance_transactions/object?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer-network) |

#### PHP

| Values | Change | Enum |
| --- | --- | --- |
| `fednow`, `rtp` | Added | [CustomerCashBalanceTransaction.funded.bank_transfer.us_bank_transfer.network](/api/cash_balance_transactions/object?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer-network) |

#### Java

This change doesn’t affect the Java SDK.

#### Node.js

| Values | Change | Enum |
| --- | --- | --- |
| `fednow`, `rtp` | Added | [CustomerCashBalanceTransaction.funded.bank_transfer.us_bank_transfer.network](/api/cash_balance_transactions/object?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer-network) |

#### Go

| Values | Change | Enum |
| --- | --- | --- |
| `fednow`, `rtp` | Added | [CustomerCashBalanceTransactionFundedBankTransferUsBankTransfer.Network](/api/cash_balance_transactions/object?api-version=2026-10-28.endive#customer_cash_balance_transaction_object-funded-bank_transfer-us_bank_transfer-network) |

#### .NET

This change doesn’t affect the .NET SDK.

## 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-10-28.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 the latest version.
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 the latest version.
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 the latest version.
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 the latest version.
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 the latest version.
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 the latest version.
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 the latest version.
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

- [Adds payment intent data configuration when updating Checkout Sessions](https://docs.stripe.com/changelog/endive/2026-10-28/adds-payment-intent-data-configuration-when-updating-checkout-sessions.md)
- [Adds Open USD (OUSD) as a supported token currency for crypto payments](https://docs.stripe.com/changelog/endive/2026-10-28/ousd-token-currency.md)
- [Adds support for requesting Scalapay Payment Links](https://docs.stripe.com/changelog/endive/2026-10-28/scalapay-payment-method-support-payment-links.md)
- [Adds the evidence submission method property to Disputes](https://docs.stripe.com/changelog/endive/2026-10-28/evidence-submission-method-property-disputes.md)
- [Adds the ability to specify the intended submission method for Disputes](https://docs.stripe.com/changelog/endive/2026-10-28/adds-intended-submission-method-for-disputes.md)
- [Adds invoice settings parameters for Checkout Sessions and Payment Links subscriptions](https://docs.stripe.com/changelog/endive/2026-10-28/invoice-settings-parameters-checkout-sessions-payment-links-subscriptions.md)
- [Adds support for submitting evidence to appeal dispute decisions](https://docs.stripe.com/changelog/endive/2026-10-28/evidence-submission-appeal-dispute-decisions.md)
- [Adds refund reference tracking for Klarna, PayPal, and Afterpay Clearpay](https://docs.stripe.com/changelog/endive/2026-10-28/refund-reference-klarna-paypal-afterpay.md)
- [Adds support for specifying card-on-file usage when saving or charging cards](https://docs.stripe.com/changelog/endive/2026-10-28/card-on-file-usage-indicators-support.md)
- [Adds webhook events and error messages for the Standalone 3DS API](https://docs.stripe.com/changelog/endive/2026-10-28/standalone-3ds-error-messages-and-webhook-events.md)
- [Adds validation for Smart Disputes availability when submitting a dispute](https://docs.stripe.com/changelog/endive/2026-10-28/smart-disputes-availability-validation.md)