diff --git a/openapi/spec3.beta.sdk.json b/openapi/spec3.beta.sdk.json
index 5e2a940f..63a5463a 100644
--- a/openapi/spec3.beta.sdk.json
+++ b/openapi/spec3.beta.sdk.json
@@ -3572,7 +3572,7 @@
             "type": "string"
           },
           "status": {
-            "description": "For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.",
+            "description": "For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In US and India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.",
             "maxLength": 5000,
             "type": "string"
           }
diff --git a/openapi/spec3.beta.sdk.yaml b/openapi/spec3.beta.sdk.yaml
index 6f89a989..f386e4b7 100644
--- a/openapi/spec3.beta.sdk.yaml
+++ b/openapi/spec3.beta.sdk.yaml
@@ -3429,7 +3429,8 @@ components:
             For external accounts, possible values are `new`, `errored` and
             `verification_failed`. If a payouts fails, the status is set to
             `errored` and scheduled payouts are stopped until account details
-            are updated. In India, if we can't [verify the owner of the bank
+            are updated. In US and India, if we can't [verify the owner of the
+            bank
             account](https://support.stripe.com/questions/bank-account-ownership-verification),
             we'll set the status to `verification_failed`. Other validations
             aren't run against external accounts because they're only used for
diff --git a/openapi/spec3.json b/openapi/spec3.json
index fd666193..f03ca53d 100644
--- a/openapi/spec3.json
+++ b/openapi/spec3.json
@@ -2689,7 +2689,7 @@
             "type": "string"
           },
           "status": {
-            "description": "For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.",
+            "description": "For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In US and India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.",
             "maxLength": 5000,
             "type": "string"
           }
diff --git a/openapi/spec3.sdk.json b/openapi/spec3.sdk.json
index ebff0a26..9eb9f855 100644
--- a/openapi/spec3.sdk.json
+++ b/openapi/spec3.sdk.json
@@ -3322,7 +3322,7 @@
             "type": "string"
           },
           "status": {
-            "description": "For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.",
+            "description": "For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In US and India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.",
             "maxLength": 5000,
             "type": "string"
           }
diff --git a/openapi/spec3.sdk.yaml b/openapi/spec3.sdk.yaml
index 5f962fd4..bd9b3160 100644
--- a/openapi/spec3.sdk.yaml
+++ b/openapi/spec3.sdk.yaml
@@ -3197,7 +3197,8 @@ components:
             For external accounts, possible values are `new`, `errored` and
             `verification_failed`. If a payouts fails, the status is set to
             `errored` and scheduled payouts are stopped until account details
-            are updated. In India, if we can't [verify the owner of the bank
+            are updated. In US and India, if we can't [verify the owner of the
+            bank
             account](https://support.stripe.com/questions/bank-account-ownership-verification),
             we'll set the status to `verification_failed`. Other validations
             aren't run against external accounts because they're only used for
diff --git a/openapi/spec3.yaml b/openapi/spec3.yaml
index 03472f22..e8b2011c 100644
--- a/openapi/spec3.yaml
+++ b/openapi/spec3.yaml
@@ -2669,7 +2669,8 @@ components:
             For external accounts, possible values are `new`, `errored` and
             `verification_failed`. If a payouts fails, the status is set to
             `errored` and scheduled payouts are stopped until account details
-            are updated. In India, if we can't [verify the owner of the bank
+            are updated. In US and India, if we can't [verify the owner of the
+            bank
             account](https://support.stripe.com/questions/bank-account-ownership-verification),
             we'll set the status to `verification_failed`. Other validations
             aren't run against external accounts because they're only used for