#khorgnil
strange orbit
rapid cedar
Hello 👋
The minimum charge amount for USD is $0.50
https://stripe.com/docs/currencies#minimum-and-maximum-charge-amounts
Also, taking a step back
If you're charging $1.50 per minute, how is the payment process going to work exactly?
Would a customer going to go through Checkout sessions again and again to pay $x per minute?
Just trying to make sure I am on the same page 🙂
true skiff
The minimum charge is not a problem, @rapid cedar . My charges are usually in excess of $100.00. The problem is Stripe won't let me have a price that has more than two decimals (ie, 0.025).
Your step back question's a good one, I could have explained that better. It's similar to offline transcription. The user will upload a file, a duration will be calculated, and then a charge will be generated for that specific duration. For example, if the user uploads a file that is 42 minutes long, that 42*60=2,520 seconds. At $0.025 per second (or 1.50 per minute), the totasl charge will be $63.00.
My intention was to effectively "sell" the user 2,520 seconds. But that didn't work because the cost for a single "second" has more than 2 decimals.
rapid cedar
Are you creating the prices using price_data parameter?
Can you share a request ID for the checkout creation?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
true skiff
@rapid cedar the error message included a request_log_url attribute. Should I share that here? Is it safe to share that URL?
rapid cedar
Yeah its fine
rapid cedar
Hmm gotcha. Let me look around and see if there's a workaround for this
true skiff
Thanks!
Also, while you're looking around, I'll also let you know that the user could "purchase" multiple seperate transactions at once. I'd like to have each of them listed as line items on the checkout page.
For example, if File A is 12 minutes long that line item would be $18.00. If File B is 24 minutes, that line item would be $36.00. The grand total would be $54.00.
I could do this if I were creating a PaymentIntent - by simply calculating the charge for each line item, and only using the Stripe Price object as basically a lookup item to tell me how much to charge per second. But since I'm trying to use Checkout (in order to avoid having to implement my own UI), I am not using Payment Intent - right?
rapid cedar
I think this is a limitation with Checkout as of today. Don't think there's a workaround for this unfortunately.
I could do this if I were creating a PaymentIntent - by simply calculating the charge for each line item, and only using the Stripe Price object as basically a lookup item to tell me how much to charge per second. But since I'm trying to use Checkout (in order to avoid having to implement my own UI), I am not using Payment Intent - right?
Correct. With a PaymentIntent, you'd control everything.
true skiff
Understood, bummer.
OK, so then I guess my next question is what is the easiest way to get up and running with PaymentIntents? My frontend is an Angular app. Is that going to be to use Elements?