diff --git a/types/2019-12-03/AccountLinks.d.ts b/types/2019-12-03/AccountLinks.d.ts index 970d788bd2..2e21f641e2 100644 --- a/types/2019-12-03/AccountLinks.d.ts +++ b/types/2019-12-03/AccountLinks.d.ts @@ -44,7 +44,7 @@ declare module 'stripe' { /** * The type of account link the user is requesting. Possible values are `custom_account_verification` or `custom_account_update`. */ - type: string; + type: AccountLinkCreateParams.Type; /** * Which information the platform needs to collect from the user. One of `currently_due` or `eventually_due`. Default is `currently_due`. @@ -59,6 +59,8 @@ declare module 'stripe' { namespace AccountLinkCreateParams { type Collect = 'currently_due' | 'eventually_due'; + + type Type = 'custom_account_update' | 'custom_account_verification'; } class AccountLinksResource { diff --git a/types/2019-12-03/Charges.d.ts b/types/2019-12-03/Charges.d.ts index 875a5b4fc4..d269224dd2 100644 --- a/types/2019-12-03/Charges.d.ts +++ b/types/2019-12-03/Charges.d.ts @@ -231,7 +231,7 @@ declare module 'stripe' { transfer_data: Charge.TransferData | null; /** - * A string that identifies this transaction as part of a group. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#grouping-transactions) for details. + * A string that identifies this transaction as part of a group. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#transfer-options) for details. */ transfer_group: string | null; } @@ -1276,7 +1276,7 @@ declare module 'stripe' { transfer_data?: ChargeCreateParams.TransferData; /** - * A string that identifies this transaction as part of a group. For details, see [Grouping transactions](https://stripe.com/docs/connect/charges-transfers#grouping-transactions). + * A string that identifies this transaction as part of a group. For details, see [Grouping transactions](https://stripe.com/docs/connect/charges-transfers#transfer-options). */ transfer_group?: string; } @@ -1378,7 +1378,7 @@ declare module 'stripe' { shipping?: ChargeUpdateParams.Shipping; /** - * A string that identifies this transaction as part of a group. `transfer_group` may only be provided if it has not been set. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#grouping-transactions) for details. + * A string that identifies this transaction as part of a group. `transfer_group` may only be provided if it has not been set. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#transfer-options) for details. */ transfer_group?: string; } @@ -1489,7 +1489,7 @@ declare module 'stripe' { transfer_data?: ChargeCaptureParams.TransferData; /** - * A string that identifies this transaction as part of a group. `transfer_group` may only be provided if it has not been set. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#grouping-transactions) for details. + * A string that identifies this transaction as part of a group. `transfer_group` may only be provided if it has not been set. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#transfer-options) for details. */ transfer_group?: string; } diff --git a/types/2019-12-03/SubscriptionItems.d.ts b/types/2019-12-03/SubscriptionItems.d.ts index 281753dfb9..1b37fce783 100644 --- a/types/2019-12-03/SubscriptionItems.d.ts +++ b/types/2019-12-03/SubscriptionItems.d.ts @@ -108,7 +108,9 @@ declare module 'stripe' { metadata?: MetadataParam; /** - * Use `allow_incomplete` to create subscriptions with `status=incomplete` if the first invoice cannot be paid. Creating subscriptions with this status allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. + * Use `allow_incomplete` to transition the subscription to `status=past_due` if a payment is required but cannot be paid. This allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. + * + * Use `pending_if_incomplete` to update the subscription using [pending updates](https://stripe.com/docs/billing/subscriptions/pending-updates). When you use `pending_if_incomplete` you can only pass the parameters [supported by pending updates](https://stripe.com/docs/billing/pending-updates-reference#supported-attributes). * * Use `error_if_incomplete` if you want Stripe to return an HTTP 402 status code if a subscription's first invoice cannot be paid. For example, if a payment method requires 3DS authentication due to SCA regulation and further user action is needed, this parameter does not create a subscription and returns an error instead. This was the default behavior for API versions prior to 2019-03-14. See the [changelog](https://stripe.com/docs/upgrades#2019-03-14) to learn more. */ @@ -194,7 +196,9 @@ declare module 'stripe' { off_session?: boolean; /** - * Use `allow_incomplete` to create subscriptions with `status=incomplete` if the first invoice cannot be paid. Creating subscriptions with this status allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. + * Use `allow_incomplete` to transition the subscription to `status=past_due` if a payment is required but cannot be paid. This allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. + * + * Use `pending_if_incomplete` to update the subscription using [pending updates](https://stripe.com/docs/billing/subscriptions/pending-updates). When you use `pending_if_incomplete` you can only pass the parameters [supported by pending updates](https://stripe.com/docs/billing/pending-updates-reference#supported-attributes). * * Use `error_if_incomplete` if you want Stripe to return an HTTP 402 status code if a subscription's first invoice cannot be paid. For example, if a payment method requires 3DS authentication due to SCA regulation and further user action is needed, this parameter does not create a subscription and returns an error instead. This was the default behavior for API versions prior to 2019-03-14. See the [changelog](https://stripe.com/docs/upgrades#2019-03-14) to learn more. */ diff --git a/types/2019-12-03/Subscriptions.d.ts b/types/2019-12-03/Subscriptions.d.ts index f76b078e0c..78d3a5972c 100644 --- a/types/2019-12-03/Subscriptions.d.ts +++ b/types/2019-12-03/Subscriptions.d.ts @@ -358,6 +358,8 @@ declare module 'stripe' { * Use `allow_incomplete` to create subscriptions with `status=incomplete` if the first invoice cannot be paid. Creating subscriptions with this status allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. * * Use `error_if_incomplete` if you want Stripe to return an HTTP 402 status code if a subscription's first invoice cannot be paid. For example, if a payment method requires 3DS authentication due to SCA regulation and further user action is needed, this parameter does not create a subscription and returns an error instead. This was the default behavior for API versions prior to 2019-03-14. See the [changelog](https://stripe.com/docs/upgrades#2019-03-14) to learn more. + * + * `pending_if_incomplete` is only used with updates and cannot be passed when creating a subscription. */ payment_behavior?: SubscriptionCreateParams.PaymentBehavior; @@ -570,7 +572,9 @@ declare module 'stripe' { off_session?: boolean; /** - * Use `allow_incomplete` to create subscriptions with `status=incomplete` if the first invoice cannot be paid. Creating subscriptions with this status allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. + * Use `allow_incomplete` to transition the subscription to `status=past_due` if a payment is required but cannot be paid. This allows you to manage scenarios where additional user actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://stripe.com/docs/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior. + * + * Use `pending_if_incomplete` to update the subscription using [pending updates](https://stripe.com/docs/billing/subscriptions/pending-updates). When you use `pending_if_incomplete` you can only pass the parameters [supported by pending updates](https://stripe.com/docs/billing/pending-updates-reference#supported-attributes). * * Use `error_if_incomplete` if you want Stripe to return an HTTP 402 status code if a subscription's first invoice cannot be paid. For example, if a payment method requires 3DS authentication due to SCA regulation and further user action is needed, this parameter does not create a subscription and returns an error instead. This was the default behavior for API versions prior to 2019-03-14. See the [changelog](https://stripe.com/docs/upgrades#2019-03-14) to learn more. */ diff --git a/types/2019-12-03/Transfers.d.ts b/types/2019-12-03/Transfers.d.ts index 2dce8e5091..42b3d112f4 100644 --- a/types/2019-12-03/Transfers.d.ts +++ b/types/2019-12-03/Transfers.d.ts @@ -85,7 +85,7 @@ declare module 'stripe' { source_type: string | null; /** - * A string that identifies this transaction as part of a group. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#grouping-transactions) for details. + * A string that identifies this transaction as part of a group. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#transfer-options) for details. */ transfer_group: string | null; } @@ -132,7 +132,7 @@ declare module 'stripe' { source_type?: TransferCreateParams.SourceType; /** - * A string that identifies this transaction as part of a group. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#grouping-transactions) for details. + * A string that identifies this transaction as part of a group. See the [Connect documentation](https://stripe.com/docs/connect/charges-transfers#transfer-options) for details. */ transfer_group?: string; }