Adds Payment Method support to Top-ups
What’s new
Adds the ability to process top-ups in the US using the Payment Methods API. This change adds two new properties to the Top-up object:
- payment_method : The ID of the PaymentMethod object used for the top-up. Currently only supports us_bank_account payment methods types.
- payment_method_options : The payment method-specific configuration for the top-up. The us _ bank _ account sub-hash includes a network property enum that specifies the US bank transfer network used (defaults to ach ).
Impact
You can now use the Payment Methods API instead of the Sources API when creating and managing Top-ups in the US. To use this new behavior, pass a us_bank_account PaymentMethod ID in the payment_method parameter when creating a top-up, and optionally configure the transfer network using payment_method_options.us_bank_account.network.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| payment_method payment_method_options | Added | Topup |
Upgrade
- View your current API version in Workbench.
- 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 to include Stripe-Version: 2026-07-29. dahlia
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.
Related changes
- Adds the ability to show who initiated a top-up
- Adds new address fields to Accounts v1 for Singapore compliance
- Adds a new Smart Disputes management feature to Account Session embedded components
- Adds new address fields to Accounts v2 for Singapore compliance
- Enables rejecting connected accounts with non-zero balances and controlling whether to pause payouts
- Adds the ability to reverse platform rejections on connected accounts