#ibgoldbergs

1 messages · Page 1 of 1 (latest)

fleet ironBOT
river sentinel
#

Just reading through your flow.

#

My first thought would be to create the Customer first, then use a Setup Intent to both collect Payment Method details and attach the PM to the Customer in one API request.

#

Oh wait.

#

Actually I think you can do it all when creating the subscription.

stark ridge
#

You can?

#

by all, what are you referring to?

river sentinel
#

Sorry, not all

stark ridge
#

so this would just remove one step (setting paymentMethodId as default for customer)

sly citrus
#

👋

#

Stepping in as Snufkin needs to step away

#

Yes

#

You can set the default payment method via the above setting when you create the Sub

#

So you don't have to do that extra step

stark ridge
#

Can we add billing details to the paymentMethod at the same time as creating the subscription as well?

sly citrus
#

You add billing details to the PaymentMethod when you collect the PaymentMethod

#

What integration are you using?

#

Sounds like Card Element potentially?

stark ridge
#

Yes the card element

#

Trying to figure out how to make our endpoint much faster/optimized

sly citrus
stark ridge
#

got it, makes sense

#

i think we can cut our requests by half

#

thanks for the help

sly citrus
#

Sure thing

stark ridge
#

Is a paymentMethod attached to a customer automatically if you create a subscription with a payment method?

#

or do we need to separately attach the paymentMethod to the customer prior to creating the subscription?