#env

1 messages ยท Page 1 of 1 (latest)

twin briarBOT
visual torrent
#

Hi ๐Ÿ‘‹

That's both a lot of explanation and still not enough to get a clear picture. So let's start with some simple descriptions here.

nova rose
#

sure ๐Ÿ‘

visual torrent
#

Okay so the tiered plans make sense. Would you want to model these as separate products?

nova rose
#

from what I read in the docs (the t-shirt example), separate products probably make sense

#

what other options would there be?

visual torrent
#

Well we do allow you to create multiple prices for a single product. This allows you to do things like upsell to subscriptions with longer billing cycles.

nova rose
#

ah, right. we could already use that for the discount based on the subscription length, right?

visual torrent
#

Yes you can

nova rose
#

sounds good. how would we implement the additional features (X,Y,Z) and the validation checks?

visual torrent
#

Okay that's the bit I'm confused about. What are these validation checks for and how would they work?

nova rose
#

we have the base modules (A,B,C), right? they are important for different areas of business and different businesses will probably need different modules (business 1 might need A and C, business 2 might only need B). we need a pre-checkout check to see if the customer has at least one of these modules in his cart, as it does not make any sense not to have one of these but still get access to our app.

visual torrent
#

Okay, that level of checking is something you would need to store/perform in your integration. Like a database table that maps the base modules to specific Product IDs in Stripe.

nova rose
#

ok, so my understanding of the workflow is the following:

  1. we have a custom store implementation in the frontend which checks the validity of the configured package.
  2. if fine, the request gets sent to our backend and also validates the configured package
  3. if also fine, our backend calls the stripe api with the products the customer selected
  4. our backend reports back to the frontend (+customer) that everythings fine
  5. our backend reacts to some webhooks, if needed for post - transaction actions
visual torrent
#

How are you collecting payment information from your Customers. Is that already saved to the Customer object?

nova rose
#

currently, not at all, we are still in the brainstorming phase ๐Ÿ˜… i guess we would go with the default?

visual torrent
#

Just to be clear, when you make the call to the stripe API are you creating a Subscription or and Invoice?

nova rose
#

are subscriptions just recurring invoices?

#

for testing i used subscriptions so far, and the whole service is subscription-based

visual torrent
#

Subscriptions are how Stripe handles recurring charges

#

If you have specific questions about a section in this or other docs I will be happy to help

#

But it will help both of us quite a lot if you familiarize yourself with the overall process

nova rose
#

sounds good, but the overall workflow should be the same, no?

#

for the package configuration process of the customer?

#

ah, i see, the examples look pretty nice ๐Ÿ‘Œ

#

ok, i'll have a look at the docs first if you sense a lot of missing knowledge which would point me in the right direction by going through the overview you sent me

visual torrent
#

The overview is going to follow the most common integration. There are more Subscription docs you can see in the navigation sidebar that may get closer to your particular use case

nova rose
#

ok, i'll try that first. if i have questions afterwards, should i ask a new question in the #dev-help channel or continue our conversation here?

visual torrent
#

We archive threads after a period inactivity. If this thread is still open you can ask here but if not you are welcome to ask in the #dev-help channel

nova rose
#

sounds good, thanks for your help!