#Juggernaut-subscription-creation

1 messages · Page 1 of 1 (latest)

glossy parcel
grand solar
#

yes

#

Actually I'm familiar with subscription

#

but my client is in direct contact with some stripe support

#

and was suggested to use invoices

#

to send payment link via email to their customers

#

Now I'm struggling with creation of invoice of recurring prices

#

I'm using stripe APIs

glossy parcel
#

If you're working with a recurring model, then you'd need a subscription to automate the recurring payments/invoices. Otherwise you'd be handling that yourself

#

To be clear, you can create a subscription will a recurring price that will email the invoice (with a payment link) each billing cycle. As opposed to automated payments

grand solar
#

okay, so it goes something like this

create customer > create a plan > create a recurring price > create a subcription of customer with this price

#

this will automatically send a payment ??

glossy parcel
#

That's the general flow, yes. With a subscription you can set whether payment will be attempted automatically (via a saved payment method), or whether the invoice will be sent for payment

#

So depending on how you want your customers to pay for their recurring service, will impact how you build the integration

grand solar
#

okay.. the end goal is to automate the payment

#

it's just the first payment which is our concern

#

we do not wanna hold the card details

#

therefore this was what client thinking,,, that the invoice will first time collect card details and then later on will automatically charge customer

#

is it possible by any means?

glossy parcel
#

From there, you'd need to update the collection_method parameter on the Subscription object to automate future payments

#

Although this is a bit of an off piste integration. Why the reluctance to capture payment methods up front for the initial payment?

grand solar
#

because we won't be having the payment method in order to bind to the subscription

#

see, we have 2 plan system... where the user create a subcription with card details once... ( we've used checkout session method )

the second plan is a daily basis charge system.. but here taking the card details second times create a doubtful impact