#Rob.Clayton

1 messages · Page 1 of 1 (latest)

sudden marshBOT
honest halo
#

Hi, what do you mean by the 'no code portal'?

hallow lion
#

I understand there is the customer portal, Stripe Checkout, Elements ... trying to workout what would be best for us, and if I've understood the options correctly

honest halo
#

Customer portal is used after a customer has a subscription, not before. I'm typing up a more comprehensive answer on my recommendation here.

hallow lion
#

Thank you very much

honest halo
#

So given that Customer portal is used for customers who have already subscribed, you'd want to use either Checkout or Payment Elements. It's up to you. Checkout would require lower bandwidth: https://stripe.com/docs/billing/quickstart.

Here is the resource for Payment Element: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements

Once your customers have subscribed, your customers can update their subscription/ manage other subscription related actions using the Customer Portal: https://stripe.com/docs/no-code/customer-portal

hallow lion
#

Does this support the following scenario, sir/madam:
A customer has no subscription:

They can purchase tier 1 or 2 or 3

ONCE they have purchased a tier they can:

Upgrade ORRR they can purchase a data pack (any number) ... but the data pack has a varying cost depending on if they are in tier 1 or two or 3.
We don't care if that's three data pack products, or whatever, but that is the scenario we have to support.

Can we do that with checkout. I'm a bit confused as to what checkout is.

Elements means we put components on the frontend, and write backend code to populate them, right?

honest halo
#

Stripe Checkout is just a prebuilt Checkout Page: https://stripe.com/docs/billing/quickstart

Once they subscribe, you can then use the customer portal. The Checkout is to help with the initial subscription creation.

hallow lion
#

Understood ... but can either of these support the requirements I outlined? I know elements can, but that takes the most code.
We need to only show 1 data pack product at a time depending on their subscribed tier.

honest halo
#

Yeah, you'd pass the price for that 1 data pack product, https://stripe.com/docs/products-prices/how-products-and-prices-work on Checkout in Subscription mode. I recommend that you read through the document thoroughly. From my understanding, you want to initially show 1 price. Then after the user is subscribed, you want them to have the option to upgrade/ downgrade the tier.

#

Let me know if I misunderstood your ask here

hallow lion
#

They would be offered all 3 possible "tier" subscriptions and no data packs when they first subscribe.
They would also be offered a separate single subscription which is a number of licenses (fixed cost per seat, easy one there)

Once subscribed they can upgrade the tier subscription, increase the license count and then purchase the data pack that is aligned with their tier (they are cheaper the higher the tier)

#

I've read the pricing rrrreasonably well (link you shared) ... but what I'm not sure about is implementing what we are proposing here, where there are effectively some workflow rules.
How much code do we need to write to support the process? When does it reach the poitn we need elements rather than checkout followed by customer portal?

honest halo
#

So you can embed the Pricing Tables, then use Checkout to create the subscription. Then, use the customer portal.

hallow lion
#

So the pricing table is for initial subscription only?

#

then customer portal upgrade their subscription?

honest halo
#

Yeap!

#

I'd look at that last document I provided in depth to make sure that it fully covers what you need

hallow lion
#

okay, and if that DOESN'T support what we want ... I assume we look at elements and backend coding?