#NovaJay2415

1 messages · Page 1 of 1 (latest)

vital girderBOT
pallid crag
#

Hello, those things are possible but Stripe's API would basically be just the one-time or recurring payment components of that. We do offer a customer portal but it does not have built in functionality that exactly lines up with switching between plans as you describe

#

I am gathering docs that will be relevant here... Will get back to you shortly

delicate flame
#

Thank you. But all the information I would need to display in the user's account could be shown from Stripe right?

#

Like the invoices, the reoccurring payment details from Stripe?

#

Also, thank you!

pallid crag
delicate flame
#

I am happy to get any and all info I can get! Thank you!

pallid crag
#

But the Customer Portal unfortunately cannot create new subscriptions. You would need to create the Subscription directly server-side or have your user go through another Checkout Session

#

Have you checked in to our surfaces for taking payments? Have you decided if you want to use our hosted Checkout pages or write your own Custom page, use our mobile SDKs, etc?

delicate flame
#

We are going to handle it through Custom pages. We want to stay PCI compliant at all costs. I am just having trouble finding the docs that talk about creating custom pages. I find the "low code" or "no code" but I really want the docs explaining how to use the API to connect to our website and help us to create our custom flow.

pallid crag
#

Switching between them dynamically might be a bit tricky. Trying to think of how may be best to do that

#

Oh I guess you could always create a subscription and just cancel it after the first payment for a one-time payment. Though that may send confusing emails to your customers.

delicate flame
#

Would it be better to just have two sperate pages on the user account? Where they could put in a one time payment on one page.. or put in reoccurring on a separate page?

#

Also, thank you for the docs! I am going to start there and I will come back when I have questions.

#

Appreciate your help.

pallid crag
#

That would definitely be a viable way to implement that. You could theoretically have this all happen on one page but you would need logic to re-render the payment element if the user switches between one-time and recurring. That might not be too difficult to implement but I don't think we have specific. I can try to find docs that would be relevant for that flow if you are interested in making this a one page thing

delicate flame
#

Yes, I am interested in the one page thing, if it is possible. I would love to see docs on that.

vital girderBOT
pallid crag
#

And if the user says they want their payment to be recurring, you can schedule a subscription to start when that next payment should take place

delicate flame
#

That makes perfect sense!

#

Thank you so so much! I am going to take a look at all this. Appreciate it, Pompey.