You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update generated code for v2324 and 2bacf30ea7a096640a42760f6973fee486bcf126
* Update generated code for v2324 and 3b7d6e3c02976c878032d9849a9dd7211d35cb97
---------
Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
Co-authored-by: David Brownman <xavdid@stripe.com>
* Returns a list of transactions that have contributed to the Stripe account balance (e.g., charges, transfers, and so forth). The transactions are returned in sorted order, with the most recent transactions appearing first.
10
+
* Returns a list of transactions that have contributed to the Stripe account balance (for example, charges, transfers, and so on). The transactions return in sorted order, with the most recent transactions appearing first.
11
11
*
12
-
* Note that this endpoint was previously called “Balance history” and used the path /v1/balance/history.
12
+
* The previous name of this endpoint was “Balance history,” and it used the path /v1/balance/history.
Copy file name to clipboardExpand all lines: src/resources/Billing/CreditBalanceSummary.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -156,7 +156,7 @@ export namespace Billing {
156
156
price_type?: 'metered';
157
157
158
158
/**
159
-
* A list of prices that the credit grant can apply to. We currently only support the `metered` prices. Cannot be used in combination with `price_type`.
159
+
* A list of prices that the credit grant can apply to. We currently only support the `metered` prices. Cannot be used in combination with `price_type`. Limit 20 prices.
* The priority for applying this credit grant. The highest priority is 0 and the lowest is 100.
169
169
*/
170
-
priority?: number|null;
170
+
priority: number|null;
171
171
172
172
/**
173
173
* ID of the test clock this credit grant belongs to.
@@ -342,7 +342,7 @@ export namespace Billing {
342
342
price_type?: 'metered';
343
343
344
344
/**
345
-
* A list of prices that the credit grant can apply to. We currently only support the `metered` prices. Cannot be used in combination with `price_type`.
345
+
* A list of prices that the credit grant can apply to. We currently only support the `metered` prices. Cannot be used in combination with `price_type`. Limit 20 prices.
Copy file name to clipboardExpand all lines: src/resources/Charges.ts
+17Lines changed: 17 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -947,6 +947,11 @@ export namespace Charge {
947
947
}
948
948
949
949
exportinterfaceBizum{
950
+
/**
951
+
* A unique identifier for the buyer as determined by the local payment processor.
952
+
*/
953
+
buyer_id: string|null;
954
+
950
955
/**
951
956
* The Bizum transaction ID associated with this payment.
952
957
*/
@@ -1090,6 +1095,11 @@ export namespace Charge {
1090
1095
*/
1091
1096
three_d_secure: Card.ThreeDSecure|null;
1092
1097
1098
+
/**
1099
+
* Transaction Link ID (TLID) is a unique identifier for a transaction. This is used by some card networks, such as Mastercard, for transaction linking, in addition to Network Transaction IDs. This value will be present if it is returned by the financial network in the authorization response, and null otherwise.
1100
+
*/
1101
+
transaction_link_id: string|null;
1102
+
1093
1103
/**
1094
1104
* If this Card is part of a card wallet, this contains the details of the card wallet.
1095
1105
*/
@@ -1744,6 +1754,11 @@ export namespace Charge {
1744
1754
*/
1745
1755
bank_transaction_id?: string|null;
1746
1756
1757
+
/**
1758
+
* Uniquely identifies this particular Pix account. You can use this attribute to check whether two Pix accounts are the same.
1759
+
*/
1760
+
fingerprint?: string|null;
1761
+
1747
1762
/**
1748
1763
* ID of the multi use Mandate generated by the PaymentIntent
* Controls when the funds will be captured from the customer's account.
2742
+
*/
2743
+
capture_method?: 'manual';
2744
+
2745
+
/**
2746
+
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
2747
+
*
2748
+
* If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.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://docs.stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2749
+
*
2750
+
* If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2751
+
*
2752
+
* When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication).
2753
+
*/
2754
+
setup_future_usage?: 'none';
2755
+
}
2756
+
2735
2757
exportinterfaceSwish{
2736
2758
/**
2737
2759
* The order reference that will be displayed to customers in the Swish application. Defaults to the `id` of the Payment Intent.
* The app ID registered with WeChat Pay. Only required when client is iOS or Android.
2820
+
*/
2821
+
app_id: string|null;
2822
+
2823
+
/**
2824
+
* The client type that the end customer will pay from
2825
+
*/
2826
+
client: WechatPay.Client|null;
2827
+
2828
+
/**
2829
+
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
2830
+
*
2831
+
* If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.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://docs.stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
2832
+
*
2833
+
* If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
2834
+
*
2835
+
* When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication).
2836
+
*/
2837
+
setup_future_usage?: 'none';
2838
+
}
2839
+
2795
2840
exportnamespaceAcssDebit{
2796
2841
exporttypeCurrency='cad'|'usd';
2797
2842
@@ -3187,6 +3232,10 @@ export namespace Session {
3187
3232
}
3188
3233
}
3189
3234
}
3235
+
3236
+
exportnamespaceWechatPay{
3237
+
exporttypeClient='android'|'ios'|'web';
3238
+
}
3190
3239
}
3191
3240
3192
3241
exportnamespacePermissions{
@@ -3757,8 +3806,6 @@ export namespace Checkout {
3757
3806
* You can configure Checkout to collect your customers' business names, individual names, or both. Each name field can be either required or optional.
3758
3807
*
3759
3808
* If a [Customer](https://docs.stripe.com/api/customers) is created or provided, the names can be saved to the Customer object as well.
3760
-
*
3761
-
* You can't set this parameter if `ui_mode` is `custom`.
* Controls when the funds will be captured from the customer's account.
6185
+
*/
6186
+
capture_method?: 'manual';
6187
+
6188
+
/**
6189
+
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
6190
+
*
6191
+
* If you provide a Customer with the PaymentIntent, you can use this parameter to [attach the payment method](https://docs.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://docs.stripe.com/api/payment_methods/attach) the payment method to a Customer after the transaction completes.
6192
+
*
6193
+
* If the payment method is `card_present` and isn't a digital wallet, Stripe creates and attaches a [generated_card](https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-card_present-generated_card) payment method representing the card to the Customer instead.
6194
+
*
6195
+
* When processing card payments, Stripe uses `setup_future_usage` to help you comply with regional legislation and network rules, such as [SCA](https://docs.stripe.com/strong-customer-authentication).
6196
+
*/
6197
+
setup_future_usage?: 'none';
6198
+
}
6199
+
6125
6200
exportinterfaceSwish{
6126
6201
/**
6127
6202
* The order reference that will be displayed to customers in the Swish application. Defaults to the `id` of the Payment Intent.
0 commit comments