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
@@ -2105,6 +2117,12 @@ class CreateParamsCapabilitiesSepaDebitPayments(TypedDict):
2105
2117
Passing true requests the capability for the account, if it is not already requested. A requested capability may not immediately become active. Any requirements to activate the capability are returned in the `requirements` arrays.
Passing true requests the capability for the account, if it is not already requested. A requested capability may not immediately become active. Any requirements to activate the capability are returned in the `requirements` arrays.
Copy file name to clipboardExpand all lines: stripe/api_resources/bank_account.py
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -358,9 +358,9 @@ class DeleteParams(RequestOptions):
358
358
"""
359
359
status: str
360
360
"""
361
-
For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn't enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a transfer sent to this bank account fails, we'll set the status to `errored` and will not continue to send transfers until the bank details are updated.
361
+
For bank accounts, possible values are `new`, `validated`, `verified`, `verification_failed`, or `errored`. A bank account that hasn't had any activity or validation performed is `new`. If Stripe can determine that the bank account exists, its status will be `validated`. Note that there often isn't enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be `verified`. If the verification failed for any reason, such as microdeposit failure, the status will be `verification_failed`. If a payout sent to this bank account fails, we'll set the status to `errored` and will not continue to send [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) until the bank details are updated.
362
362
363
-
For external accounts, possible values are `new`, `errored` and `verification_failed`. If a transfer fails, the status is set to `errored` and transfers are stopped until account details are updated. In India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.
363
+
For external accounts, possible values are `new`, `errored` and `verification_failed`. If a payouts fails, the status is set to `errored` and scheduled payouts are stopped until account details are updated. In India, if we can't [verify the owner of the bank account](https://support.stripe.com/questions/bank-account-ownership-verification), we'll set the status to `verification_failed`. Other validations aren't run against external accounts because they're only used for payouts. This means the other statuses don't apply.
Copy file name to clipboardExpand all lines: stripe/api_resources/card.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -153,7 +153,7 @@ class DeleteParams(RequestOptions):
153
153
"""
154
154
status: Optional[str]
155
155
"""
156
-
For external accounts, possible values are `new` and `errored`. If a transfer fails, the status is set to `errored` and transfers are stopped until account details are updated.
156
+
For external accounts that are cards, possible values are `new` and `errored`. If a payout fails, the status is set to `errored` and [scheduled payouts](https://stripe.com/docs/payouts#payout-schedule) are stopped until account details are updated.
Copy file name to clipboardExpand all lines: stripe/api_resources/checkout/session.py
+26-3Lines changed: 26 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -798,6 +798,9 @@ class Pix(StripeObject):
798
798
The number of seconds after which Pix payment will expire.
799
799
"""
800
800
801
+
classRevolutPay(StripeObject):
802
+
pass
803
+
801
804
classSepaDebit(StripeObject):
802
805
setup_future_usage: Optional[
803
806
Literal["none", "off_session", "on_session"]
@@ -886,6 +889,7 @@ class FinancialConnections(StripeObject):
886
889
p24: Optional[P24]
887
890
paynow: Optional[Paynow]
888
891
pix: Optional[Pix]
892
+
revolut_pay: Optional[RevolutPay]
889
893
sepa_debit: Optional[SepaDebit]
890
894
sofort: Optional[Sofort]
891
895
us_bank_account: Optional[UsBankAccount]
@@ -913,6 +917,7 @@ class FinancialConnections(StripeObject):
913
917
"p24": P24,
914
918
"paynow": Paynow,
915
919
"pix": Pix,
920
+
"revolut_pay": RevolutPay,
916
921
"sepa_debit": SepaDebit,
917
922
"sofort": Sofort,
918
923
"us_bank_account": UsBankAccount,
@@ -1427,10 +1432,10 @@ class CreateParams(RequestOptions):
1427
1432
"""
1428
1433
customer: NotRequired["str|None"]
1429
1434
"""
1430
-
ID of an existing Customer, if one exists. In `payment` mode, the customer's most recent card
1435
+
ID of an existing Customer, if one exists. In `payment` mode, the customer's most recently saved card
1431
1436
payment method will be used to prefill the email, name, card details, and billing address
1432
1437
on the Checkout page. In `subscription` mode, the customer's [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)
1433
-
will be used if it's a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.
1438
+
will be used if it's a card, otherwise the most recently saved card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.
1434
1439
1435
1440
If the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.
1436
1441
If the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.
@@ -1537,7 +1542,7 @@ class CreateParams(RequestOptions):
@@ -2346,6 +2357,18 @@ class CreateParamsPaymentMethodOptionsSepaDebit(TypedDict):
2346
2357
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).
Indicates that you intend to make future payments with this PaymentIntent's payment method.
2366
+
2367
+
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.
2368
+
2369
+
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).
Copy file name to clipboardExpand all lines: stripe/api_resources/customer.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -642,7 +642,7 @@ class ListPaymentMethodsParams(RequestOptions):
642
642
A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
An optional filter on the list, based on the object `type` field. Without the filter, the list includes all current and future payment method types. If your integration expects only one type of payment method in the response, make sure to provide a type value in the request.
0 commit comments