Updates requirements collection parameters for Accounts v2Breaking changes
What’s new
The defaults.responsibilities.requirements_collector parameter replaces the deprecated requirements.collector parameter. You use the requirements_ parameter to specify whether Stripe or your platform is responsible for collecting requirements on connected accounts while using Accounts v2.
This change also updates the enum values for requirements.entries[].reference.type, which specify which API resource is related to a given requirement.
Why is this a breaking change?
This is a breaking change because:
- The
requirements_parameter replaces thecollector collectorparameter. - Parameter enum values in
requirements.are now more specific (for example,entries[]. reference. type payment_andmethod person). This could cause validation errors if your integration expects the previous generic value ofresource.
Impact
The updated parameter enum values for requirements. may require changes to how you handle specific requirements in your verification flows.
If your integration relies on the collector parameter or the resource enum value, you need to update your code before upgrading to this API version to avoid integration failures.
Changes
Upgrade
Related changes
- Adds future requirements field to Accounts v2
- PaymentMethods can now list payment methods for a customer account using Accounts v2
- Adds support for PayPay to Accounts
- Adds support for Konbini payments and Japanese statement descriptors in Accounts v2
- Adds the capabilty to hold EUR funds to Accounts v2
- Adds account and person tokens to Accounts v2 to securely transmit sensitive data