stripe 16.7.0-beta.1 → 16.7.0

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.
Files changed (168) hide show
  1. package/CHANGELOG.md +128 -787
  2. package/README.md +0 -33
  3. package/VERSION +1 -1
  4. package/cjs/RequestSender.js +5 -66
  5. package/cjs/StripeResource.js +1 -1
  6. package/cjs/apiVersion.js +1 -2
  7. package/cjs/multipart.js +1 -1
  8. package/cjs/resources/FinancialConnections/Accounts.js +0 -5
  9. package/cjs/resources/Invoices.js +0 -17
  10. package/cjs/resources/OAuth.js +1 -1
  11. package/cjs/resources/PaymentIntents.js +0 -4
  12. package/cjs/resources/Quotes.js +0 -32
  13. package/cjs/resources/SubscriptionSchedules.js +0 -4
  14. package/cjs/resources/Tax/Calculations.js +4 -0
  15. package/cjs/resources/Terminal/Readers.js +0 -12
  16. package/cjs/resources.js +10 -40
  17. package/cjs/stripe.core.js +3 -6
  18. package/cjs/utils.js +3 -30
  19. package/esm/RequestSender.js +6 -67
  20. package/esm/StripeResource.js +2 -2
  21. package/esm/apiVersion.js +0 -1
  22. package/esm/multipart.js +2 -2
  23. package/esm/resources/FinancialConnections/Accounts.js +0 -5
  24. package/esm/resources/Invoices.js +0 -17
  25. package/esm/resources/OAuth.js +2 -2
  26. package/esm/resources/PaymentIntents.js +0 -4
  27. package/esm/resources/Quotes.js +0 -32
  28. package/esm/resources/SubscriptionSchedules.js +0 -4
  29. package/esm/resources/Tax/Calculations.js +4 -0
  30. package/esm/resources/Terminal/Readers.js +0 -12
  31. package/esm/resources.js +0 -26
  32. package/esm/stripe.core.js +3 -6
  33. package/esm/utils.js +1 -27
  34. package/package.json +1 -1
  35. package/types/AccountLinksResource.d.ts +1 -5
  36. package/types/AccountSessions.d.ts +0 -15
  37. package/types/AccountSessionsResource.d.ts +0 -215
  38. package/types/Accounts.d.ts +5 -110
  39. package/types/AccountsResource.d.ts +6 -252
  40. package/types/Cards.d.ts +2 -2
  41. package/types/Charges.d.ts +8 -70
  42. package/types/ChargesResource.d.ts +5 -1299
  43. package/types/Checkout/Sessions.d.ts +91 -118
  44. package/types/Checkout/SessionsResource.d.ts +97 -114
  45. package/types/ConfirmationTokens.d.ts +22 -62
  46. package/types/Coupons.d.ts +1 -1
  47. package/types/CouponsResource.d.ts +1 -1
  48. package/types/CreditNotes.d.ts +0 -21
  49. package/types/CreditNotesResource.d.ts +0 -51
  50. package/types/CustomerSessions.d.ts +1 -1
  51. package/types/CustomerSessionsResource.d.ts +1 -1
  52. package/types/CustomersResource.d.ts +0 -2
  53. package/types/Disputes.d.ts +0 -158
  54. package/types/DisputesResource.d.ts +0 -120
  55. package/types/EventTypes.d.ts +0 -460
  56. package/types/Events.d.ts +0 -85
  57. package/types/FinancialConnections/Accounts.d.ts +1 -29
  58. package/types/FinancialConnections/AccountsResource.d.ts +3 -35
  59. package/types/FinancialConnections/Sessions.d.ts +1 -49
  60. package/types/FinancialConnections/SessionsResource.d.ts +1 -38
  61. package/types/Identity/VerificationSessions.d.ts +5 -0
  62. package/types/Identity/VerificationSessionsResource.d.ts +7 -0
  63. package/types/InvoiceItems.d.ts +0 -5
  64. package/types/InvoiceItemsResource.d.ts +0 -98
  65. package/types/InvoiceLineItems.d.ts +0 -22
  66. package/types/Invoices.d.ts +2 -116
  67. package/types/InvoicesResource.d.ts +1763 -5421
  68. package/types/Issuing/CardholdersResource.d.ts +1 -2
  69. package/types/LineItems.d.ts +0 -7
  70. package/types/Mandates.d.ts +0 -77
  71. package/types/PaymentIntents.d.ts +119 -608
  72. package/types/PaymentIntentsResource.d.ts +3680 -7208
  73. package/types/PaymentLinks.d.ts +2 -2
  74. package/types/PaymentLinksResource.d.ts +4 -4
  75. package/types/PaymentMethodConfigurations.d.ts +0 -36
  76. package/types/PaymentMethodConfigurationsResource.d.ts +0 -50
  77. package/types/PaymentMethods.d.ts +22 -62
  78. package/types/PaymentMethodsResource.d.ts +0 -110
  79. package/types/Persons.d.ts +4 -1
  80. package/types/Prices.d.ts +0 -22
  81. package/types/PricesResource.d.ts +0 -22
  82. package/types/Products.d.ts +0 -39
  83. package/types/ProductsResource.d.ts +0 -36
  84. package/types/Quotes.d.ts +1 -596
  85. package/types/QuotesResource.d.ts +266 -3175
  86. package/types/SetupAttempts.d.ts +6 -9
  87. package/types/SetupIntents.d.ts +3 -110
  88. package/types/SetupIntentsResource.d.ts +6 -498
  89. package/types/Sources.d.ts +0 -23
  90. package/types/SubscriptionItems.d.ts +0 -21
  91. package/types/SubscriptionItemsResource.d.ts +0 -109
  92. package/types/SubscriptionSchedules.d.ts +0 -200
  93. package/types/SubscriptionSchedulesResource.d.ts +13 -1231
  94. package/types/Subscriptions.d.ts +3 -83
  95. package/types/SubscriptionsResource.d.ts +8 -351
  96. package/types/Tax/CalculationsResource.d.ts +20 -0
  97. package/types/Terminal/Readers.d.ts +1 -279
  98. package/types/Terminal/ReadersResource.d.ts +0 -208
  99. package/types/TestHelpers/ConfirmationTokensResource.d.ts +0 -55
  100. package/types/TestHelpers/Treasury/ReceivedCreditsResource.d.ts +0 -26
  101. package/types/TestHelpers/Treasury/ReceivedDebitsResource.d.ts +0 -26
  102. package/types/TransfersResource.d.ts +1 -1
  103. package/types/Treasury/FinancialAccounts.d.ts +3 -5
  104. package/types/Treasury/FinancialAccountsResource.d.ts +0 -10
  105. package/types/Treasury/OutboundTransfers.d.ts +0 -26
  106. package/types/Treasury/OutboundTransfersResource.d.ts +0 -26
  107. package/types/Treasury/ReceivedCredits.d.ts +0 -26
  108. package/types/Treasury/ReceivedDebits.d.ts +0 -31
  109. package/types/WebhookEndpointsResource.d.ts +0 -54
  110. package/types/index.d.ts +0 -67
  111. package/types/lib.d.ts +0 -12
  112. package/cjs/resources/AccountNotices.js +0 -21
  113. package/cjs/resources/Capital/FinancingOffers.js +0 -21
  114. package/cjs/resources/Capital/FinancingSummary.js +0 -12
  115. package/cjs/resources/Capital/FinancingTransactions.js +0 -17
  116. package/cjs/resources/FinancialConnections/Institutions.js +0 -17
  117. package/cjs/resources/GiftCards/Cards.js +0 -23
  118. package/cjs/resources/GiftCards/Transactions.js +0 -33
  119. package/cjs/resources/Issuing/CreditUnderwritingRecords.js +0 -33
  120. package/cjs/resources/Margins.js +0 -22
  121. package/cjs/resources/Orders.js +0 -24
  122. package/cjs/resources/QuotePhases.js +0 -22
  123. package/cjs/resources/Tax/Associations.js +0 -9
  124. package/cjs/resources/Tax/Forms.js +0 -20
  125. package/esm/resources/AccountNotices.js +0 -18
  126. package/esm/resources/Capital/FinancingOffers.js +0 -18
  127. package/esm/resources/Capital/FinancingSummary.js +0 -9
  128. package/esm/resources/Capital/FinancingTransactions.js +0 -14
  129. package/esm/resources/FinancialConnections/Institutions.js +0 -14
  130. package/esm/resources/GiftCards/Cards.js +0 -20
  131. package/esm/resources/GiftCards/Transactions.js +0 -30
  132. package/esm/resources/Issuing/CreditUnderwritingRecords.js +0 -30
  133. package/esm/resources/Margins.js +0 -19
  134. package/esm/resources/Orders.js +0 -21
  135. package/esm/resources/QuotePhases.js +0 -19
  136. package/esm/resources/Tax/Associations.js +0 -6
  137. package/esm/resources/Tax/Forms.js +0 -17
  138. package/types/AccountNotices.d.ts +0 -113
  139. package/types/AccountNoticesResource.d.ts +0 -98
  140. package/types/Capital/FinancingOffers.d.ts +0 -188
  141. package/types/Capital/FinancingOffersResource.d.ts +0 -97
  142. package/types/Capital/FinancingSummary.d.ts +0 -106
  143. package/types/Capital/FinancingSummaryResource.d.ts +0 -27
  144. package/types/Capital/FinancingTransactions.d.ts +0 -135
  145. package/types/Capital/FinancingTransactionsResource.d.ts +0 -68
  146. package/types/FinancialConnections/AccountInferredBalances.d.ts +0 -38
  147. package/types/FinancialConnections/Institutions.d.ts +0 -93
  148. package/types/FinancialConnections/InstitutionsResource.d.ts +0 -47
  149. package/types/GiftCards/Cards.d.ts +0 -118
  150. package/types/GiftCards/CardsResource.d.ts +0 -159
  151. package/types/GiftCards/Transactions.d.ts +0 -129
  152. package/types/GiftCards/TransactionsResource.d.ts +0 -201
  153. package/types/InvoicePayments.d.ts +0 -138
  154. package/types/Issuing/CreditUnderwritingRecords.d.ts +0 -446
  155. package/types/Issuing/CreditUnderwritingRecordsResource.d.ts +0 -1017
  156. package/types/Margins.d.ts +0 -56
  157. package/types/MarginsResource.d.ts +0 -114
  158. package/types/Orders.d.ts +0 -1083
  159. package/types/OrdersResource.d.ts +0 -2763
  160. package/types/QuoteLines.d.ts +0 -634
  161. package/types/QuotePhases.d.ts +0 -198
  162. package/types/QuotePhasesResource.d.ts +0 -67
  163. package/types/QuotePreviewInvoices.d.ts +0 -1529
  164. package/types/QuotePreviewSubscriptionSchedules.d.ts +0 -814
  165. package/types/Tax/Associations.d.ts +0 -126
  166. package/types/Tax/AssociationsResource.d.ts +0 -29
  167. package/types/Tax/Forms.d.ts +0 -133
  168. package/types/Tax/FormsResource.d.ts +0 -90
@@ -53,8 +53,6 @@ declare module 'stripe' {
53
53
  */
54
54
  application_fee_amount: number | null;
55
55
 
56
- async_workflows?: PaymentIntent.AsyncWorkflows;
57
-
58
56
  /**
59
57
  * Settings to configure compatible payment methods from the [Stripe Dashboard](https://dashboard.stripe.com/settings/payment_methods)
60
58
  */
@@ -148,8 +146,6 @@ declare module 'stripe' {
148
146
  */
149
147
  on_behalf_of: string | Stripe.Account | null;
150
148
 
151
- payment_details?: PaymentIntent.PaymentDetails;
152
-
153
149
  /**
154
150
  * ID of the payment method used in this PaymentIntent.
155
151
  */
@@ -185,19 +181,14 @@ declare module 'stripe' {
185
181
  */
186
182
  review: string | Stripe.Review | null;
187
183
 
188
- /**
189
- * Indicates whether confirmation for this PaymentIntent using a secret key is `required` or `optional`.
190
- */
191
- secret_key_confirmation?: PaymentIntent.SecretKeyConfirmation;
192
-
193
184
  /**
194
185
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
195
186
  *
196
- * 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.
187
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
197
188
  *
198
- * 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.
189
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
199
190
  *
200
- * 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).
191
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
201
192
  */
202
193
  setup_future_usage: PaymentIntent.SetupFutureUsage | null;
203
194
 
@@ -216,12 +207,12 @@ declare module 'stripe' {
216
207
  | null;
217
208
 
218
209
  /**
219
- * For card charges, use [statement_descriptor_suffix](https://stripe.com/docs/payments/account/statement-descriptors#dynamic). Otherwise, you can use this value as the complete description of a charge on your customers' statements. It must contain at least one letter and be 1–22 characters long.
210
+ * Text that appears on the customer's statement as the [statement descriptor](https://docs.stripe.com/get-started/account/statement-descriptors) for a non-card charge. This value overrides the account's default statement descriptor. Setting this value for a card charge returns an error. For card charges, set the [statement_descriptor_suffix](https://docs.stripe.com/get-started/account/statement-descriptors#dynamic) instead.
220
211
  */
221
212
  statement_descriptor: string | null;
222
213
 
223
214
  /**
224
- * Provides information about a card payment that customers see on their statements. Concatenated with the prefix (shortened descriptor) or statement descriptor that's set on the account to form the complete statement descriptor. Maximum 22 characters for the concatenated descriptor.
215
+ * Provides information about a card charge. Concatenated to the account's [statement descriptor prefix](https://docs.corp.stripe.com/get-started/account/statement-descriptors#static) to form the complete statement descriptor that appears on the customer's statement.
225
216
  */
226
217
  statement_descriptor_suffix: string | null;
227
218
 
@@ -255,25 +246,6 @@ declare module 'stripe' {
255
246
  }
256
247
  }
257
248
 
258
- interface AsyncWorkflows {
259
- inputs?: AsyncWorkflows.Inputs;
260
- }
261
-
262
- namespace AsyncWorkflows {
263
- interface Inputs {
264
- tax?: Inputs.Tax;
265
- }
266
-
267
- namespace Inputs {
268
- interface Tax {
269
- /**
270
- * The [TaxCalculation](https://stripe.com/docs/api/tax/calculations) id
271
- */
272
- calculation: string;
273
- }
274
- }
275
- }
276
-
277
249
  interface AutomaticPaymentMethods {
278
250
  /**
279
251
  * Controls whether this PaymentIntent will accept redirect-based payment methods.
@@ -453,15 +425,11 @@ declare module 'stripe' {
453
425
  | 'email_invalid'
454
426
  | 'expired_card'
455
427
  | 'financial_connections_account_inactive'
456
- | 'financial_connections_institution_unavailable'
457
428
  | 'financial_connections_no_successful_transaction_refresh'
458
429
  | 'forwarding_api_inactive'
459
430
  | 'forwarding_api_invalid_parameter'
460
431
  | 'forwarding_api_upstream_connection_error'
461
432
  | 'forwarding_api_upstream_connection_timeout'
462
- | 'gift_card_balance_insufficient'
463
- | 'gift_card_code_exists'
464
- | 'gift_card_inactive'
465
433
  | 'idempotency_key_in_use'
466
434
  | 'incorrect_address'
467
435
  | 'incorrect_cvc'
@@ -480,6 +448,7 @@ declare module 'stripe' {
480
448
  | 'invalid_cvc'
481
449
  | 'invalid_expiry_month'
482
450
  | 'invalid_expiry_year'
451
+ | 'invalid_mandate_reference_prefix_format'
483
452
  | 'invalid_number'
484
453
  | 'invalid_source_usage'
485
454
  | 'invalid_tax_location'
@@ -550,7 +519,6 @@ declare module 'stripe' {
550
519
  | 'return_intent_already_processed'
551
520
  | 'routing_number_invalid'
552
521
  | 'secret_key_required'
553
- | 'sensitive_data_access_expired'
554
522
  | 'sepa_unsupported_account'
555
523
  | 'setup_attempt_failed'
556
524
  | 'setup_intent_authentication_failure'
@@ -1294,289 +1262,6 @@ declare module 'stripe' {
1294
1262
  }
1295
1263
  }
1296
1264
 
1297
- interface PaymentDetails {
1298
- car_rental?: PaymentDetails.CarRental;
1299
-
1300
- event_details?: PaymentDetails.EventDetails;
1301
-
1302
- subscription?: PaymentDetails.Subscription;
1303
- }
1304
-
1305
- namespace PaymentDetails {
1306
- interface CarRental {
1307
- affiliate?: CarRental.Affiliate;
1308
-
1309
- /**
1310
- * The booking number associated with the car rental.
1311
- */
1312
- booking_number: string;
1313
-
1314
- /**
1315
- * Class code of the car.
1316
- */
1317
- car_class_code?: string;
1318
-
1319
- /**
1320
- * Make of the car.
1321
- */
1322
- car_make?: string;
1323
-
1324
- /**
1325
- * Model of the car.
1326
- */
1327
- car_model?: string;
1328
-
1329
- /**
1330
- * The name of the rental car company.
1331
- */
1332
- company?: string;
1333
-
1334
- /**
1335
- * The customer service phone number of the car rental company.
1336
- */
1337
- customer_service_phone_number?: string;
1338
-
1339
- /**
1340
- * Number of days the car is being rented.
1341
- */
1342
- days_rented: number;
1343
-
1344
- delivery?: CarRental.Delivery;
1345
-
1346
- /**
1347
- * The details of the drivers associated with the trip.
1348
- */
1349
- drivers?: Array<CarRental.Driver>;
1350
-
1351
- /**
1352
- * List of additional charges being billed.
1353
- */
1354
- extra_charges?: Array<CarRental.ExtraCharge>;
1355
-
1356
- /**
1357
- * Indicates if the customer did not keep nor cancel their booking.
1358
- */
1359
- no_show?: boolean;
1360
-
1361
- pickup_address?: Stripe.Address;
1362
-
1363
- /**
1364
- * Car pick-up time. Measured in seconds since the Unix epoch.
1365
- */
1366
- pickup_at: number;
1367
-
1368
- /**
1369
- * Rental rate.
1370
- */
1371
- rate_amount?: number;
1372
-
1373
- /**
1374
- * The frequency at which the rate amount is applied. One of `day`, `week` or `month`
1375
- */
1376
- rate_interval?: CarRental.RateInterval;
1377
-
1378
- /**
1379
- * The full name of the person or entity renting the car.
1380
- */
1381
- renter_name?: string;
1382
-
1383
- return_address?: Stripe.Address;
1384
-
1385
- /**
1386
- * Car return time. Measured in seconds since the Unix epoch.
1387
- */
1388
- return_at: number;
1389
-
1390
- /**
1391
- * Indicates whether the goods or services are tax-exempt or tax is not collected.
1392
- */
1393
- tax_exempt?: boolean;
1394
- }
1395
-
1396
- namespace CarRental {
1397
- interface Affiliate {
1398
- /**
1399
- * The name of the affiliate that originated the purchase.
1400
- */
1401
- name?: string;
1402
- }
1403
-
1404
- interface Delivery {
1405
- /**
1406
- * The delivery method for the payment
1407
- */
1408
- mode?: Delivery.Mode;
1409
-
1410
- recipient?: Delivery.Recipient;
1411
- }
1412
-
1413
- namespace Delivery {
1414
- type Mode = 'email' | 'phone' | 'pickup' | 'post';
1415
-
1416
- interface Recipient {
1417
- /**
1418
- * The email of the recipient the ticket is delivered to.
1419
- */
1420
- email?: string;
1421
-
1422
- /**
1423
- * The name of the recipient the ticket is delivered to.
1424
- */
1425
- name?: string;
1426
-
1427
- /**
1428
- * The phone number of the recipient the ticket is delivered to.
1429
- */
1430
- phone?: string;
1431
- }
1432
- }
1433
-
1434
- interface Driver {
1435
- /**
1436
- * Full name of the driver on the reservation.
1437
- */
1438
- name?: string;
1439
- }
1440
-
1441
- type ExtraCharge =
1442
- | 'extra_mileage'
1443
- | 'gas'
1444
- | 'late_return'
1445
- | 'one_way_service'
1446
- | 'parking_violation';
1447
-
1448
- type RateInterval = 'day' | 'month' | 'week';
1449
- }
1450
-
1451
- interface EventDetails {
1452
- /**
1453
- * Indicates if the tickets are digitally checked when entering the venue.
1454
- */
1455
- access_controlled_venue?: boolean;
1456
-
1457
- address?: Stripe.Address;
1458
-
1459
- affiliate?: EventDetails.Affiliate;
1460
-
1461
- /**
1462
- * The name of the company
1463
- */
1464
- company?: string;
1465
-
1466
- delivery?: EventDetails.Delivery;
1467
-
1468
- /**
1469
- * Event end time. Measured in seconds since the Unix epoch.
1470
- */
1471
- ends_at?: number;
1472
-
1473
- /**
1474
- * Type of the event entertainment (concert, sports event etc)
1475
- */
1476
- genre?: string;
1477
-
1478
- /**
1479
- * The name of the event.
1480
- */
1481
- name?: string;
1482
-
1483
- /**
1484
- * Event start time. Measured in seconds since the Unix epoch.
1485
- */
1486
- starts_at?: number;
1487
- }
1488
-
1489
- namespace EventDetails {
1490
- interface Affiliate {
1491
- /**
1492
- * The name of the affiliate that originated the purchase.
1493
- */
1494
- name?: string;
1495
- }
1496
-
1497
- interface Delivery {
1498
- /**
1499
- * The delivery method for the payment
1500
- */
1501
- mode?: Delivery.Mode;
1502
-
1503
- recipient?: Delivery.Recipient;
1504
- }
1505
-
1506
- namespace Delivery {
1507
- type Mode = 'email' | 'phone' | 'pickup' | 'post';
1508
-
1509
- interface Recipient {
1510
- /**
1511
- * The email of the recipient the ticket is delivered to.
1512
- */
1513
- email?: string;
1514
-
1515
- /**
1516
- * The name of the recipient the ticket is delivered to.
1517
- */
1518
- name?: string;
1519
-
1520
- /**
1521
- * The phone number of the recipient the ticket is delivered to.
1522
- */
1523
- phone?: string;
1524
- }
1525
- }
1526
- }
1527
-
1528
- interface Subscription {
1529
- affiliate?: Subscription.Affiliate;
1530
-
1531
- /**
1532
- * Info whether the subscription will be auto renewed upon expiry.
1533
- */
1534
- auto_renewal?: boolean;
1535
-
1536
- billing_interval?: Subscription.BillingInterval;
1537
-
1538
- /**
1539
- * Subscription end time. Measured in seconds since the Unix epoch.
1540
- */
1541
- ends_at?: number;
1542
-
1543
- /**
1544
- * Name of the product on subscription. e.g. Apple Music Subscription.
1545
- */
1546
- name?: string;
1547
-
1548
- /**
1549
- * Subscription start time. Measured in seconds since the Unix epoch.
1550
- */
1551
- starts_at?: number;
1552
- }
1553
-
1554
- namespace Subscription {
1555
- interface Affiliate {
1556
- /**
1557
- * The name of the affiliate that originated the purchase.
1558
- */
1559
- name?: string;
1560
- }
1561
-
1562
- interface BillingInterval {
1563
- /**
1564
- * The number of intervals, as an whole number greater than 0. Stripe multiplies this by the interval type to get the overall duration.
1565
- */
1566
- count?: number;
1567
-
1568
- /**
1569
- * Specifies a type of interval unit. Either `day`, `week`, `month` or `year`.
1570
- */
1571
- interval?: BillingInterval.Interval;
1572
- }
1573
-
1574
- namespace BillingInterval {
1575
- type Interval = 'day' | 'month' | 'week' | 'year';
1576
- }
1577
- }
1578
- }
1579
-
1580
1265
  interface PaymentMethodConfigurationDetails {
1581
1266
  /**
1582
1267
  * ID of the payment method configuration used.
@@ -1648,14 +1333,10 @@ declare module 'stripe' {
1648
1333
 
1649
1334
  paypal?: PaymentMethodOptions.Paypal;
1650
1335
 
1651
- payto?: PaymentMethodOptions.Payto;
1652
-
1653
1336
  pix?: PaymentMethodOptions.Pix;
1654
1337
 
1655
1338
  promptpay?: PaymentMethodOptions.Promptpay;
1656
1339
 
1657
- rechnung?: PaymentMethodOptions.Rechnung;
1658
-
1659
1340
  revolut_pay?: PaymentMethodOptions.RevolutPay;
1660
1341
 
1661
1342
  sepa_debit?: PaymentMethodOptions.SepaDebit;
@@ -1680,11 +1361,11 @@ declare module 'stripe' {
1680
1361
  /**
1681
1362
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1682
1363
  *
1683
- * 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.
1364
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1684
1365
  *
1685
- * 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.
1366
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1686
1367
  *
1687
- * 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).
1368
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1688
1369
  */
1689
1370
  setup_future_usage?: AcssDebit.SetupFutureUsage;
1690
1371
 
@@ -1742,11 +1423,11 @@ declare module 'stripe' {
1742
1423
  /**
1743
1424
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1744
1425
  *
1745
- * 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.
1426
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1746
1427
  *
1747
- * 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.
1428
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1748
1429
  *
1749
- * 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).
1430
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1750
1431
  */
1751
1432
  setup_future_usage?: 'none';
1752
1433
  }
@@ -1766,11 +1447,11 @@ declare module 'stripe' {
1766
1447
  /**
1767
1448
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1768
1449
  *
1769
- * 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.
1450
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1770
1451
  *
1771
- * 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.
1452
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1772
1453
  *
1773
- * 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).
1454
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1774
1455
  */
1775
1456
  setup_future_usage?: 'none';
1776
1457
  }
@@ -1779,11 +1460,11 @@ declare module 'stripe' {
1779
1460
  /**
1780
1461
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1781
1462
  *
1782
- * 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.
1463
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1783
1464
  *
1784
- * 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.
1465
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1785
1466
  *
1786
- * 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).
1467
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1787
1468
  */
1788
1469
  setup_future_usage?: Alipay.SetupFutureUsage;
1789
1470
  }
@@ -1801,11 +1482,11 @@ declare module 'stripe' {
1801
1482
  /**
1802
1483
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1803
1484
  *
1804
- * 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.
1485
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1805
1486
  *
1806
- * 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.
1487
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1807
1488
  *
1808
- * 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).
1489
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1809
1490
  */
1810
1491
  setup_future_usage?: AmazonPay.SetupFutureUsage;
1811
1492
  }
@@ -1818,11 +1499,11 @@ declare module 'stripe' {
1818
1499
  /**
1819
1500
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1820
1501
  *
1821
- * 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.
1502
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1822
1503
  *
1823
- * 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.
1504
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1824
1505
  *
1825
- * 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).
1506
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1826
1507
  */
1827
1508
  setup_future_usage?: AuBecsDebit.SetupFutureUsage;
1828
1509
  }
@@ -1835,11 +1516,11 @@ declare module 'stripe' {
1835
1516
  /**
1836
1517
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1837
1518
  *
1838
- * 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.
1519
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1839
1520
  *
1840
- * 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.
1521
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1841
1522
  *
1842
- * 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).
1523
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1843
1524
  */
1844
1525
  setup_future_usage?: BacsDebit.SetupFutureUsage;
1845
1526
  }
@@ -1857,11 +1538,11 @@ declare module 'stripe' {
1857
1538
  /**
1858
1539
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1859
1540
  *
1860
- * 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.
1541
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1861
1542
  *
1862
- * 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.
1543
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1863
1544
  *
1864
- * 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).
1545
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1865
1546
  */
1866
1547
  setup_future_usage?: Bancontact.SetupFutureUsage;
1867
1548
  }
@@ -1876,11 +1557,11 @@ declare module 'stripe' {
1876
1557
  /**
1877
1558
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1878
1559
  *
1879
- * 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.
1560
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1880
1561
  *
1881
- * 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.
1562
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1882
1563
  *
1883
- * 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).
1564
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1884
1565
  */
1885
1566
  setup_future_usage?: 'none';
1886
1567
  }
@@ -1894,11 +1575,11 @@ declare module 'stripe' {
1894
1575
  /**
1895
1576
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1896
1577
  *
1897
- * 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.
1578
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1898
1579
  *
1899
- * 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.
1580
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1900
1581
  *
1901
- * 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).
1582
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1902
1583
  */
1903
1584
  setup_future_usage?: Boleto.SetupFutureUsage;
1904
1585
  }
@@ -1930,11 +1611,6 @@ declare module 'stripe' {
1930
1611
  */
1931
1612
  network: Card.Network | null;
1932
1613
 
1933
- /**
1934
- * Request ability to [decrement the authorization](https://stripe.com/docs/payments/decremental-authorization) for this PaymentIntent.
1935
- */
1936
- request_decremental_authorization?: Card.RequestDecrementalAuthorization;
1937
-
1938
1614
  /**
1939
1615
  * Request ability to [capture beyond the standard authorization validity window](https://stripe.com/docs/payments/extended-authorization) for this PaymentIntent.
1940
1616
  */
@@ -1968,11 +1644,11 @@ declare module 'stripe' {
1968
1644
  /**
1969
1645
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
1970
1646
  *
1971
- * 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.
1647
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
1972
1648
  *
1973
- * 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.
1649
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
1974
1650
  *
1975
- * 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).
1651
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
1976
1652
  */
1977
1653
  setup_future_usage?: Card.SetupFutureUsage;
1978
1654
 
@@ -1985,8 +1661,6 @@ declare module 'stripe' {
1985
1661
  * Provides information about a card payment that customers see on their statements. Concatenated with the Kanji prefix (shortened Kanji descriptor) or Kanji statement descriptor that's set on the account to form the complete statement descriptor. Maximum 17 characters. On card statements, the *concatenation* of both prefix and suffix (including separators) will appear truncated to 17 characters.
1986
1662
  */
1987
1663
  statement_descriptor_suffix_kanji?: string;
1988
-
1989
- statement_details?: Card.StatementDetails;
1990
1664
  }
1991
1665
 
1992
1666
  namespace Card {
@@ -2104,6 +1778,7 @@ declare module 'stripe' {
2104
1778
  | 'diners'
2105
1779
  | 'discover'
2106
1780
  | 'eftpos_au'
1781
+ | 'girocard'
2107
1782
  | 'interac'
2108
1783
  | 'jcb'
2109
1784
  | 'mastercard'
@@ -2111,8 +1786,6 @@ declare module 'stripe' {
2111
1786
  | 'unknown'
2112
1787
  | 'visa';
2113
1788
 
2114
- type RequestDecrementalAuthorization = 'if_available' | 'never';
2115
-
2116
1789
  type RequestExtendedAuthorization = 'if_available' | 'never';
2117
1790
 
2118
1791
  type RequestIncrementalAuthorization = 'if_available' | 'never';
@@ -2124,49 +1797,6 @@ declare module 'stripe' {
2124
1797
  type RequestThreeDSecure = 'any' | 'automatic' | 'challenge';
2125
1798
 
2126
1799
  type SetupFutureUsage = 'none' | 'off_session' | 'on_session';
2127
-
2128
- interface StatementDetails {
2129
- address?: StatementDetails.Address;
2130
-
2131
- /**
2132
- * Phone number
2133
- */
2134
- phone?: string;
2135
- }
2136
-
2137
- namespace StatementDetails {
2138
- interface Address {
2139
- /**
2140
- * City, district, suburb, town, or village.
2141
- */
2142
- city?: string;
2143
-
2144
- /**
2145
- * Two-letter country code ([ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)).
2146
- */
2147
- country?: string;
2148
-
2149
- /**
2150
- * Address line 1 (e.g., street, PO Box, or company name).
2151
- */
2152
- line1?: string;
2153
-
2154
- /**
2155
- * Address line 2 (e.g., apartment, suite, unit, or building).
2156
- */
2157
- line2?: string;
2158
-
2159
- /**
2160
- * ZIP or postal code.
2161
- */
2162
- postal_code?: string;
2163
-
2164
- /**
2165
- * State, county, province, or region.
2166
- */
2167
- state?: string;
2168
- }
2169
- }
2170
1800
  }
2171
1801
 
2172
1802
  interface CardPresent {
@@ -2205,11 +1835,11 @@ declare module 'stripe' {
2205
1835
  /**
2206
1836
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2207
1837
  *
2208
- * 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.
1838
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2209
1839
  *
2210
- * 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.
1840
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2211
1841
  *
2212
- * 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).
1842
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2213
1843
  */
2214
1844
  setup_future_usage?: Cashapp.SetupFutureUsage;
2215
1845
  }
@@ -2229,11 +1859,11 @@ declare module 'stripe' {
2229
1859
  /**
2230
1860
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2231
1861
  *
2232
- * 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.
1862
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2233
1863
  *
2234
- * 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.
1864
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2235
1865
  *
2236
- * 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).
1866
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2237
1867
  */
2238
1868
  setup_future_usage?: 'none';
2239
1869
  }
@@ -2289,11 +1919,11 @@ declare module 'stripe' {
2289
1919
  /**
2290
1920
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2291
1921
  *
2292
- * 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.
1922
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2293
1923
  *
2294
- * 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.
1924
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2295
1925
  *
2296
- * 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).
1926
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2297
1927
  */
2298
1928
  setup_future_usage?: 'none';
2299
1929
  }
@@ -2302,11 +1932,11 @@ declare module 'stripe' {
2302
1932
  /**
2303
1933
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2304
1934
  *
2305
- * 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.
1935
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2306
1936
  *
2307
- * 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.
1937
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2308
1938
  *
2309
- * 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).
1939
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2310
1940
  */
2311
1941
  setup_future_usage?: 'none';
2312
1942
  }
@@ -2315,11 +1945,11 @@ declare module 'stripe' {
2315
1945
  /**
2316
1946
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2317
1947
  *
2318
- * 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.
1948
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2319
1949
  *
2320
- * 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.
1950
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2321
1951
  *
2322
- * 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).
1952
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2323
1953
  */
2324
1954
  setup_future_usage?: 'none';
2325
1955
  }
@@ -2328,11 +1958,11 @@ declare module 'stripe' {
2328
1958
  /**
2329
1959
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2330
1960
  *
2331
- * 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.
1961
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2332
1962
  *
2333
- * 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.
1963
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2334
1964
  *
2335
- * 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).
1965
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2336
1966
  */
2337
1967
  setup_future_usage?: 'none';
2338
1968
  }
@@ -2341,11 +1971,11 @@ declare module 'stripe' {
2341
1971
  /**
2342
1972
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2343
1973
  *
2344
- * 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.
1974
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2345
1975
  *
2346
- * 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.
1976
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2347
1977
  *
2348
- * 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).
1978
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2349
1979
  */
2350
1980
  setup_future_usage?: Ideal.SetupFutureUsage;
2351
1981
  }
@@ -2370,11 +2000,11 @@ declare module 'stripe' {
2370
2000
  /**
2371
2001
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2372
2002
  *
2373
- * 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.
2003
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2374
2004
  *
2375
- * 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.
2005
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2376
2006
  *
2377
- * 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).
2007
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2378
2008
  */
2379
2009
  setup_future_usage?: 'none';
2380
2010
  }
@@ -2403,11 +2033,11 @@ declare module 'stripe' {
2403
2033
  /**
2404
2034
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2405
2035
  *
2406
- * 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.
2036
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2407
2037
  *
2408
- * 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.
2038
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2409
2039
  *
2410
- * 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).
2040
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2411
2041
  */
2412
2042
  setup_future_usage?: 'none';
2413
2043
  }
@@ -2427,11 +2057,11 @@ declare module 'stripe' {
2427
2057
  /**
2428
2058
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2429
2059
  *
2430
- * 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.
2060
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2431
2061
  *
2432
- * 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.
2062
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2433
2063
  *
2434
- * 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).
2064
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2435
2065
  */
2436
2066
  setup_future_usage?: Link.SetupFutureUsage;
2437
2067
  }
@@ -2449,11 +2079,11 @@ declare module 'stripe' {
2449
2079
  /**
2450
2080
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2451
2081
  *
2452
- * 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.
2082
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2453
2083
  *
2454
- * 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.
2084
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2455
2085
  *
2456
- * 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).
2086
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2457
2087
  */
2458
2088
  setup_future_usage?: 'none';
2459
2089
  }
@@ -2462,11 +2092,11 @@ declare module 'stripe' {
2462
2092
  /**
2463
2093
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2464
2094
  *
2465
- * 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.
2095
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2466
2096
  *
2467
- * 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.
2097
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2468
2098
  *
2469
- * 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).
2099
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2470
2100
  */
2471
2101
  setup_future_usage?: 'none';
2472
2102
  }
@@ -2480,11 +2110,11 @@ declare module 'stripe' {
2480
2110
  /**
2481
2111
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2482
2112
  *
2483
- * 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.
2113
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2484
2114
  *
2485
- * 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.
2115
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2486
2116
  *
2487
- * 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).
2117
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2488
2118
  */
2489
2119
  setup_future_usage?: 'none';
2490
2120
  }
@@ -2493,11 +2123,11 @@ declare module 'stripe' {
2493
2123
  /**
2494
2124
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2495
2125
  *
2496
- * 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.
2126
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2497
2127
  *
2498
- * 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.
2128
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2499
2129
  *
2500
- * 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).
2130
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2501
2131
  */
2502
2132
  setup_future_usage?: 'none';
2503
2133
  }
@@ -2506,11 +2136,11 @@ declare module 'stripe' {
2506
2136
  /**
2507
2137
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2508
2138
  *
2509
- * 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.
2139
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2510
2140
  *
2511
- * 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.
2141
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2512
2142
  *
2513
- * 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).
2143
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2514
2144
  */
2515
2145
  setup_future_usage?: 'none';
2516
2146
  }
@@ -2531,110 +2161,22 @@ declare module 'stripe' {
2531
2161
  */
2532
2162
  reference: string | null;
2533
2163
 
2534
- /**
2535
- * A reference of the PayPal transaction visible to customer which is mapped to PayPal's invoice ID. This must be a globally unique ID if you have configured in your PayPal settings to block multiple payments per invoice ID.
2536
- */
2537
- reference_id?: string | null;
2538
-
2539
2164
  /**
2540
2165
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2541
2166
  *
2542
- * 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.
2167
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2543
2168
  *
2544
- * 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.
2169
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2545
2170
  *
2546
- * 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).
2171
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2547
2172
  */
2548
2173
  setup_future_usage?: Paypal.SetupFutureUsage;
2549
-
2550
- /**
2551
- * The Stripe connected account IDs of the sellers on the platform for this transaction (optional). Only allowed when [separate charges and transfers](https://stripe.com/docs/connect/separate-charges-and-transfers) are used.
2552
- */
2553
- subsellers?: Array<string>;
2554
2174
  }
2555
2175
 
2556
2176
  namespace Paypal {
2557
2177
  type SetupFutureUsage = 'none' | 'off_session';
2558
2178
  }
2559
2179
 
2560
- interface Payto {
2561
- mandate_options?: Payto.MandateOptions;
2562
-
2563
- /**
2564
- * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2565
- *
2566
- * 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.
2567
- *
2568
- * 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.
2569
- *
2570
- * 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).
2571
- */
2572
- setup_future_usage?: Payto.SetupFutureUsage;
2573
- }
2574
-
2575
- namespace Payto {
2576
- interface MandateOptions {
2577
- /**
2578
- * Amount that will be collected. It is required when `amount_type` is `fixed`.
2579
- */
2580
- amount: number | null;
2581
-
2582
- /**
2583
- * The type of amount that will be collected. The amount charged must be exact or up to the value of `amount` param for `fixed` or `maximum` type respectively.
2584
- */
2585
- amount_type: MandateOptions.AmountType | null;
2586
-
2587
- /**
2588
- * Date, in YYYY-MM-DD format, after which payments will not be collected. Defaults to no end date.
2589
- */
2590
- end_date: string | null;
2591
-
2592
- /**
2593
- * The periodicity at which payments will be collected.
2594
- */
2595
- payment_schedule: MandateOptions.PaymentSchedule | null;
2596
-
2597
- /**
2598
- * The number of payments that will be made during a payment period. Defaults to 1 except for when `payment_schedule` is `adhoc`. In that case, it defaults to no limit.
2599
- */
2600
- payments_per_period: number | null;
2601
-
2602
- /**
2603
- * The purpose for which payments are made. Defaults to retail.
2604
- */
2605
- purpose: MandateOptions.Purpose | null;
2606
- }
2607
-
2608
- namespace MandateOptions {
2609
- type AmountType = 'fixed' | 'maximum';
2610
-
2611
- type PaymentSchedule =
2612
- | 'adhoc'
2613
- | 'annual'
2614
- | 'daily'
2615
- | 'fortnightly'
2616
- | 'monthly'
2617
- | 'quarterly'
2618
- | 'semi_annual'
2619
- | 'weekly';
2620
-
2621
- type Purpose =
2622
- | 'dependant_support'
2623
- | 'government'
2624
- | 'loan'
2625
- | 'mortgage'
2626
- | 'other'
2627
- | 'pension'
2628
- | 'personal'
2629
- | 'retail'
2630
- | 'salary'
2631
- | 'tax'
2632
- | 'utility';
2633
- }
2634
-
2635
- type SetupFutureUsage = 'none' | 'off_session';
2636
- }
2637
-
2638
2180
  interface Pix {
2639
2181
  /**
2640
2182
  * The number of seconds (between 10 and 1209600) after which Pix payment will expire.
@@ -2649,11 +2191,11 @@ declare module 'stripe' {
2649
2191
  /**
2650
2192
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2651
2193
  *
2652
- * 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.
2194
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2653
2195
  *
2654
- * 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.
2196
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2655
2197
  *
2656
- * 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).
2198
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2657
2199
  */
2658
2200
  setup_future_usage?: 'none';
2659
2201
  }
@@ -2662,22 +2204,15 @@ declare module 'stripe' {
2662
2204
  /**
2663
2205
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2664
2206
  *
2665
- * 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.
2207
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2666
2208
  *
2667
- * 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.
2209
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2668
2210
  *
2669
- * 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).
2211
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2670
2212
  */
2671
2213
  setup_future_usage?: 'none';
2672
2214
  }
2673
2215
 
2674
- interface Rechnung {
2675
- /**
2676
- * A unique identifier that correlates each transaction with the collected risk data.
2677
- */
2678
- risk_correlation_id: string | null;
2679
- }
2680
-
2681
2216
  interface RevolutPay {
2682
2217
  /**
2683
2218
  * Controls when the funds will be captured from the customer's account.
@@ -2687,11 +2222,11 @@ declare module 'stripe' {
2687
2222
  /**
2688
2223
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2689
2224
  *
2690
- * 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.
2225
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2691
2226
  *
2692
- * 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.
2227
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2693
2228
  *
2694
- * 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).
2229
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2695
2230
  */
2696
2231
  setup_future_usage?: RevolutPay.SetupFutureUsage;
2697
2232
  }
@@ -2706,11 +2241,11 @@ declare module 'stripe' {
2706
2241
  /**
2707
2242
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2708
2243
  *
2709
- * 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.
2244
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2710
2245
  *
2711
- * 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.
2246
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2712
2247
  *
2713
- * 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).
2248
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2714
2249
  */
2715
2250
  setup_future_usage?: SepaDebit.SetupFutureUsage;
2716
2251
  }
@@ -2730,11 +2265,11 @@ declare module 'stripe' {
2730
2265
  /**
2731
2266
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2732
2267
  *
2733
- * 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.
2268
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2734
2269
  *
2735
- * 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.
2270
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2736
2271
  *
2737
- * 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).
2272
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2738
2273
  */
2739
2274
  setup_future_usage?: Sofort.SetupFutureUsage;
2740
2275
  }
@@ -2761,11 +2296,11 @@ declare module 'stripe' {
2761
2296
  /**
2762
2297
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2763
2298
  *
2764
- * 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.
2299
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2765
2300
  *
2766
- * 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.
2301
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2767
2302
  *
2768
- * 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).
2303
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2769
2304
  */
2770
2305
  setup_future_usage?: 'none';
2771
2306
  }
@@ -2774,11 +2309,11 @@ declare module 'stripe' {
2774
2309
  /**
2775
2310
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2776
2311
  *
2777
- * 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.
2312
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2778
2313
  *
2779
- * 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.
2314
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2780
2315
  *
2781
- * 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).
2316
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2782
2317
  */
2783
2318
  setup_future_usage?: 'none';
2784
2319
  }
@@ -2796,11 +2331,11 @@ declare module 'stripe' {
2796
2331
  /**
2797
2332
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2798
2333
  *
2799
- * 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.
2334
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2800
2335
  *
2801
- * 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.
2336
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2802
2337
  *
2803
- * 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).
2338
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2804
2339
  */
2805
2340
  setup_future_usage?: UsBankAccount.SetupFutureUsage;
2806
2341
 
@@ -2814,8 +2349,6 @@ declare module 'stripe' {
2814
2349
  interface FinancialConnections {
2815
2350
  filters?: FinancialConnections.Filters;
2816
2351
 
2817
- manual_entry?: FinancialConnections.ManualEntry;
2818
-
2819
2352
  /**
2820
2353
  * The list of permissions to request. The `payment_method` permission must be included.
2821
2354
  */
@@ -2838,39 +2371,19 @@ declare module 'stripe' {
2838
2371
  * The account subcategories to use to filter for possible accounts to link. Valid subcategories are `checking` and `savings`.
2839
2372
  */
2840
2373
  account_subcategories?: Array<Filters.AccountSubcategory>;
2841
-
2842
- /**
2843
- * The institution to use to filter for possible accounts to link.
2844
- */
2845
- institution?: string;
2846
2374
  }
2847
2375
 
2848
2376
  namespace Filters {
2849
2377
  type AccountSubcategory = 'checking' | 'savings';
2850
2378
  }
2851
2379
 
2852
- interface ManualEntry {
2853
- /**
2854
- * Settings for configuring manual entry of account details.
2855
- */
2856
- mode?: ManualEntry.Mode;
2857
- }
2858
-
2859
- namespace ManualEntry {
2860
- type Mode = 'automatic' | 'custom';
2861
- }
2862
-
2863
2380
  type Permission =
2864
2381
  | 'balances'
2865
2382
  | 'ownership'
2866
2383
  | 'payment_method'
2867
2384
  | 'transactions';
2868
2385
 
2869
- type Prefetch =
2870
- | 'balances'
2871
- | 'inferred_balances'
2872
- | 'ownership'
2873
- | 'transactions';
2386
+ type Prefetch = 'balances' | 'ownership' | 'transactions';
2874
2387
  }
2875
2388
 
2876
2389
  interface MandateOptions {
@@ -2901,11 +2414,11 @@ declare module 'stripe' {
2901
2414
  /**
2902
2415
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2903
2416
  *
2904
- * 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.
2417
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2905
2418
  *
2906
- * 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.
2419
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2907
2420
  *
2908
- * 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).
2421
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2909
2422
  */
2910
2423
  setup_future_usage?: 'none';
2911
2424
  }
@@ -2918,11 +2431,11 @@ declare module 'stripe' {
2918
2431
  /**
2919
2432
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2920
2433
  *
2921
- * 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.
2434
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://stripe.com/payments/save-during-payment) to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still [attach](https://stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2922
2435
  *
2923
- * 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.
2436
+ * If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2924
2437
  *
2925
- * 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).
2438
+ * When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://stripe.com/strong-customer-authentication).
2926
2439
  */
2927
2440
  setup_future_usage?: 'none';
2928
2441
  }
@@ -2957,8 +2470,6 @@ declare module 'stripe' {
2957
2470
  }
2958
2471
  }
2959
2472
 
2960
- type SecretKeyConfirmation = 'optional' | 'required';
2961
-
2962
2473
  type SetupFutureUsage = 'off_session' | 'on_session';
2963
2474
 
2964
2475
  interface Shipping {