#gracine-subscription-schedule
ruby field
lyric axle
There is a subscription_data hash to set things on if you are creating a subscription with Checkout https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-subscription_data
Can you clarify a bit what you are trying to do? What are you trying to set via payment_intent_data?
dire juniper
Ok, my use case is that we will charge a relatively high amount of money for a professional plan which allows you to be listed on a curated directory for professional services
Upon subscription, our process is to validate each profile on different criteria and if they pass we will charge them from the Stripe Portal
And the subscription is yearly
So I wanted to let them subscribe in stripe on the given product but not charge them right away
Let our internal team validate, them charge in stripe, which will trigger our webhook and update their subscription status
lyric axle
Gotcha. So I assume you are starting with a $0 per year price, and updating the subscription afterwards to add things for the profiles?
dire juniper
all users start free (do stripe subscription at all), them opt-in for this professional plan if they want
*(no stripe subscription at all)
my goal is to avoid the most friction possible for the user
lyric axle
Gotcha. And do you know how to do what you were aiming for with the payment_intent_data parameters now?
dire juniper
No i get an API error when specifying capture_method: 'manual'
and I don't understand which param I should use in the subscription_data hash that you mentionned at the beginning
I want the concept of pre-auth, like we do at the gaz station when you swipe your credit card before putting gaz
lyric axle
Unfortunately subscriptions don't support separate auth and capture. You would need to make multiple separate payment intents to do that
dire juniper
So I would need implement the scheduling mechanism that will invoice my customer each year
lyric axle
Yes, in that case the scheduling would be on your side