#Rename it stable version how to#
#Rename it stable version update#
#Rename it stable version upgrade#
#Rename it stable version full#

The boolean values that indicate the associated owners, executives, or directors have been provided now appear as company.owners_provided, company.executives_provided, or company.directors_provided instead of relationship.owner, relationship.executive, or relationship.director, respectively.

When a director’s date of birth is required, it will appear as, , and instead of relationship.director.

When an executive’s ID number is required, it will appear as executives.id_number instead of relationship.executive.

#Rename it stable version full#

When an owner’s full name is required, it will appear as owners.first_name and owners.last_name instead of relationship.owner.

When the representative’s phone number is required, it will appear as representative.phone instead of relationship.representative.

Person requirements will be previewed as follows:

Fields that are required for persons with representative, owner, director, and executive roles will be prefixed with representative, owners, directors, and executives, respectively.

The requirements hash on the Account and Capability objects, and the verification_fields hash on the Country Spec object have newly formatted strings for requirements that are related to key persons associated with an account: This switches the version used by API calls that don’t have the Stripe-Version header and also switches the version used to render objects sent to your webhooks.

#Rename it stable version upgrade#

When you’re confident that your code can handle the latest API version, click the Upgrade version button in your Dashboard.

Trigger the event in test mode and validate that your code works for the new structure.

Change the version of a test webhook endpoint to the version you want to test.

#Rename it stable version update#

Update your webhook code to handle both the old and new version of each object.Check for breaking changes to see which objects will be structured differently.To safely upgrade your webhooks, Stripe recommends that you:

#Rename it stable version how to#

Learn how to manage versioning in our server-side libraries.įor webhooks, you can override the version of a single test webhook endpoint in your Dashboard. To test a newer version for API calls, set the Stripe-Version header (in live or test mode). When performing an API upgrade, make sure that you specify the API version that you’re integrating against in your code instead of relying on your account’s default API version. To see what version you’re running and upgrade to the latest one, visit your Dashboard. See the API changelog for details about how your default API version will impact these operations. Automated Billing operations performed by Stripe (for example, generating an invoice for a new subscription period) use your account’s default API version.The structure of objects sent to your webhook endpoints (both Account and Connect ones.) If an endpoint has an explicit version set, it will remain unaffected.The structure of objects received with Stripe.js methods such as confirmCardPayment.The API calls you make without a Stripe-Version header: the parameters you can send and the structure of objects returned.

If you’re running an older version of the API, upgrade to the latest version to take advantage of new functionality or to streamline responses so the API is faster for you. Your webhook listener should gracefully handle unfamiliar event types. If for example you’re using MySQL, you should store IDs in a VARCHAR(255) COLLATE utf8_bin column (the COLLATE configuration ensures case-sensitivity in lookups). You can safely assume object IDs we generate will never exceed 255 characters, but you should be able to handle IDs of up to that length. This includes adding or removing fixed prefixes (such as ch_ on charge IDs). Stripe considers the following changes to be backwards-compatible:Īdding new optional request parameters to existing API methods.Īdding new properties to existing API responses.Ĭhanging the order of properties in existing API responses.Ĭhanging the length or format of opaque strings, such as object IDs, error messages, and other human-readable strings. If you make requests on behalf of other users using Connect, we’ll use your application’s API version, making it easy for you to write code that works for all your users no matter what API versions they’re individually running. To avoid breaking your code, we don’t change your version until you’re ready to upgrade. When a breaking change is introduced to the Stripe API, a new dated version is released. Your version gets set the first time you make an API request. Your API version controls the API and webhook behavior you see (for example, what properties you see in responses, what parameters you’re permitted to send in requests, and so on).