#Jasuno
1 messages ยท Page 1 of 1 (latest)
Hi there ๐ can you help me understand what part of that discussion you're referring to?
"Instead, you need to revise your payment intents to include future use setup:
setup_future_usage=off_session (or on_session)"
Hm, I don't think so. When working with Subscriptions you typically want to set up your payment method(s) before creating the Subscription, so that the Invoices created by the Subscription can be automatically paid by an existing Payment Method.
Interesting, at the moment i have the subscription to send invoince in case the customer wants to pay on a month by month basis manually, but i want to also give the option to a payment method as a recurring option. Imagine you phone bill, its technically a subscription, but you have the option to pay on an automatical recurring basis or on a month to month basis.
Oohh, gotcha, there may be an option to use setup_future_usage in that case, let me double check that.
The closest parameter I'm finding is this save_default_payment_method option available during Subscription creation:
https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings-save_default_payment_method
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
That may not work because we are not asking the user for a payment method until after the first invoice is sent, I guess ill have to setup a payment method first and then process the transaction
I would suggest testing that parameter using our test clocks to see exactly how it will behave.
https://stripe.com/docs/billing/testing/test-clocks
I don't have much hands on experience with that parameter directly, but the wording of its description makes think the associated functionality will trigger whenever a Subscription payment succeeds.
Yeah i'm already using test clocks thank you very much