Adds future requirements field to Accounts v2Breaking changes
What’s new
Adds future_requirements to the Accounts v2 API as a new includable property. Accounts now have two properties that specify any required information that must be collected from the company, individual, or business:
- The future_requirements property specifies what information Stripe will eventually be required to collect.
- The requirements property specifies what information Stripe currently is required to collect.
Why is this a breaking change?
Any requirements previously included in the requirements hash with a requested reason code of future_ are now included in the future_ hash.
Impact
You no longer need to review all individual requirements to determine whether they’re required to unblock capabilities on an account. If requirements.entries is empty, all requested capabilities are active.
Changes
Upgrade
Related changes
- Updates requirements collection parameters for 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 capability to hold EUR funds to Accounts v2
- Adds account and person tokens to Accounts v2 to securely transmit sensitive data