Skip to content

Commit

Permalink
OpenAPI Update (#650)
Browse files Browse the repository at this point in the history 
Update OpenAPI for de4fea8614a0c04d74f2bd8f0174f59619e2fa51

Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
  • Loading branch information
@stripe-openapi
stripe-openapi[bot] authored Feb 6, 2024
1 parent a011a96 commit e784d66
Show file tree
Hide file tree
Showing 2 changed files with 87 additions and 0 deletions.
70 changes: 70 additions & 0 deletions embedded/openapi/spec3.beta.sdk.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8880,6 +8880,15 @@
]
}
},
"payment_method_options": {
"anyOf": [
{
"$ref": "#/components/schemas/confirmation_tokens_resource_payment_method_options"
}
],
"description": "Payment-method-specific configuration for this ConfirmationToken.",
"nullable": true
},
"payment_method_preview": {
"anyOf": [
{
Expand Down Expand Up @@ -8929,6 +8938,7 @@
"object",
"payment_intent",
"payment_method",
"payment_method_options",
"payment_method_preview",
"return_url",
"setup_future_usage",
Expand All @@ -8940,6 +8950,7 @@
"x-expandableFields": [
"mandate_data",
"payment_method",
"payment_method_options",
"payment_method_preview",
"shipping"
],
Expand Down Expand Up @@ -9026,6 +9037,45 @@
"type": "object",
"x-expandableFields": []
},
"confirmation_tokens_resource_payment_method_options": {
"description": "Payment-method-specific configuration",
"properties": {
"card": {
"anyOf": [
{
"$ref": "#/components/schemas/confirmation_tokens_resource_payment_method_options_resource_card"
}
],
"description": "This hash contains the card payment method options.",
"nullable": true
}
},
"required": [
"card"
],
"title": "ConfirmationTokensResourcePaymentMethodOptions",
"type": "object",
"x-expandableFields": [
"card"
]
},
"confirmation_tokens_resource_payment_method_options_resource_card": {
"description": "This hash contains the card payment method options.",
"properties": {
"cvc_token": {
"description": "The `cvc_update` Token collected from the Payment Element.",
"maxLength": 5000,
"nullable": true,
"type": "string"
}
},
"required": [
"cvc_token"
],
"title": "ConfirmationTokensResourcePaymentMethodOptionsResourceCard",
"type": "object",
"x-expandableFields": []
},
"confirmation_tokens_resource_payment_method_preview": {
"description": "Details of the PaymentMethod collected by Payment Element",
"properties": {
Expand Down Expand Up @@ -35047,6 +35097,10 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down Expand Up @@ -35336,6 +35390,10 @@
"installments": {
"$ref": "#/components/schemas/payment_flows_installment_options"
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down Expand Up @@ -131095,6 +131153,10 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down Expand Up @@ -134952,6 +135014,10 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down Expand Up @@ -139745,6 +139811,10 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down
17 changes: 17 additions & 0 deletions embedded/openapi/spec3.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -23150,6 +23150,10 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down Expand Up @@ -23403,6 +23407,10 @@
"installments": {
"$ref": "#/components/schemas/payment_flows_installment_options"
},
"require_cvc_recollection": {
"description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
"type": "boolean"
},
"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": [
Expand Down Expand Up @@ -94671,6 +94679,9 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"type": "boolean"
},
"setup_future_usage": {
"enum": [
"",
Expand Down Expand Up @@ -97285,6 +97296,9 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"type": "boolean"
},
"setup_future_usage": {
"enum": [
"",
Expand Down Expand Up @@ -100038,6 +100052,9 @@
"type": "string",
"x-stripeBypassValidation": true
},
"require_cvc_recollection": {
"type": "boolean"
},
"setup_future_usage": {
"enum": [
"",
Expand Down

0 comments on commit e784d66

Please sign in to comment.