stripe 16.6.0-beta.1 → 16.6.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 (159) hide show
  1. package/CHANGELOG.md +116 -778
  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 -13
  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/Terminal/Readers.js +0 -12
  15. package/cjs/resources.js +10 -42
  16. package/cjs/stripe.core.js +3 -6
  17. package/cjs/utils.js +3 -30
  18. package/esm/RequestSender.js +6 -67
  19. package/esm/StripeResource.js +2 -2
  20. package/esm/apiVersion.js +0 -1
  21. package/esm/multipart.js +2 -2
  22. package/esm/resources/FinancialConnections/Accounts.js +0 -5
  23. package/esm/resources/Invoices.js +0 -13
  24. package/esm/resources/OAuth.js +2 -2
  25. package/esm/resources/PaymentIntents.js +0 -4
  26. package/esm/resources/Quotes.js +0 -32
  27. package/esm/resources/SubscriptionSchedules.js +0 -4
  28. package/esm/resources/Terminal/Readers.js +0 -12
  29. package/esm/resources.js +0 -28
  30. package/esm/stripe.core.js +3 -6
  31. package/esm/utils.js +1 -27
  32. package/package.json +1 -1
  33. package/types/AccountLinksResource.d.ts +1 -5
  34. package/types/AccountSessions.d.ts +0 -15
  35. package/types/AccountSessionsResource.d.ts +0 -163
  36. package/types/Accounts.d.ts +1 -106
  37. package/types/AccountsResource.d.ts +0 -246
  38. package/types/Charges.d.ts +0 -72
  39. package/types/ChargesResource.d.ts +0 -1294
  40. package/types/Checkout/Sessions.d.ts +62 -29
  41. package/types/Checkout/SessionsResource.d.ts +64 -16
  42. package/types/ConfirmationTokens.d.ts +0 -62
  43. package/types/Coupons.d.ts +1 -1
  44. package/types/CouponsResource.d.ts +1 -1
  45. package/types/CreditNotes.d.ts +0 -21
  46. package/types/CreditNotesResource.d.ts +0 -51
  47. package/types/CustomersResource.d.ts +0 -2
  48. package/types/Disputes.d.ts +0 -168
  49. package/types/DisputesResource.d.ts +0 -120
  50. package/types/EventTypes.d.ts +0 -426
  51. package/types/Events.d.ts +0 -83
  52. package/types/FinancialConnections/Accounts.d.ts +3 -31
  53. package/types/FinancialConnections/AccountsResource.d.ts +3 -35
  54. package/types/FinancialConnections/Sessions.d.ts +1 -49
  55. package/types/FinancialConnections/SessionsResource.d.ts +1 -38
  56. package/types/InvoiceItems.d.ts +0 -5
  57. package/types/InvoiceItemsResource.d.ts +0 -98
  58. package/types/InvoiceLineItems.d.ts +0 -22
  59. package/types/Invoices.d.ts +2 -116
  60. package/types/InvoicesResource.d.ts +1782 -5359
  61. package/types/Issuing/CardholdersResource.d.ts +1 -2
  62. package/types/LineItems.d.ts +0 -7
  63. package/types/Mandates.d.ts +0 -77
  64. package/types/PaymentIntents.d.ts +79 -491
  65. package/types/PaymentIntentsResource.d.ts +3625 -6925
  66. package/types/PaymentMethodConfigurations.d.ts +0 -36
  67. package/types/PaymentMethodConfigurationsResource.d.ts +0 -50
  68. package/types/PaymentMethods.d.ts +0 -62
  69. package/types/PaymentMethodsResource.d.ts +0 -110
  70. package/types/Prices.d.ts +0 -22
  71. package/types/PricesResource.d.ts +0 -22
  72. package/types/Products.d.ts +0 -39
  73. package/types/ProductsResource.d.ts +0 -36
  74. package/types/Quotes.d.ts +1 -578
  75. package/types/QuotesResource.d.ts +266 -3175
  76. package/types/SetupAttempts.d.ts +1 -9
  77. package/types/SetupIntents.d.ts +3 -111
  78. package/types/SetupIntentsResource.d.ts +4 -499
  79. package/types/Sources.d.ts +0 -23
  80. package/types/SubscriptionItems.d.ts +0 -21
  81. package/types/SubscriptionItemsResource.d.ts +1 -110
  82. package/types/SubscriptionSchedules.d.ts +0 -164
  83. package/types/SubscriptionSchedulesResource.d.ts +13 -1231
  84. package/types/Subscriptions.d.ts +1 -46
  85. package/types/SubscriptionsResource.d.ts +4 -349
  86. package/types/Terminal/Readers.d.ts +0 -278
  87. package/types/Terminal/ReadersResource.d.ts +0 -208
  88. package/types/TestHelpers/ConfirmationTokensResource.d.ts +0 -55
  89. package/types/TestHelpers/Treasury/ReceivedCreditsResource.d.ts +0 -26
  90. package/types/TestHelpers/Treasury/ReceivedDebitsResource.d.ts +0 -26
  91. package/types/Treasury/FinancialAccounts.d.ts +0 -5
  92. package/types/Treasury/FinancialAccountsResource.d.ts +0 -10
  93. package/types/Treasury/OutboundTransfers.d.ts +0 -26
  94. package/types/Treasury/OutboundTransfersResource.d.ts +0 -26
  95. package/types/Treasury/ReceivedCredits.d.ts +0 -26
  96. package/types/Treasury/ReceivedDebits.d.ts +0 -31
  97. package/types/WebhookEndpointsResource.d.ts +0 -50
  98. package/types/index.d.ts +0 -69
  99. package/types/lib.d.ts +0 -12
  100. package/cjs/resources/AccountNotices.js +0 -21
  101. package/cjs/resources/Billing/Alerts.js +0 -27
  102. package/cjs/resources/Capital/FinancingOffers.js +0 -21
  103. package/cjs/resources/Capital/FinancingSummary.js +0 -12
  104. package/cjs/resources/Capital/FinancingTransactions.js +0 -17
  105. package/cjs/resources/FinancialConnections/Institutions.js +0 -17
  106. package/cjs/resources/GiftCards/Cards.js +0 -23
  107. package/cjs/resources/GiftCards/Transactions.js +0 -33
  108. package/cjs/resources/Issuing/CreditUnderwritingRecords.js +0 -33
  109. package/cjs/resources/Margins.js +0 -22
  110. package/cjs/resources/Orders.js +0 -24
  111. package/cjs/resources/QuotePhases.js +0 -22
  112. package/cjs/resources/Tax/Associations.js +0 -9
  113. package/cjs/resources/Tax/Forms.js +0 -20
  114. package/esm/resources/AccountNotices.js +0 -18
  115. package/esm/resources/Billing/Alerts.js +0 -24
  116. package/esm/resources/Capital/FinancingOffers.js +0 -18
  117. package/esm/resources/Capital/FinancingSummary.js +0 -9
  118. package/esm/resources/Capital/FinancingTransactions.js +0 -14
  119. package/esm/resources/FinancialConnections/Institutions.js +0 -14
  120. package/esm/resources/GiftCards/Cards.js +0 -20
  121. package/esm/resources/GiftCards/Transactions.js +0 -30
  122. package/esm/resources/Issuing/CreditUnderwritingRecords.js +0 -30
  123. package/esm/resources/Margins.js +0 -19
  124. package/esm/resources/Orders.js +0 -21
  125. package/esm/resources/QuotePhases.js +0 -19
  126. package/esm/resources/Tax/Associations.js +0 -6
  127. package/esm/resources/Tax/Forms.js +0 -17
  128. package/types/AccountNotices.d.ts +0 -113
  129. package/types/AccountNoticesResource.d.ts +0 -98
  130. package/types/Billing/AlertsResource.d.ts +0 -176
  131. package/types/Capital/FinancingOffers.d.ts +0 -188
  132. package/types/Capital/FinancingOffersResource.d.ts +0 -97
  133. package/types/Capital/FinancingSummary.d.ts +0 -106
  134. package/types/Capital/FinancingSummaryResource.d.ts +0 -27
  135. package/types/Capital/FinancingTransactions.d.ts +0 -135
  136. package/types/Capital/FinancingTransactionsResource.d.ts +0 -68
  137. package/types/FinancialConnections/AccountInferredBalances.d.ts +0 -38
  138. package/types/FinancialConnections/Institutions.d.ts +0 -93
  139. package/types/FinancialConnections/InstitutionsResource.d.ts +0 -47
  140. package/types/GiftCards/Cards.d.ts +0 -118
  141. package/types/GiftCards/CardsResource.d.ts +0 -159
  142. package/types/GiftCards/Transactions.d.ts +0 -129
  143. package/types/GiftCards/TransactionsResource.d.ts +0 -201
  144. package/types/InvoicePayments.d.ts +0 -138
  145. package/types/Issuing/CreditUnderwritingRecords.d.ts +0 -446
  146. package/types/Issuing/CreditUnderwritingRecordsResource.d.ts +0 -1017
  147. package/types/Margins.d.ts +0 -56
  148. package/types/MarginsResource.d.ts +0 -114
  149. package/types/Orders.d.ts +0 -1057
  150. package/types/OrdersResource.d.ts +0 -2711
  151. package/types/QuoteLines.d.ts +0 -634
  152. package/types/QuotePhases.d.ts +0 -198
  153. package/types/QuotePhasesResource.d.ts +0 -67
  154. package/types/QuotePreviewInvoices.d.ts +0 -1528
  155. package/types/QuotePreviewSubscriptionSchedules.d.ts +0 -778
  156. package/types/Tax/Associations.d.ts +0 -126
  157. package/types/Tax/AssociationsResource.d.ts +0 -29
  158. package/types/Tax/Forms.d.ts +0 -133
  159. 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
  */
@@ -104,7 +102,7 @@ declare module 'stripe' {
104
102
  *
105
103
  * Payment methods attached to other Customers cannot be used with this PaymentIntent.
106
104
  *
107
- * If present in combination with [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage), this PaymentIntent's payment method will be attached to the Customer after the PaymentIntent has been confirmed and any required actions from the user are complete.
105
+ * If [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) is set and this PaymentIntent's payment method is not `card_present`, then the payment method attaches to the Customer after the PaymentIntent has been confirmed and any required actions from the user are complete. 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.
108
106
  */
109
107
  customer: string | Stripe.Customer | Stripe.DeletedCustomer | null;
110
108
 
@@ -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,16 +181,13 @@ 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
187
  * 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.
197
188
  *
189
+ * 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.
190
+ *
198
191
  * 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).
199
192
  */
200
193
  setup_future_usage: PaymentIntent.SetupFutureUsage | null;
@@ -253,25 +246,6 @@ declare module 'stripe' {
253
246
  }
254
247
  }
255
248
 
256
- interface AsyncWorkflows {
257
- inputs?: AsyncWorkflows.Inputs;
258
- }
259
-
260
- namespace AsyncWorkflows {
261
- interface Inputs {
262
- tax?: Inputs.Tax;
263
- }
264
-
265
- namespace Inputs {
266
- interface Tax {
267
- /**
268
- * The [TaxCalculation](https://stripe.com/docs/api/tax/calculations) id
269
- */
270
- calculation: string;
271
- }
272
- }
273
- }
274
-
275
249
  interface AutomaticPaymentMethods {
276
250
  /**
277
251
  * Controls whether this PaymentIntent will accept redirect-based payment methods.
@@ -436,6 +410,7 @@ declare module 'stripe' {
436
410
  | 'charge_already_refunded'
437
411
  | 'charge_disputed'
438
412
  | 'charge_exceeds_source_limit'
413
+ | 'charge_exceeds_transaction_limit'
439
414
  | 'charge_expired_for_capture'
440
415
  | 'charge_invalid_parameter'
441
416
  | 'charge_not_refundable'
@@ -450,15 +425,11 @@ declare module 'stripe' {
450
425
  | 'email_invalid'
451
426
  | 'expired_card'
452
427
  | 'financial_connections_account_inactive'
453
- | 'financial_connections_institution_unavailable'
454
428
  | 'financial_connections_no_successful_transaction_refresh'
455
429
  | 'forwarding_api_inactive'
456
430
  | 'forwarding_api_invalid_parameter'
457
431
  | 'forwarding_api_upstream_connection_error'
458
432
  | 'forwarding_api_upstream_connection_timeout'
459
- | 'gift_card_balance_insufficient'
460
- | 'gift_card_code_exists'
461
- | 'gift_card_inactive'
462
433
  | 'idempotency_key_in_use'
463
434
  | 'incorrect_address'
464
435
  | 'incorrect_cvc'
@@ -547,7 +518,6 @@ declare module 'stripe' {
547
518
  | 'return_intent_already_processed'
548
519
  | 'routing_number_invalid'
549
520
  | 'secret_key_required'
550
- | 'sensitive_data_access_expired'
551
521
  | 'sepa_unsupported_account'
552
522
  | 'setup_attempt_failed'
553
523
  | 'setup_intent_authentication_failure'
@@ -1291,289 +1261,6 @@ declare module 'stripe' {
1291
1261
  }
1292
1262
  }
1293
1263
 
1294
- interface PaymentDetails {
1295
- car_rental?: PaymentDetails.CarRental;
1296
-
1297
- event_details?: PaymentDetails.EventDetails;
1298
-
1299
- subscription?: PaymentDetails.Subscription;
1300
- }
1301
-
1302
- namespace PaymentDetails {
1303
- interface CarRental {
1304
- affiliate?: CarRental.Affiliate;
1305
-
1306
- /**
1307
- * The booking number associated with the car rental.
1308
- */
1309
- booking_number: string;
1310
-
1311
- /**
1312
- * Class code of the car.
1313
- */
1314
- car_class_code?: string;
1315
-
1316
- /**
1317
- * Make of the car.
1318
- */
1319
- car_make?: string;
1320
-
1321
- /**
1322
- * Model of the car.
1323
- */
1324
- car_model?: string;
1325
-
1326
- /**
1327
- * The name of the rental car company.
1328
- */
1329
- company?: string;
1330
-
1331
- /**
1332
- * The customer service phone number of the car rental company.
1333
- */
1334
- customer_service_phone_number?: string;
1335
-
1336
- /**
1337
- * Number of days the car is being rented.
1338
- */
1339
- days_rented: number;
1340
-
1341
- delivery?: CarRental.Delivery;
1342
-
1343
- /**
1344
- * The details of the drivers associated with the trip.
1345
- */
1346
- drivers?: Array<CarRental.Driver>;
1347
-
1348
- /**
1349
- * List of additional charges being billed.
1350
- */
1351
- extra_charges?: Array<CarRental.ExtraCharge>;
1352
-
1353
- /**
1354
- * Indicates if the customer did not keep nor cancel their booking.
1355
- */
1356
- no_show?: boolean;
1357
-
1358
- pickup_address?: Stripe.Address;
1359
-
1360
- /**
1361
- * Car pick-up time. Measured in seconds since the Unix epoch.
1362
- */
1363
- pickup_at: number;
1364
-
1365
- /**
1366
- * Rental rate.
1367
- */
1368
- rate_amount?: number;
1369
-
1370
- /**
1371
- * The frequency at which the rate amount is applied. One of `day`, `week` or `month`
1372
- */
1373
- rate_interval?: CarRental.RateInterval;
1374
-
1375
- /**
1376
- * The full name of the person or entity renting the car.
1377
- */
1378
- renter_name?: string;
1379
-
1380
- return_address?: Stripe.Address;
1381
-
1382
- /**
1383
- * Car return time. Measured in seconds since the Unix epoch.
1384
- */
1385
- return_at: number;
1386
-
1387
- /**
1388
- * Indicates whether the goods or services are tax-exempt or tax is not collected.
1389
- */
1390
- tax_exempt?: boolean;
1391
- }
1392
-
1393
- namespace CarRental {
1394
- interface Affiliate {
1395
- /**
1396
- * The name of the affiliate that originated the purchase.
1397
- */
1398
- name?: string;
1399
- }
1400
-
1401
- interface Delivery {
1402
- /**
1403
- * The delivery method for the payment
1404
- */
1405
- mode?: Delivery.Mode;
1406
-
1407
- recipient?: Delivery.Recipient;
1408
- }
1409
-
1410
- namespace Delivery {
1411
- type Mode = 'email' | 'phone' | 'pickup' | 'post';
1412
-
1413
- interface Recipient {
1414
- /**
1415
- * The email of the recipient the ticket is delivered to.
1416
- */
1417
- email?: string;
1418
-
1419
- /**
1420
- * The name of the recipient the ticket is delivered to.
1421
- */
1422
- name?: string;
1423
-
1424
- /**
1425
- * The phone number of the recipient the ticket is delivered to.
1426
- */
1427
- phone?: string;
1428
- }
1429
- }
1430
-
1431
- interface Driver {
1432
- /**
1433
- * Full name of the driver on the reservation.
1434
- */
1435
- name?: string;
1436
- }
1437
-
1438
- type ExtraCharge =
1439
- | 'extra_mileage'
1440
- | 'gas'
1441
- | 'late_return'
1442
- | 'one_way_service'
1443
- | 'parking_violation';
1444
-
1445
- type RateInterval = 'day' | 'month' | 'week';
1446
- }
1447
-
1448
- interface EventDetails {
1449
- /**
1450
- * Indicates if the tickets are digitally checked when entering the venue.
1451
- */
1452
- access_controlled_venue?: boolean;
1453
-
1454
- address?: Stripe.Address;
1455
-
1456
- affiliate?: EventDetails.Affiliate;
1457
-
1458
- /**
1459
- * The name of the company
1460
- */
1461
- company?: string;
1462
-
1463
- delivery?: EventDetails.Delivery;
1464
-
1465
- /**
1466
- * Event end time. Measured in seconds since the Unix epoch.
1467
- */
1468
- ends_at?: number;
1469
-
1470
- /**
1471
- * Type of the event entertainment (concert, sports event etc)
1472
- */
1473
- genre?: string;
1474
-
1475
- /**
1476
- * The name of the event.
1477
- */
1478
- name?: string;
1479
-
1480
- /**
1481
- * Event start time. Measured in seconds since the Unix epoch.
1482
- */
1483
- starts_at?: number;
1484
- }
1485
-
1486
- namespace EventDetails {
1487
- interface Affiliate {
1488
- /**
1489
- * The name of the affiliate that originated the purchase.
1490
- */
1491
- name?: string;
1492
- }
1493
-
1494
- interface Delivery {
1495
- /**
1496
- * The delivery method for the payment
1497
- */
1498
- mode?: Delivery.Mode;
1499
-
1500
- recipient?: Delivery.Recipient;
1501
- }
1502
-
1503
- namespace Delivery {
1504
- type Mode = 'email' | 'phone' | 'pickup' | 'post';
1505
-
1506
- interface Recipient {
1507
- /**
1508
- * The email of the recipient the ticket is delivered to.
1509
- */
1510
- email?: string;
1511
-
1512
- /**
1513
- * The name of the recipient the ticket is delivered to.
1514
- */
1515
- name?: string;
1516
-
1517
- /**
1518
- * The phone number of the recipient the ticket is delivered to.
1519
- */
1520
- phone?: string;
1521
- }
1522
- }
1523
- }
1524
-
1525
- interface Subscription {
1526
- affiliate?: Subscription.Affiliate;
1527
-
1528
- /**
1529
- * Info whether the subscription will be auto renewed upon expiry.
1530
- */
1531
- auto_renewal?: boolean;
1532
-
1533
- billing_interval?: Subscription.BillingInterval;
1534
-
1535
- /**
1536
- * Subscription end time. Measured in seconds since the Unix epoch.
1537
- */
1538
- ends_at?: number;
1539
-
1540
- /**
1541
- * Name of the product on subscription. e.g. Apple Music Subscription.
1542
- */
1543
- name?: string;
1544
-
1545
- /**
1546
- * Subscription start time. Measured in seconds since the Unix epoch.
1547
- */
1548
- starts_at?: number;
1549
- }
1550
-
1551
- namespace Subscription {
1552
- interface Affiliate {
1553
- /**
1554
- * The name of the affiliate that originated the purchase.
1555
- */
1556
- name?: string;
1557
- }
1558
-
1559
- interface BillingInterval {
1560
- /**
1561
- * The number of intervals, as an whole number greater than 0. Stripe multiplies this by the interval type to get the overall duration.
1562
- */
1563
- count?: number;
1564
-
1565
- /**
1566
- * Specifies a type of interval unit. Either `day`, `week`, `month` or `year`.
1567
- */
1568
- interval?: BillingInterval.Interval;
1569
- }
1570
-
1571
- namespace BillingInterval {
1572
- type Interval = 'day' | 'month' | 'week' | 'year';
1573
- }
1574
- }
1575
- }
1576
-
1577
1264
  interface PaymentMethodConfigurationDetails {
1578
1265
  /**
1579
1266
  * ID of the payment method configuration used.
@@ -1645,14 +1332,10 @@ declare module 'stripe' {
1645
1332
 
1646
1333
  paypal?: PaymentMethodOptions.Paypal;
1647
1334
 
1648
- payto?: PaymentMethodOptions.Payto;
1649
-
1650
1335
  pix?: PaymentMethodOptions.Pix;
1651
1336
 
1652
1337
  promptpay?: PaymentMethodOptions.Promptpay;
1653
1338
 
1654
- rechnung?: PaymentMethodOptions.Rechnung;
1655
-
1656
1339
  revolut_pay?: PaymentMethodOptions.RevolutPay;
1657
1340
 
1658
1341
  sepa_debit?: PaymentMethodOptions.SepaDebit;
@@ -1679,6 +1362,8 @@ declare module 'stripe' {
1679
1362
  *
1680
1363
  * 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.
1681
1364
  *
1365
+ * 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
+ *
1682
1367
  * 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).
1683
1368
  */
1684
1369
  setup_future_usage?: AcssDebit.SetupFutureUsage;
@@ -1739,6 +1424,8 @@ declare module 'stripe' {
1739
1424
  *
1740
1425
  * 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.
1741
1426
  *
1427
+ * 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
+ *
1742
1429
  * 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).
1743
1430
  */
1744
1431
  setup_future_usage?: 'none';
@@ -1761,6 +1448,8 @@ declare module 'stripe' {
1761
1448
  *
1762
1449
  * 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.
1763
1450
  *
1451
+ * 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
+ *
1764
1453
  * 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).
1765
1454
  */
1766
1455
  setup_future_usage?: 'none';
@@ -1772,6 +1461,8 @@ declare module 'stripe' {
1772
1461
  *
1773
1462
  * 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.
1774
1463
  *
1464
+ * 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
+ *
1775
1466
  * 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).
1776
1467
  */
1777
1468
  setup_future_usage?: Alipay.SetupFutureUsage;
@@ -1792,6 +1483,8 @@ declare module 'stripe' {
1792
1483
  *
1793
1484
  * 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.
1794
1485
  *
1486
+ * 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
+ *
1795
1488
  * 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).
1796
1489
  */
1797
1490
  setup_future_usage?: AmazonPay.SetupFutureUsage;
@@ -1807,6 +1500,8 @@ declare module 'stripe' {
1807
1500
  *
1808
1501
  * 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.
1809
1502
  *
1503
+ * 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
+ *
1810
1505
  * 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).
1811
1506
  */
1812
1507
  setup_future_usage?: AuBecsDebit.SetupFutureUsage;
@@ -1822,6 +1517,8 @@ declare module 'stripe' {
1822
1517
  *
1823
1518
  * 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.
1824
1519
  *
1520
+ * 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
+ *
1825
1522
  * 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).
1826
1523
  */
1827
1524
  setup_future_usage?: BacsDebit.SetupFutureUsage;
@@ -1842,6 +1539,8 @@ declare module 'stripe' {
1842
1539
  *
1843
1540
  * 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.
1844
1541
  *
1542
+ * 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
+ *
1845
1544
  * 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).
1846
1545
  */
1847
1546
  setup_future_usage?: Bancontact.SetupFutureUsage;
@@ -1859,6 +1558,8 @@ declare module 'stripe' {
1859
1558
  *
1860
1559
  * 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.
1861
1560
  *
1561
+ * 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
+ *
1862
1563
  * 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).
1863
1564
  */
1864
1565
  setup_future_usage?: 'none';
@@ -1875,6 +1576,8 @@ declare module 'stripe' {
1875
1576
  *
1876
1577
  * 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.
1877
1578
  *
1579
+ * 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
+ *
1878
1581
  * 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).
1879
1582
  */
1880
1583
  setup_future_usage?: Boleto.SetupFutureUsage;
@@ -1907,11 +1610,6 @@ declare module 'stripe' {
1907
1610
  */
1908
1611
  network: Card.Network | null;
1909
1612
 
1910
- /**
1911
- * Request ability to [decrement the authorization](https://stripe.com/docs/payments/decremental-authorization) for this PaymentIntent.
1912
- */
1913
- request_decremental_authorization?: Card.RequestDecrementalAuthorization;
1914
-
1915
1613
  /**
1916
1614
  * Request ability to [capture beyond the standard authorization validity window](https://stripe.com/docs/payments/extended-authorization) for this PaymentIntent.
1917
1615
  */
@@ -1947,6 +1645,8 @@ declare module 'stripe' {
1947
1645
  *
1948
1646
  * 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.
1949
1647
  *
1648
+ * 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
+ *
1950
1650
  * 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).
1951
1651
  */
1952
1652
  setup_future_usage?: Card.SetupFutureUsage;
@@ -1960,8 +1660,6 @@ declare module 'stripe' {
1960
1660
  * 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.
1961
1661
  */
1962
1662
  statement_descriptor_suffix_kanji?: string;
1963
-
1964
- statement_details?: Card.StatementDetails;
1965
1663
  }
1966
1664
 
1967
1665
  namespace Card {
@@ -2086,8 +1784,6 @@ declare module 'stripe' {
2086
1784
  | 'unknown'
2087
1785
  | 'visa';
2088
1786
 
2089
- type RequestDecrementalAuthorization = 'if_available' | 'never';
2090
-
2091
1787
  type RequestExtendedAuthorization = 'if_available' | 'never';
2092
1788
 
2093
1789
  type RequestIncrementalAuthorization = 'if_available' | 'never';
@@ -2099,49 +1795,6 @@ declare module 'stripe' {
2099
1795
  type RequestThreeDSecure = 'any' | 'automatic' | 'challenge';
2100
1796
 
2101
1797
  type SetupFutureUsage = 'none' | 'off_session' | 'on_session';
2102
-
2103
- interface StatementDetails {
2104
- address?: StatementDetails.Address;
2105
-
2106
- /**
2107
- * Phone number
2108
- */
2109
- phone?: string;
2110
- }
2111
-
2112
- namespace StatementDetails {
2113
- interface Address {
2114
- /**
2115
- * City, district, suburb, town, or village.
2116
- */
2117
- city?: string;
2118
-
2119
- /**
2120
- * Two-letter country code ([ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)).
2121
- */
2122
- country?: string;
2123
-
2124
- /**
2125
- * Address line 1 (e.g., street, PO Box, or company name).
2126
- */
2127
- line1?: string;
2128
-
2129
- /**
2130
- * Address line 2 (e.g., apartment, suite, unit, or building).
2131
- */
2132
- line2?: string;
2133
-
2134
- /**
2135
- * ZIP or postal code.
2136
- */
2137
- postal_code?: string;
2138
-
2139
- /**
2140
- * State, county, province, or region.
2141
- */
2142
- state?: string;
2143
- }
2144
- }
2145
1798
  }
2146
1799
 
2147
1800
  interface CardPresent {
@@ -2182,6 +1835,8 @@ declare module 'stripe' {
2182
1835
  *
2183
1836
  * 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.
2184
1837
  *
1838
+ * 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.
1839
+ *
2185
1840
  * 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).
2186
1841
  */
2187
1842
  setup_future_usage?: Cashapp.SetupFutureUsage;
@@ -2204,6 +1859,8 @@ declare module 'stripe' {
2204
1859
  *
2205
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.
2206
1861
  *
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.
1863
+ *
2207
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).
2208
1865
  */
2209
1866
  setup_future_usage?: 'none';
@@ -2262,6 +1919,8 @@ declare module 'stripe' {
2262
1919
  *
2263
1920
  * 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.
2264
1921
  *
1922
+ * 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.
1923
+ *
2265
1924
  * 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).
2266
1925
  */
2267
1926
  setup_future_usage?: 'none';
@@ -2273,6 +1932,8 @@ declare module 'stripe' {
2273
1932
  *
2274
1933
  * 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.
2275
1934
  *
1935
+ * 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.
1936
+ *
2276
1937
  * 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).
2277
1938
  */
2278
1939
  setup_future_usage?: 'none';
@@ -2284,6 +1945,8 @@ declare module 'stripe' {
2284
1945
  *
2285
1946
  * 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.
2286
1947
  *
1948
+ * 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.
1949
+ *
2287
1950
  * 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).
2288
1951
  */
2289
1952
  setup_future_usage?: 'none';
@@ -2295,6 +1958,8 @@ declare module 'stripe' {
2295
1958
  *
2296
1959
  * 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.
2297
1960
  *
1961
+ * 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.
1962
+ *
2298
1963
  * 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).
2299
1964
  */
2300
1965
  setup_future_usage?: 'none';
@@ -2306,6 +1971,8 @@ declare module 'stripe' {
2306
1971
  *
2307
1972
  * 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.
2308
1973
  *
1974
+ * 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.
1975
+ *
2309
1976
  * 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).
2310
1977
  */
2311
1978
  setup_future_usage?: Ideal.SetupFutureUsage;
@@ -2333,6 +2000,8 @@ declare module 'stripe' {
2333
2000
  *
2334
2001
  * 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.
2335
2002
  *
2003
+ * 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.
2004
+ *
2336
2005
  * 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).
2337
2006
  */
2338
2007
  setup_future_usage?: 'none';
@@ -2364,6 +2033,8 @@ declare module 'stripe' {
2364
2033
  *
2365
2034
  * 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.
2366
2035
  *
2036
+ * 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.
2037
+ *
2367
2038
  * 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).
2368
2039
  */
2369
2040
  setup_future_usage?: 'none';
@@ -2386,6 +2057,8 @@ declare module 'stripe' {
2386
2057
  *
2387
2058
  * 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.
2388
2059
  *
2060
+ * 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.
2061
+ *
2389
2062
  * 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).
2390
2063
  */
2391
2064
  setup_future_usage?: Link.SetupFutureUsage;
@@ -2406,6 +2079,8 @@ declare module 'stripe' {
2406
2079
  *
2407
2080
  * 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.
2408
2081
  *
2082
+ * 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.
2083
+ *
2409
2084
  * 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).
2410
2085
  */
2411
2086
  setup_future_usage?: 'none';
@@ -2417,6 +2092,8 @@ declare module 'stripe' {
2417
2092
  *
2418
2093
  * 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.
2419
2094
  *
2095
+ * 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.
2096
+ *
2420
2097
  * 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
2098
  */
2422
2099
  setup_future_usage?: 'none';
@@ -2433,6 +2110,8 @@ declare module 'stripe' {
2433
2110
  *
2434
2111
  * 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.
2435
2112
  *
2113
+ * 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.
2114
+ *
2436
2115
  * 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).
2437
2116
  */
2438
2117
  setup_future_usage?: 'none';
@@ -2444,6 +2123,8 @@ declare module 'stripe' {
2444
2123
  *
2445
2124
  * 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.
2446
2125
  *
2126
+ * 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.
2127
+ *
2447
2128
  * 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).
2448
2129
  */
2449
2130
  setup_future_usage?: 'none';
@@ -2455,6 +2136,8 @@ declare module 'stripe' {
2455
2136
  *
2456
2137
  * 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.
2457
2138
  *
2139
+ * 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.
2140
+ *
2458
2141
  * 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).
2459
2142
  */
2460
2143
  setup_future_usage?: 'none';
@@ -2476,106 +2159,22 @@ declare module 'stripe' {
2476
2159
  */
2477
2160
  reference: string | null;
2478
2161
 
2479
- /**
2480
- * 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.
2481
- */
2482
- reference_id?: string | null;
2483
-
2484
2162
  /**
2485
2163
  * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2486
2164
  *
2487
2165
  * 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.
2488
2166
  *
2167
+ * 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.
2168
+ *
2489
2169
  * 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).
2490
2170
  */
2491
2171
  setup_future_usage?: Paypal.SetupFutureUsage;
2492
-
2493
- /**
2494
- * 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.
2495
- */
2496
- subsellers?: Array<string>;
2497
2172
  }
2498
2173
 
2499
2174
  namespace Paypal {
2500
2175
  type SetupFutureUsage = 'none' | 'off_session';
2501
2176
  }
2502
2177
 
2503
- interface Payto {
2504
- mandate_options?: Payto.MandateOptions;
2505
-
2506
- /**
2507
- * Indicates that you intend to make future payments with this PaymentIntent's payment method.
2508
- *
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.
2510
- *
2511
- * 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).
2512
- */
2513
- setup_future_usage?: Payto.SetupFutureUsage;
2514
- }
2515
-
2516
- namespace Payto {
2517
- interface MandateOptions {
2518
- /**
2519
- * Amount that will be collected. It is required when `amount_type` is `fixed`.
2520
- */
2521
- amount: number | null;
2522
-
2523
- /**
2524
- * 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.
2525
- */
2526
- amount_type: MandateOptions.AmountType | null;
2527
-
2528
- /**
2529
- * Date, in YYYY-MM-DD format, after which payments will not be collected. Defaults to no end date.
2530
- */
2531
- end_date: string | null;
2532
-
2533
- /**
2534
- * The periodicity at which payments will be collected.
2535
- */
2536
- payment_schedule: MandateOptions.PaymentSchedule | null;
2537
-
2538
- /**
2539
- * 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.
2540
- */
2541
- payments_per_period: number | null;
2542
-
2543
- /**
2544
- * The purpose for which payments are made. Defaults to retail.
2545
- */
2546
- purpose: MandateOptions.Purpose | null;
2547
- }
2548
-
2549
- namespace MandateOptions {
2550
- type AmountType = 'fixed' | 'maximum';
2551
-
2552
- type PaymentSchedule =
2553
- | 'adhoc'
2554
- | 'annual'
2555
- | 'daily'
2556
- | 'fortnightly'
2557
- | 'monthly'
2558
- | 'quarterly'
2559
- | 'semi_annual'
2560
- | 'weekly';
2561
-
2562
- type Purpose =
2563
- | 'dependant_support'
2564
- | 'government'
2565
- | 'loan'
2566
- | 'mortgage'
2567
- | 'other'
2568
- | 'pension'
2569
- | 'personal'
2570
- | 'retail'
2571
- | 'salary'
2572
- | 'tax'
2573
- | 'utility';
2574
- }
2575
-
2576
- type SetupFutureUsage = 'none' | 'off_session';
2577
- }
2578
-
2579
2178
  interface Pix {
2580
2179
  /**
2581
2180
  * The number of seconds (between 10 and 1209600) after which Pix payment will expire.
@@ -2592,6 +2191,8 @@ declare module 'stripe' {
2592
2191
  *
2593
2192
  * 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.
2594
2193
  *
2194
+ * 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.
2195
+ *
2595
2196
  * 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).
2596
2197
  */
2597
2198
  setup_future_usage?: 'none';
@@ -2603,18 +2204,13 @@ declare module 'stripe' {
2603
2204
  *
2604
2205
  * 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.
2605
2206
  *
2207
+ * 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.
2208
+ *
2606
2209
  * 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).
2607
2210
  */
2608
2211
  setup_future_usage?: 'none';
2609
2212
  }
2610
2213
 
2611
- interface Rechnung {
2612
- /**
2613
- * A unique identifier that correlates each transaction with the collected risk data.
2614
- */
2615
- risk_correlation_id: string | null;
2616
- }
2617
-
2618
2214
  interface RevolutPay {
2619
2215
  /**
2620
2216
  * Controls when the funds will be captured from the customer's account.
@@ -2626,6 +2222,8 @@ declare module 'stripe' {
2626
2222
  *
2627
2223
  * 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.
2628
2224
  *
2225
+ * 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.
2226
+ *
2629
2227
  * 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).
2630
2228
  */
2631
2229
  setup_future_usage?: RevolutPay.SetupFutureUsage;
@@ -2643,6 +2241,8 @@ declare module 'stripe' {
2643
2241
  *
2644
2242
  * 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.
2645
2243
  *
2244
+ * 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.
2245
+ *
2646
2246
  * 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).
2647
2247
  */
2648
2248
  setup_future_usage?: SepaDebit.SetupFutureUsage;
@@ -2665,6 +2265,8 @@ declare module 'stripe' {
2665
2265
  *
2666
2266
  * 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.
2667
2267
  *
2268
+ * 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.
2269
+ *
2668
2270
  * 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).
2669
2271
  */
2670
2272
  setup_future_usage?: Sofort.SetupFutureUsage;
@@ -2694,6 +2296,8 @@ declare module 'stripe' {
2694
2296
  *
2695
2297
  * 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.
2696
2298
  *
2299
+ * 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.
2300
+ *
2697
2301
  * 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).
2698
2302
  */
2699
2303
  setup_future_usage?: 'none';
@@ -2705,6 +2309,8 @@ declare module 'stripe' {
2705
2309
  *
2706
2310
  * 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.
2707
2311
  *
2312
+ * 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.
2313
+ *
2708
2314
  * 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).
2709
2315
  */
2710
2316
  setup_future_usage?: 'none';
@@ -2725,6 +2331,8 @@ declare module 'stripe' {
2725
2331
  *
2726
2332
  * 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.
2727
2333
  *
2334
+ * 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.
2335
+ *
2728
2336
  * 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).
2729
2337
  */
2730
2338
  setup_future_usage?: UsBankAccount.SetupFutureUsage;
@@ -2739,8 +2347,6 @@ declare module 'stripe' {
2739
2347
  interface FinancialConnections {
2740
2348
  filters?: FinancialConnections.Filters;
2741
2349
 
2742
- manual_entry?: FinancialConnections.ManualEntry;
2743
-
2744
2350
  /**
2745
2351
  * The list of permissions to request. The `payment_method` permission must be included.
2746
2352
  */
@@ -2763,39 +2369,19 @@ declare module 'stripe' {
2763
2369
  * The account subcategories to use to filter for possible accounts to link. Valid subcategories are `checking` and `savings`.
2764
2370
  */
2765
2371
  account_subcategories?: Array<Filters.AccountSubcategory>;
2766
-
2767
- /**
2768
- * The institution to use to filter for possible accounts to link.
2769
- */
2770
- institution?: string;
2771
2372
  }
2772
2373
 
2773
2374
  namespace Filters {
2774
2375
  type AccountSubcategory = 'checking' | 'savings';
2775
2376
  }
2776
2377
 
2777
- interface ManualEntry {
2778
- /**
2779
- * Settings for configuring manual entry of account details.
2780
- */
2781
- mode?: ManualEntry.Mode;
2782
- }
2783
-
2784
- namespace ManualEntry {
2785
- type Mode = 'automatic' | 'custom';
2786
- }
2787
-
2788
2378
  type Permission =
2789
2379
  | 'balances'
2790
2380
  | 'ownership'
2791
2381
  | 'payment_method'
2792
2382
  | 'transactions';
2793
2383
 
2794
- type Prefetch =
2795
- | 'balances'
2796
- | 'inferred_balances'
2797
- | 'ownership'
2798
- | 'transactions';
2384
+ type Prefetch = 'balances' | 'ownership' | 'transactions';
2799
2385
  }
2800
2386
 
2801
2387
  interface MandateOptions {
@@ -2828,6 +2414,8 @@ declare module 'stripe' {
2828
2414
  *
2829
2415
  * 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.
2830
2416
  *
2417
+ * 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.
2418
+ *
2831
2419
  * 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).
2832
2420
  */
2833
2421
  setup_future_usage?: 'none';
@@ -2843,6 +2431,8 @@ declare module 'stripe' {
2843
2431
  *
2844
2432
  * 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.
2845
2433
  *
2434
+ * 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.
2435
+ *
2846
2436
  * 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).
2847
2437
  */
2848
2438
  setup_future_usage?: 'none';
@@ -2878,8 +2468,6 @@ declare module 'stripe' {
2878
2468
  }
2879
2469
  }
2880
2470
 
2881
- type SecretKeyConfirmation = 'optional' | 'required';
2882
-
2883
2471
  type SetupFutureUsage = 'off_session' | 'on_session';
2884
2472
 
2885
2473
  interface Shipping {