Skip to content

Commit

Permalink
OpenAPI Update (#651)
Browse files Browse the repository at this point in the history
Update OpenAPI for 2d119ba7b6dfefa7fb5c21343b30c57ebb9ce746

Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
  • Loading branch information
stripe-openapi[bot] committed Feb 7, 2024
1 parent e784d66 commit 143cde5
Show file tree
Hide file tree
Showing 2 changed files with 71 additions and 2 deletions.
38 changes: 37 additions & 1 deletion embedded/openapi/spec3.beta.sdk.json
Expand Up @@ -35003,7 +35003,16 @@
},
"payment_intent_payment_method_options_blik": {
"description": "",
"properties": {},
"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",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_blik",
"type": "object",
"x-expandableFields": []
Expand Down Expand Up @@ -130904,6 +130913,15 @@
"description": "The 6-digit BLIK code that a customer has generated using their banking application. Can only be set on confirmation.",
"maxLength": 5000,
"type": "string"
},
"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).\n\nIf `setup_future_usage` is already set and you are performing a request using a publishable key, you may only update the value from `on_session` to `off_session`.",
"enum": [
"",
"none"
],
"type": "string",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_param",
Expand Down Expand Up @@ -134765,6 +134783,15 @@
"description": "The 6-digit BLIK code that a customer has generated using their banking application. Can only be set on confirmation.",
"maxLength": 5000,
"type": "string"
},
"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).\n\nIf `setup_future_usage` is already set and you are performing a request using a publishable key, you may only update the value from `on_session` to `off_session`.",
"enum": [
"",
"none"
],
"type": "string",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_param",
Expand Down Expand Up @@ -139562,6 +139589,15 @@
"description": "The 6-digit BLIK code that a customer has generated using their banking application. Can only be set on confirmation.",
"maxLength": 5000,
"type": "string"
},
"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).\n\nIf `setup_future_usage` is already set and you are performing a request using a publishable key, you may only update the value from `on_session` to `off_session`.",
"enum": [
"",
"none"
],
"type": "string",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_param",
Expand Down
35 changes: 34 additions & 1 deletion embedded/openapi/spec3.json
Expand Up @@ -23056,7 +23056,16 @@
},
"payment_intent_payment_method_options_blik": {
"description": "",
"properties": {},
"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",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_blik",
"type": "object",
"x-expandableFields": []
Expand Down Expand Up @@ -94462,6 +94471,14 @@
"code": {
"maxLength": 5000,
"type": "string"
},
"setup_future_usage": {
"enum": [
"",
"none"
],
"type": "string",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_param",
Expand Down Expand Up @@ -97079,6 +97096,14 @@
"code": {
"maxLength": 5000,
"type": "string"
},
"setup_future_usage": {
"enum": [
"",
"none"
],
"type": "string",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_param",
Expand Down Expand Up @@ -99835,6 +99860,14 @@
"code": {
"maxLength": 5000,
"type": "string"
},
"setup_future_usage": {
"enum": [
"",
"none"
],
"type": "string",
"x-stripeBypassValidation": true
}
},
"title": "payment_intent_payment_method_options_param",
Expand Down

0 comments on commit 143cde5

Please sign in to comment.