Public preview
Adds new status and consolidates error codes for money management APIs Public preview
What’s new
This release introduces several enhancements for money management:
- Adds a new pending status to the Financial Account resource to indicate when a Financial Account has been created and is in the process of opening.
- Replaces the description property with metadata in the Financial Account resource.
- Adds additional types to the balance _ transfer object in the Received Credit resource.
- Consolidates and aligns error codes for the methods to create an outbound transfer and create an outbound payment .
| Old error code | New error code |
|---|---|
outbound_transfer_insufficient_funds | insufficient_funds |
outbound_payment_insufficient_funds | insufficient_funds |
outbound_payment_recipient_amount_limit_exceeded | recipient_amount_limit_exceeded |
outbound_payment_recipient_count_limit_exceeded | recipient_count_limit_exceeded |
outbound_payment_recipient_email_does_not_exist | recipient_email_does_not_exist |
outbound_payment_recipient_feature_not_active | recipient_feature_not_active |
Impact
- The new pending status provides greater visibility into Financial Account states when you’re creating accounts.
- Replacing description with metadata allows you to associate more powerful, structured data with Financial Accounts.
- Consolidating error codes across the methods to create an outbound transfer and create an outbound payment simplifies error management for your integration.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| metadata | Added | V2. MoneyManagement. FinancialAccount |
| description | Removed | V2. MoneyManagement. FinancialAccount |
| from_account outbound_payment outbound_transfer | Added | V2. MoneyManagement. ReceivedCredit. balance_transfer |
| Value | Change | Enum |
| pending | Added | V2. MoneyManagement. FinancialAccount. status |
| Fields | Change | From → to |
| V2. MoneyManagement. ReceivedCredit. balance_transfer. type | Changed | literal('payout_v1') → enum('outbound_payment'|'outbound_transfer'|'payout_v1') |
| V2. MoneyManagement. ReceivedCredit. balance_transfer. payout_v1 | Changed | string → nullable(string) |
| Codes | Change | |
| storer_capability_missing storer_capability_not_active | Added | Error. code |
| insufficient_funds | Added | Error. code |
| outbound_payment_insufficient_funds outbound_transfer_insufficient_funds | Removed | Error. code |
| recipient_amount_limit_exceeded recipient_count_limit_exceeded | Added | Error. code |
| outbound_payment_recipient_amount_limit_exceeded outbound_payment_recipient_count_limit_exceeded | Removed | Error. code |
| recipient_email_does_not_exist | Added | Error. code |
| outbound_payment_recipient_email_does_not_exist | Removed | Error. code |
| recipient_feature_not_active | Added | Error. code |
| outbound_payment_recipient_feature_not_active | Removed | Error. code |
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: 2025-06-30. preview
- 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.