stripe 20.1.0-beta.1 → 20.1.1

package/types/Capabilities.d.ts

@@ -5,7 +5,7 @@ declare module 'stripe' {
     /**
      * This is an object representing a capability for a Stripe account.
      *
-     * Related guide: [Account capabilities](https://stripe.com/docs/connect/account-capabilities)
+     * Related guide: [Account capabilities](https://docs.stripe.com/connect/account-capabilities)
      */
     interface Capability {
       /**
@@ -46,7 +46,7 @@ declare module 'stripe' {
     namespace Capability {
       interface FutureRequirements {
         /**
-         * Fields that are due and can be satisfied by providing the corresponding alternative fields instead.
+         * Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same `original_fields_due`. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing `original_fields_due` again also serves as a pathway for attempting to resolve the fields.
          */
         alternatives: Array<FutureRequirements.Alternative> | null;
 
@@ -56,7 +56,7 @@ declare module 'stripe' {
         current_deadline: number | null;
 
         /**
-         * Fields that need to be collected to keep the capability enabled. If not collected by `future_requirements[current_deadline]`, these fields will transition to the main `requirements` hash.
+         * Fields that need to be resolved to keep the capability enabled. If not resolved by `future_requirements[current_deadline]`, these fields will transition to the main `requirements` hash.
          */
         currently_due: Array<string>;
 
@@ -66,7 +66,7 @@ declare module 'stripe' {
         disabled_reason: FutureRequirements.DisabledReason | null;
 
         /**
-         * Fields that are `currently_due` and need to be collected again because validation or verification failed.
+         * Details about validation and verification failures for `due` requirements that must be resolved.
          */
         errors: Array<FutureRequirements.Error>;
 
@@ -76,12 +76,12 @@ declare module 'stripe' {
         eventually_due: Array<string>;
 
         /**
-         * Fields that weren't collected by `requirements.current_deadline`. These fields need to be collected to enable the capability on the account. New fields will never appear here; `future_requirements.past_due` will always be a subset of `requirements.past_due`.
+         * Fields that haven't been resolved by `requirements.current_deadline`. These fields need to be resolved to enable the capability on the account. `future_requirements.past_due` is a subset of `requirements.past_due`.
          */
         past_due: Array<string>;
 
         /**
-         * Fields that might become required depending on the results of verification or review. It's an empty array unless an asynchronous verification is pending. If verification fails, these fields move to `eventually_due` or `currently_due`. Fields might appear in `eventually_due` or `currently_due` and in `pending_verification` if verification fails but another verification is still pending.
+         * Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending.
          */
         pending_verification: Array<string>;
       }
@@ -89,12 +89,12 @@ declare module 'stripe' {
       namespace FutureRequirements {
         interface Alternative {
           /**
-           * Fields that can be provided to satisfy all fields in `original_fields_due`.
+           * Fields that can be provided to resolve all fields in `original_fields_due`.
            */
           alternative_fields_due: Array<string>;
 
           /**
-           * Fields that are due and can be satisfied by providing all fields in `alternative_fields_due`.
+           * Fields that are due and can be resolved by providing all fields in `alternative_fields_due`.
            */
           original_fields_due: Array<string>;
         }
@@ -174,7 +174,6 @@ declare module 'stripe' {
             | 'invalid_url_website_other'
             | 'invalid_value_other'
             | 'unsupported_business_type'
-            | 'verification_data_not_found'
             | 'verification_directors_mismatch'
             | 'verification_document_address_mismatch'
             | 'verification_document_address_missing'
@@ -233,7 +232,7 @@ declare module 'stripe' {
 
       interface Requirements {
         /**
-         * Fields that are due and can be satisfied by providing the corresponding alternative fields instead.
+         * Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same `original_fields_due`. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing `original_fields_due` again also serves as a pathway for attempting to resolve the fields.
          */
         alternatives: Array<Requirements.Alternative> | null;
 
@@ -243,17 +242,17 @@ declare module 'stripe' {
         current_deadline: number | null;
 
         /**
-         * Fields that need to be collected to keep the capability enabled. If not collected by `current_deadline`, these fields appear in `past_due` as well, and the capability is disabled.
+         * Fields that need to be resolved to keep the capability enabled. If not resolved by `current_deadline`, these fields will appear in `past_due` as well, and the capability is disabled.
          */
         currently_due: Array<string>;
 
         /**
-         * Description of why the capability is disabled. [Learn more about handling verification issues](https://stripe.com/docs/connect/handling-api-verification).
+         * Description of why the capability is disabled. [Learn more about handling verification issues](https://docs.stripe.com/connect/handling-api-verification).
          */
         disabled_reason: Requirements.DisabledReason | null;
 
         /**
-         * Fields that are `currently_due` and need to be collected again because validation or verification failed.
+         * Details about validation and verification failures for `due` requirements that must be resolved.
          */
         errors: Array<Requirements.Error>;
 
@@ -263,12 +262,12 @@ declare module 'stripe' {
         eventually_due: Array<string>;
 
         /**
-         * Fields that weren't collected by `current_deadline`. These fields need to be collected to enable the capability on the account.
+         * Fields that haven't been resolved by `current_deadline`. These fields need to be resolved to enable the capability on the account.
          */
         past_due: Array<string>;
 
         /**
-         * Fields that might become required depending on the results of verification or review. It's an empty array unless an asynchronous verification is pending. If verification fails, these fields move to `eventually_due`, `currently_due`, or `past_due`. Fields might appear in `eventually_due`, `currently_due`, or `past_due` and in `pending_verification` if verification fails but another verification is still pending.
+         * Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending.
          */
         pending_verification: Array<string>;
       }
@@ -276,12 +275,12 @@ declare module 'stripe' {
       namespace Requirements {
         interface Alternative {
           /**
-           * Fields that can be provided to satisfy all fields in `original_fields_due`.
+           * Fields that can be provided to resolve all fields in `original_fields_due`.
            */
           alternative_fields_due: Array<string>;
 
           /**
-           * Fields that are due and can be satisfied by providing all fields in `alternative_fields_due`.
+           * Fields that are due and can be resolved by providing all fields in `alternative_fields_due`.
            */
           original_fields_due: Array<string>;
         }
@@ -361,7 +360,6 @@ declare module 'stripe' {
             | 'invalid_url_website_other'
             | 'invalid_value_other'
             | 'unsupported_business_type'
-            | 'verification_data_not_found'
             | 'verification_directors_mismatch'
             | 'verification_document_address_mismatch'
             | 'verification_document_address_missing'

package/types/Cards.d.ts

@@ -7,7 +7,7 @@ declare module 'stripe' {
      * later. You can also store multiple debit cards on a recipient in order to
      * transfer to those cards later.
      *
-     * Related guide: [Card payments with Sources](https://stripe.com/docs/sources/cards)
+     * Related guide: [Card payments with Sources](https://docs.stripe.com/sources/cards)
      */
     interface Card {
       /**
@@ -77,11 +77,6 @@ declare module 'stripe' {
        */
       brand: string;
 
-      /**
-       * The [product code](https://stripe.com/docs/card-product-codes) that identifies the specific program or product associated with a card. (For internal use only and not typically available in standard API requests.)
-       */
-      brand_product?: string | null;
-
       /**
        * Two-letter ISO code representing the country of the card. You could use this attribute to get a sense of the international breakdown of cards you've collected.
        */
@@ -160,7 +155,7 @@ declare module 'stripe' {
       last4: string;
 
       /**
-       * Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
+       * Set of [key-value pairs](https://docs.stripe.com/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
        */
       metadata: Stripe.Metadata | null;
 

package/types/CashBalances.d.ts

@@ -12,7 +12,7 @@ declare module 'stripe' {
       object: 'cash_balance';
 
       /**
-       * A hash of all cash balances available to this customer. You cannot delete a customer with any cash balances, even if the balance is 0. Amounts are represented in the [smallest currency unit](https://stripe.com/docs/currencies#zero-decimal).
+       * A hash of all cash balances available to this customer. You cannot delete a customer with any cash balances, even if the balance is 0. Amounts are represented in the [smallest currency unit](https://docs.stripe.com/currencies#zero-decimal).
        */
       available: {
         [key: string]: number;
@@ -24,9 +24,9 @@ declare module 'stripe' {
       customer: string;
 
       /**
-       * The ID of the account whose cash balance this object represents.
+       * The ID of an Account representing a customer whose cash balance this object represents.
        */
-      customer_account?: string | null;
+      customer_account: string | null;
 
       /**
        * Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.