#hss-dev_api

1 messages ¡ Page 1 of 1 (latest)

shell stratusBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1319014287502737518

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

reef quest
#

Hello

#

When you say "Advertiser 1" "2" "3" ... are these separate Customers with separate Subscriptions?

warped dagger
#

Hi bismarck

#

yes, advertiser 1, 2, and 3 will have a recurring subscription to an advertising spot product

#

not sure if making the product $300 is the right thing to do, but in my mind represents the capped price that any one advertiser would have to pay at end of the month

reef quest
#

Gotcha, the easiest way to handle this in my opinion is to use a $1 Metered Price here and record usage up to 300 based on the amount you are going to charge.

#

To be clear, you want to post-bill here.

#

Like charge for usage over the course of the month, correct?

warped dagger
#

well, the way the advertising meter would work would be based on number of contacts that an advertiser would have based on ad (like a lead)

#

so, say advertiser had 500 leads through my application and another had 250 leads, I would standardize their usage like 250/750 x 300 = invoice at end of month for advertiser 2.

#

yes, I think post bill is most appropriate

#

I don't want to charge upfront and mess with credits

reef quest
#

Okay yeah overall if you are going to post-bill then you are going to have to track this yourself and then just apply the correct usage to the Meter in order to charge that Customer.

warped dagger
#

okay

reef quest
#

There isn't really any other Pricing model within Stripe that handles something dynamic like this with post-billing.

warped dagger
#

so, what would be the price of product for something like this?

reef quest
#

Likely it would be $1 per quantity

warped dagger
#

do I specify $300 for ad spot, each advertiser has recurring subscription on this, with exact bill calculated in invoice

#

yes, but $1 for each lead doesn't make sense

reef quest
#

No it is just $1 so you can record usage for the correct amount.

#

That's necessary if you are saying the end result can be any sort of split.

#

And it is in unknown increments up front.

warped dagger
#

oh

reef quest
#

If there are specific increments for the split then you can use that as the base $ amount

warped dagger
#

so, performing the % of total number of lead from ad as metered event in invoice would be way to go

reef quest
#

Yeah that's the only way I can think of to accomplish what you are looking for really

warped dagger
#

alright, and the $1 price of the product. would there be way to describe this upfront in product what invoice would be at end of month for each advertiser based on said capped price for each ad spot product. would there be an appropriate place in product to describe how invoice would happen or include the $300 capped price?

reef quest
#

I'm not sure what you mean by that, sorry.

#

Can you maybe rephrase or give me a specific example of what you mean?

warped dagger
#

sure

#

in the product, you said make price $1 because we don't know end of month bill for any advertiser subscriber. However, is there a place in product or subscription where I could explain that the ad spot would at most cost $300 at the end of the month say for 100% of leads or explain the standardization of usage like leads_for_advertiser/total_leads_for_all_advertisers x 300 = invoice at end of month for any one advertiser

reef quest
#

This will appear on the line item on the Invoice

warped dagger
#

you are referring to the description key on the product json object

#

{
"id": "prod_NWjs8kKbJWmuuc",
"object": "product",
"active": true,
"created": 1678833149,
"default_price": null,
"description": null,
"images": [],
"marketing_features": [],
"livemode": false,
"metadata": {},
"name": "Gold Plan",
"package_dimensions": null,
"shippable": null,
"statement_descriptor": null,
"tax_code": null,
"unit_label": null,
"updated": 1678833149,
"url": null
}

reef quest
#

Yes

warped dagger
#

what would this look like to customer on product page, do you have example of this on a screen?

#

sorry, I am just starting out with Stripe but feel I am best served by just asking

reef quest
#

No I don't have an example handy. Best thing to do at this point is test this stuff out in test mode so you can see exactly what it looks like.

warped dagger
#

alright

reef quest
warped dagger
#

I noticed I am in test mode now, which is what I am needing b/c I am developing the application right now. I'll look into Test Clocks more. Thank you.

reef quest
#

Sure thing

warped dagger
#

last thing. just to confirm, this would be a usage-based billing product

#

@reef quest , can you confirm my last question before I leave. I really appreciate your time and expertise today.