stripe 16.6.0-beta.1 → 16.7.0-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,14 @@
1
1
  # Changelog
2
2
 
3
+ ## 16.7.0-beta.1 - 2024-08-01
4
+ * [#2145](https://github.com/stripe/stripe-node/pull/2145) Update generated code for beta
5
+ * Add support for `attach_payment` method on resource `Invoice`
6
+ * Add support for `app_install` and `app_viewport` on `AccountSessionCreateParams.components`
7
+ * Remove support for `partner_rejected_details` on `Dispute.evidence_details.enhanced_eligibility.visa_compelling_evidence_3`
8
+ * Add support for `lines_invalid` on `Quote.status_details.stale.last_reason`
9
+ * Add support for new value `lines_invalid` on enum `Quote.status_details.stale.last_reason.type`
10
+ * Add support for `last_price_migration_error` on `SubscriptionSchedule` and `Subscription`
11
+
3
12
  ## 16.6.0-beta.1 - 2024-07-25
4
13
  * [#2137](https://github.com/stripe/stripe-node/pull/2137) Update generated code for beta
5
14
  * Add support for new resources `Billing.AlertTriggered`, `Billing.Alert`, and `Tax.Association`
package/VERSION CHANGED
@@ -1 +1 @@
1
- 16.6.0-beta.1
1
+ 16.7.0-beta.1
@@ -18,6 +18,10 @@ exports.Invoices = StripeResource_js_1.StripeResource.extend({
18
18
  method: 'POST',
19
19
  fullPath: '/v1/invoices/{invoice}/add_lines',
20
20
  }),
21
+ attachPayment: stripeMethod({
22
+ method: 'POST',
23
+ fullPath: '/v1/invoices/{invoice}/attach_payment',
24
+ }),
21
25
  attachPaymentIntent: stripeMethod({
22
26
  method: 'POST',
23
27
  fullPath: '/v1/invoices/{invoice}/attach_payment_intent',
@@ -34,7 +34,7 @@ const ALLOWED_CONFIG_PROPERTIES = [
34
34
  ];
35
35
  const defaultRequestSenderFactory = (stripe) => new RequestSender_js_1.RequestSender(stripe, StripeResource_js_1.StripeResource.MAX_BUFFERED_REQUEST_METRICS);
36
36
  function createStripe(platformFunctions, requestSender = defaultRequestSenderFactory) {
37
- Stripe.PACKAGE_VERSION = '16.6.0-beta.1';
37
+ Stripe.PACKAGE_VERSION = '16.7.0-beta.1';
38
38
  Stripe.USER_AGENT = Object.assign({ bindings_version: Stripe.PACKAGE_VERSION, lang: 'node', publisher: 'stripe', uname: null, typescript: false }, (0, utils_js_1.determineProcessUserAgentProperties)());
39
39
  Stripe.StripeResource = StripeResource_js_1.StripeResource;
40
40
  Stripe.resources = resources;
@@ -15,6 +15,10 @@ export const Invoices = StripeResource.extend({
15
15
  method: 'POST',
16
16
  fullPath: '/v1/invoices/{invoice}/add_lines',
17
17
  }),
18
+ attachPayment: stripeMethod({
19
+ method: 'POST',
20
+ fullPath: '/v1/invoices/{invoice}/attach_payment',
21
+ }),
18
22
  attachPaymentIntent: stripeMethod({
19
23
  method: 'POST',
20
24
  fullPath: '/v1/invoices/{invoice}/attach_payment_intent',
@@ -31,7 +31,7 @@ const ALLOWED_CONFIG_PROPERTIES = [
31
31
  ];
32
32
  const defaultRequestSenderFactory = (stripe) => new RequestSender(stripe, StripeResource.MAX_BUFFERED_REQUEST_METRICS);
33
33
  export function createStripe(platformFunctions, requestSender = defaultRequestSenderFactory) {
34
- Stripe.PACKAGE_VERSION = '16.6.0-beta.1';
34
+ Stripe.PACKAGE_VERSION = '16.7.0-beta.1';
35
35
  Stripe.USER_AGENT = Object.assign({ bindings_version: Stripe.PACKAGE_VERSION, lang: 'node', publisher: 'stripe', uname: null, typescript: false }, determineProcessUserAgentProperties());
36
36
  Stripe.StripeResource = StripeResource;
37
37
  Stripe.resources = resources;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "stripe",
3
- "version": "16.6.0-beta.1",
3
+ "version": "16.7.0-beta.1",
4
4
  "description": "Stripe API wrapper",
5
5
  "keywords": [
6
6
  "stripe",
@@ -31,6 +31,16 @@ declare module 'stripe' {
31
31
  */
32
32
  account_onboarding?: Components.AccountOnboarding;
33
33
 
34
+ /**
35
+ * Configuration for the app install component.
36
+ */
37
+ app_install?: Components.AppInstall;
38
+
39
+ /**
40
+ * Configuration for the app viewport component.
41
+ */
42
+ app_viewport?: Components.AppViewport;
43
+
34
44
  /**
35
45
  * Configuration for the balances embedded component.
36
46
  */
@@ -152,6 +162,48 @@ declare module 'stripe' {
152
162
  }
153
163
  }
154
164
 
165
+ interface AppInstall {
166
+ /**
167
+ * Whether the embedded component is enabled.
168
+ */
169
+ enabled: boolean;
170
+
171
+ /**
172
+ * The list of features enabled in the embedded component.
173
+ */
174
+ features?: AppInstall.Features;
175
+ }
176
+
177
+ namespace AppInstall {
178
+ interface Features {
179
+ /**
180
+ * List of apps allowed to be enabled for this account session.
181
+ */
182
+ allowed_apps?: Stripe.Emptyable<Array<string>>;
183
+ }
184
+ }
185
+
186
+ interface AppViewport {
187
+ /**
188
+ * Whether the embedded component is enabled.
189
+ */
190
+ enabled: boolean;
191
+
192
+ /**
193
+ * The list of features enabled in the embedded component.
194
+ */
195
+ features?: AppViewport.Features;
196
+ }
197
+
198
+ namespace AppViewport {
199
+ interface Features {
200
+ /**
201
+ * List of apps allowed to be enabled for this account session.
202
+ */
203
+ allowed_apps?: Stripe.Emptyable<Array<string>>;
204
+ }
205
+ }
206
+
155
207
  interface Balances {
156
208
  /**
157
209
  * Whether the embedded component is enabled.
@@ -707,11 +707,6 @@ declare module 'stripe' {
707
707
  */
708
708
  amount_authorized: number | null;
709
709
 
710
- /**
711
- * Authorization code on the charge.
712
- */
713
- authorization_code?: string | null;
714
-
715
710
  /**
716
711
  * Card brand. Can be `amex`, `diners`, `discover`, `eftpos_au`, `jcb`, `mastercard`, `unionpay`, `visa`, or `unknown`.
717
712
  */
@@ -95,7 +95,7 @@ declare module 'stripe' {
95
95
  currency: string | null;
96
96
 
97
97
  /**
98
- * Currency conversion details for automatic currency conversion sessions
98
+ * Currency conversion details for [Adaptive Pricing](https://docs.stripe.com/payments/checkout/adaptive-pricing) sessions
99
99
  */
100
100
  currency_conversion: Session.CurrencyConversion | null;
101
101
 
@@ -973,6 +973,8 @@ declare module 'stripe' {
973
973
  *
974
974
  * Providing 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.
975
975
  *
976
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
977
+ *
976
978
  * When 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).
977
979
  */
978
980
  setup_future_usage?: AcssDebit.SetupFutureUsage;
@@ -1032,6 +1034,8 @@ declare module 'stripe' {
1032
1034
  *
1033
1035
  * Providing 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.
1034
1036
  *
1037
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1038
+ *
1035
1039
  * When 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).
1036
1040
  */
1037
1041
  setup_future_usage?: 'none';
@@ -1043,6 +1047,8 @@ declare module 'stripe' {
1043
1047
  *
1044
1048
  * Providing 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.
1045
1049
  *
1050
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1051
+ *
1046
1052
  * When 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).
1047
1053
  */
1048
1054
  setup_future_usage?: 'none';
@@ -1054,6 +1060,8 @@ declare module 'stripe' {
1054
1060
  *
1055
1061
  * Providing 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.
1056
1062
  *
1063
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1064
+ *
1057
1065
  * When 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).
1058
1066
  */
1059
1067
  setup_future_usage?: 'none';
@@ -1065,6 +1073,8 @@ declare module 'stripe' {
1065
1073
  *
1066
1074
  * Providing 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.
1067
1075
  *
1076
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1077
+ *
1068
1078
  * When 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).
1069
1079
  */
1070
1080
  setup_future_usage?: AmazonPay.SetupFutureUsage;
@@ -1080,6 +1090,8 @@ declare module 'stripe' {
1080
1090
  *
1081
1091
  * Providing 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.
1082
1092
  *
1093
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1094
+ *
1083
1095
  * When 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).
1084
1096
  */
1085
1097
  setup_future_usage?: 'none';
@@ -1091,6 +1103,8 @@ declare module 'stripe' {
1091
1103
  *
1092
1104
  * Providing 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.
1093
1105
  *
1106
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1107
+ *
1094
1108
  * When 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).
1095
1109
  */
1096
1110
  setup_future_usage?: BacsDebit.SetupFutureUsage;
@@ -1106,6 +1120,8 @@ declare module 'stripe' {
1106
1120
  *
1107
1121
  * Providing 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.
1108
1122
  *
1123
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1124
+ *
1109
1125
  * When 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).
1110
1126
  */
1111
1127
  setup_future_usage?: 'none';
@@ -1122,6 +1138,8 @@ declare module 'stripe' {
1122
1138
  *
1123
1139
  * Providing 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.
1124
1140
  *
1141
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1142
+ *
1125
1143
  * When 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).
1126
1144
  */
1127
1145
  setup_future_usage?: Boleto.SetupFutureUsage;
@@ -1144,6 +1162,8 @@ declare module 'stripe' {
1144
1162
  *
1145
1163
  * Providing 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.
1146
1164
  *
1165
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1166
+ *
1147
1167
  * When 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).
1148
1168
  */
1149
1169
  setup_future_usage?: Card.SetupFutureUsage;
@@ -1178,6 +1198,8 @@ declare module 'stripe' {
1178
1198
  *
1179
1199
  * Providing 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.
1180
1200
  *
1201
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1202
+ *
1181
1203
  * When 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).
1182
1204
  */
1183
1205
  setup_future_usage?: 'none';
@@ -1196,6 +1218,8 @@ declare module 'stripe' {
1196
1218
  *
1197
1219
  * Providing 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.
1198
1220
  *
1221
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1222
+ *
1199
1223
  * When 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).
1200
1224
  */
1201
1225
  setup_future_usage?: 'none';
@@ -1256,6 +1280,8 @@ declare module 'stripe' {
1256
1280
  *
1257
1281
  * Providing 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.
1258
1282
  *
1283
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1284
+ *
1259
1285
  * When 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).
1260
1286
  */
1261
1287
  setup_future_usage?: 'none';
@@ -1267,6 +1293,8 @@ declare module 'stripe' {
1267
1293
  *
1268
1294
  * Providing 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.
1269
1295
  *
1296
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1297
+ *
1270
1298
  * When 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).
1271
1299
  */
1272
1300
  setup_future_usage?: 'none';
@@ -1278,6 +1306,8 @@ declare module 'stripe' {
1278
1306
  *
1279
1307
  * Providing 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.
1280
1308
  *
1309
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1310
+ *
1281
1311
  * When 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).
1282
1312
  */
1283
1313
  setup_future_usage?: 'none';
@@ -1289,6 +1319,8 @@ declare module 'stripe' {
1289
1319
  *
1290
1320
  * Providing 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.
1291
1321
  *
1322
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1323
+ *
1292
1324
  * When 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).
1293
1325
  */
1294
1326
  setup_future_usage?: 'none';
@@ -1300,6 +1332,8 @@ declare module 'stripe' {
1300
1332
  *
1301
1333
  * Providing 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.
1302
1334
  *
1335
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1336
+ *
1303
1337
  * When 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).
1304
1338
  */
1305
1339
  setup_future_usage?: 'none';
@@ -1311,6 +1345,8 @@ declare module 'stripe' {
1311
1345
  *
1312
1346
  * Providing 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.
1313
1347
  *
1348
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1349
+ *
1314
1350
  * When 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).
1315
1351
  */
1316
1352
  setup_future_usage?: Klarna.SetupFutureUsage;
@@ -1331,6 +1367,8 @@ declare module 'stripe' {
1331
1367
  *
1332
1368
  * Providing 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.
1333
1369
  *
1370
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1371
+ *
1334
1372
  * When 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).
1335
1373
  */
1336
1374
  setup_future_usage?: 'none';
@@ -1342,6 +1380,8 @@ declare module 'stripe' {
1342
1380
  *
1343
1381
  * Providing 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.
1344
1382
  *
1383
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1384
+ *
1345
1385
  * When 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).
1346
1386
  */
1347
1387
  setup_future_usage?: Link.SetupFutureUsage;
@@ -1357,6 +1397,8 @@ declare module 'stripe' {
1357
1397
  *
1358
1398
  * Providing 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.
1359
1399
  *
1400
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1401
+ *
1360
1402
  * When 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).
1361
1403
  */
1362
1404
  setup_future_usage?: 'none';
@@ -1368,6 +1410,8 @@ declare module 'stripe' {
1368
1410
  *
1369
1411
  * Providing 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.
1370
1412
  *
1413
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1414
+ *
1371
1415
  * When 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).
1372
1416
  */
1373
1417
  setup_future_usage?: 'none';
@@ -1384,6 +1428,8 @@ declare module 'stripe' {
1384
1428
  *
1385
1429
  * Providing 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.
1386
1430
  *
1431
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1432
+ *
1387
1433
  * When 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).
1388
1434
  */
1389
1435
  setup_future_usage?: 'none';
@@ -1395,6 +1441,8 @@ declare module 'stripe' {
1395
1441
  *
1396
1442
  * Providing 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.
1397
1443
  *
1444
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1445
+ *
1398
1446
  * When 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).
1399
1447
  */
1400
1448
  setup_future_usage?: 'none';
@@ -1406,6 +1454,8 @@ declare module 'stripe' {
1406
1454
  *
1407
1455
  * Providing 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.
1408
1456
  *
1457
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1458
+ *
1409
1459
  * When 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).
1410
1460
  */
1411
1461
  setup_future_usage?: 'none';
@@ -1432,6 +1482,8 @@ declare module 'stripe' {
1432
1482
  *
1433
1483
  * Providing 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.
1434
1484
  *
1485
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1486
+ *
1435
1487
  * When 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).
1436
1488
  */
1437
1489
  setup_future_usage?: Paypal.SetupFutureUsage;
@@ -1459,6 +1511,8 @@ declare module 'stripe' {
1459
1511
  *
1460
1512
  * Providing 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.
1461
1513
  *
1514
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1515
+ *
1462
1516
  * When 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).
1463
1517
  */
1464
1518
  setup_future_usage?: RevolutPay.SetupFutureUsage;
@@ -1474,6 +1528,8 @@ declare module 'stripe' {
1474
1528
  *
1475
1529
  * Providing 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.
1476
1530
  *
1531
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1532
+ *
1477
1533
  * When 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).
1478
1534
  */
1479
1535
  setup_future_usage?: SepaDebit.SetupFutureUsage;
@@ -1489,6 +1545,8 @@ declare module 'stripe' {
1489
1545
  *
1490
1546
  * Providing 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.
1491
1547
  *
1548
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1549
+ *
1492
1550
  * When 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).
1493
1551
  */
1494
1552
  setup_future_usage?: 'none';
@@ -1509,6 +1567,8 @@ declare module 'stripe' {
1509
1567
  *
1510
1568
  * Providing 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.
1511
1569
  *
1570
+ * If the payment method is `card_present` and isn't a digital wallet, then a [generated_card](https://docs.corp.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card is created and attached to the Customer instead.
1571
+ *
1512
1572
  * When 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).
1513
1573
  */
1514
1574
  setup_future_usage?: UsBankAccount.SetupFutureUsage;