Update services based on v281 of Stripe OpenApi SDK

Reference: https://github.com/stripe/openapi/releases/tag/v281
beam-community · Mar 28, 2023 · 2efcaf6 · 2efcaf6
1 parent 5403b89
commit 2efcaf6
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/.latest-tag-stripe-openapi-sdk b/.latest-tag-stripe-openapi-sdk
@@ -1 +1 @@
-v278
+v281
diff --git a/priv/openapi/spec3.sdk.json b/priv/openapi/spec3.sdk.json
@@ -2843,7 +2843,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 transfer sent to this bank account fails, we'll set the status to `errored` and will not continue to send transfers until the bank details are updated.\n\nFor external accounts, possible values are `new` and `errored`. Validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply. If a transfer fails, the status is set to `errored` and transfers are stopped until account details are updated.",
+            "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 transfer sent to this bank account fails, we'll set the status to `errored` and will not continue to send transfers until the bank details are updated.\n\nFor external accounts, possible values are `new`, `errored` and `verification_failed`. If a transfer fails, the status is set to `errored` and transfers 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.",
             "maxLength": 5000,
             "type": "string"
           }
@@ -13927,15 +13927,15 @@
           "status": {
             "description": "The status of the invoice, one of `draft`, `open`, `paid`, `uncollectible`, or `void`. [Learn more](https://stripe.com/docs/billing/invoices/workflow#workflow-overview)",
             "enum": [
-              "deleted",
               "draft",
               "open",
               "paid",
               "uncollectible",
               "void"
             ],
             "nullable": true,
-            "type": "string"
+            "type": "string",
+            "x-stripeBypassValidation": true
           },
           "status_transitions": {
             "$ref": "#/components/schemas/invoices_status_transitions"
@@ -73168,8 +73168,8 @@
                 "uncollectible",
                 "void"
               ],
-              "maxLength": 5000,
-              "type": "string"
+              "type": "string",
+              "x-stripeBypassValidation": true
             },
             "style": "form"
           },