Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenAPI Update #785

Merged
merged 1 commit into from
Apr 29, 2024
Merged

OpenAPI Update #785

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions embedded/openapi/spec3.beta.sdk.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8484,6 +8484,21 @@
"type": "object",
"x-expandableFields": []
},
"checkout_multibanco_payment_method_options": {
"description": "",
"properties": {
"setup_future_usage": {
"description": "Indicates that you intend to make future payments with this PaymentIntent's payment method.\n\nProviding this parameter will [attach the payment method](https://stripe.com/docs/payments/save-during-payment) to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be [attached](https://stripe.com/docs/api/payment_methods/attach) to a Customer after the transaction completes.\n\nWhen processing card payments, Stripe also uses `setup_future_usage` to dynamically optimize your payment flow and comply with regional legislation and network rules, such as [SCA](https://stripe.com/docs/strong-customer-authentication).",
"enum": [
"none"
],
"type": "string"
}
},
"title": "CheckoutMultibancoPaymentMethodOptions",
"type": "object",
"x-expandableFields": []
},
"checkout_oxxo_payment_method_options": {
"description": "",
"properties": {
Expand Down Expand Up @@ -8698,6 +8713,9 @@
"mobilepay": {
"$ref": "#/components/schemas/checkout_mobilepay_payment_method_options"
},
"multibanco": {
"$ref": "#/components/schemas/checkout_multibanco_payment_method_options"
},
"oxxo": {
"$ref": "#/components/schemas/checkout_oxxo_payment_method_options"
},
Expand Down Expand Up @@ -8753,6 +8771,7 @@
"konbini",
"link",
"mobilepay",
"multibanco",
"oxxo",
"p24",
"paynow",
Expand Down Expand Up @@ -88414,6 +88433,20 @@
"title": "payment_method_options_param",
"type": "object"
},
"multibanco": {
"description": "contains details about the Multibanco payment method options.",
"properties": {
"setup_future_usage": {
"description": "Indicates that you intend to make future payments with this PaymentIntent's payment method.\n\nProviding this parameter will [attach the payment method](https://stripe.com/docs/payments/save-during-payment) to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be [attached](https://stripe.com/docs/api/payment_methods/attach) to a Customer after the transaction completes.\n\nWhen processing card payments, Stripe also uses `setup_future_usage` to dynamically optimize your payment flow and comply with regional legislation and network rules, such as [SCA](https://stripe.com/docs/strong-customer-authentication).",
"enum": [
"none"
],
"type": "string"
}
},
"title": "payment_method_options_param",
"type": "object"
},
"oxxo": {
"description": "contains details about the OXXO payment method options.",
"properties": {
Expand Down Expand Up @@ -88729,6 +88762,7 @@
"konbini",
"link",
"mobilepay",
"multibanco",
"oxxo",
"p24",
"paynow",
Expand Down
Loading