birdy247 | Stripe Developers | Page 1

split burrowBOT Oct 7, 2022, 9:30 AM

#

prime stratus Oct 7, 2022, 9:30 AM

#

We seem to be making far too many API calls and its taking 5/6 seconds to prepare things

#

1/ create customer

#

2/ create subscription schedule

#

3/ Finalise the invoice

#

4/ Update the payment intent for off_session usage

#

4 Api calls just to get the necessary payment intent secret

#

Can this be optimised?

#

Hello?

upbeat fulcrum Oct 7, 2022, 9:36 AM

#

👋 Hi there, Happy to help!

prime stratus Oct 7, 2022, 9:36 AM

#

Can you see my messages above?

upbeat fulcrum Oct 7, 2022, 9:36 AM

#

yes I'm on it

prime stratus Oct 7, 2022, 9:38 AM

#

Thanks

upbeat fulcrum Oct 7, 2022, 9:39 AM

#

Why are you doing step 3 and 4?

#

I may suggest you to follow this guide on how to build subscription:
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
You can replace the subscription API creation call with a subscription _schedule API creation request

#

4 Api calls just to get the necessary payment intent secret
For example this step can be done at the same time while creating the subscritpion_schedule, by expanding the response latest_invoice.payment_intent, then you'll get the client secret directly

prime stratus Oct 7, 2022, 9:42 AM

#

I tried that

#

But the invoice had a null payment_intent

#

because it wasnt fianlised

#

This is a subscription schedule

#

On subscriptions, we can pass 'payment_behavior' => 'default_incomplete',

#

But it seems different on subscription schedules]

upbeat fulcrum Oct 7, 2022, 9:48 AM

#

You are right let me do some tests please

#

Thanks for your patience,
One of the option and if you pricing model allows it, at the beginning you can create a subscription (which reflect the first phase of your subscritpion_schedule) then asynchronously you create a subscritpion_schedule from the subscription, and then you do the necessary updates in order to get the target subscritpion_schedule
https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-from_subscription

#

or you can keep your first logic, and do those steps asynchronously if your UX design allows that: like you don't collect all the information of the customer, the subscription, the plan in a single large form, but you do it in a seperate forms. Then after each step you do asynchronously one of the calls in order to not let the user waits at the ends 5/6 sec

prime stratus Oct 7, 2022, 11:06 AM

#

Hi, sorry, just returning here

prime sparrow Oct 7, 2022, 11:18 AM

#

@prime stratus Did you have a Q?

spring sluice Oct 7, 2022, 11:44 AM

#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

#birdy247