#echelon-startup

1 messages · Page 1 of 1 (latest)

worthy zephyr
#

Hi there 👋 starting a thread for this, and will leave comments on various pieces below.

#

Are you planning on allowing for the creation of subscription-like flows where your users/customers are billed at a certain frequency, or are you focusing on accepting one-time payments?

boreal fractal
#

Workloads would be paid for up front, but we may have a priority queuing system that is a subscription product. Subscribe and your workloads get queue priority.

#

So to directly answer your question, billed upfront as a one-time payment.

worthy zephyr
#

Gotcha, for that, this guide would be a great starting point. It walks through the process of collecting a one-time Payment, and shows you different paths of how you could do that.
https://stripe.com/docs/payments/accept-a-payment

The Prebuilt Checkout page flow uses our Checkout Sessions, and it would have the benefit of using our Price objects where you could structure your prices inside of Stripe rather than needing to calculate them on your end.
For the pricing structure that you described, I think one of our tiered pricing models would be a good fit:
https://stripe.com/docs/products-prices/pricing-models#tiered-pricing

#

Our system does have the concept of customer credits/balances, but those are in currencies and don't allow custom units so I don't think they'd be a good fit for your credits and would recommend you handle those on your end.

boreal fractal
worthy zephyr
#

Happy to help! I know there is a lot of info to go through, but we're happy to help you parse it and decide on the best technical structure for your project. Feel free to ask any clarifying questions.

boreal fractal
#

Will do. Thank you again!