#cecile-checkout

1 messages · Page 1 of 1 (latest)

manic skiff
#

not it's not possible

#

can you clarify a little why you want to remove it so I can make sure the use case/feedback can be taken into account?

radiant oar
#

I want to remove it beacause customers are perturbed by this information. This product is only 43.9 the first month, then the price change to 18.9 the next 5 months and then 9.9 by month (it's written in the description bellow but the vendor is afraid customers will think they're goind to pays 43.9 by month).
The change of price is applied after the payment with a webhook on the invoice.paid event. Because there was no way to create directly the price with this specification from the create-cherckout-session.

manic skiff
#

so you mean you are using SubscriptionSchedules after the CheckoutSession to set up a more custom recurring pricing over the future months?

radiant oar
#

I'm updating the subscription price.
I thought the SubscriptionSchedules were not usable with checkout session?

manic skiff
#

they are not

#

but I mean you could use one after the CheckoutSession, but either way, it's the same thing.
I was curious how you do this "the price changes after 5 months", do you just manually call the API to change the price by counting webhooks?

#

but it has the same problem(the Checkout page doesn't know about the Schedule so it will say 43.90 per month), so it doesn't help that specific part of your query, just mentioning it

radiant oar
#

I record payments in my database and change the price or stop the subscription according to the data of the products and the number of payment recorded. I find about schedule after implemented my solution.

#

But it's true that's doens't change my problem. So I guess I would have to create manually my payment form?

manic skiff
#

yes, the only option if this is a real problem for you would be to build your own entirely custom payment form where you can present the information directly the customer in the way you want

#

it's a trade-off between the amount of work that is, versus how much of a problem this is for you, it's probably a lot easier to go with Checkout for now

radiant oar
#

Yes I suppose it is.
But I'm afraid my client really want to remove that information...
And more, I'm really new on Stripe dev and the cehckout API is really easy and well documented but I don't know where to start to do it manually...
From here : https://stripe.com/docs/payments/quickstart ?
And then, is the webhook the same with different events?

Custom payment flow
manic skiff
#

but I would suggest using Checkout and finding some other solution, since as you say, Checkout is a much much better and easier option and should always be used by default if you can

radiant oar
#

Thanks a lot for your time a precious advices, I'll try to convince my client...

#

Is there a way to create a subcription after a onetime payment through the webhook and then make the subscriptionscedulte directly after the first payment. Then my checkout form will only be for onetime payment and the subscription will be created after this one?

manic skiff
#

you can do that yes (you can call the create Subscription API when handling the checkout.session.completed event and start a Subscription for the customer). Make sure you use a trial period though, since you have to skip the first payment to avoid double charging the customer

#

not sure I'd recommend it — the Checkout page will not show the customer they are signing up for a subscription, which would surely also confuse/perturb them.