#selby14 - Product
obtuse pasture
We are moving to use Checkout for all of our products, but we have one case where we need to make re-bill the customer once they hit a limit of use. When this happens we do an API call using a paymentIntent to charge the client behind the scenes. I have not been able to find a way to use our existing Stripe productId or PriceId to use for this charge and am currently just sending the amount and a description.
Or is there a different way to handle this api call instead of using a paymentIntent?
vague egret
Yeah, Payment Intents are one of the more basic Stripe objects.
So we don't have support for passing Price ID or Product ID. What is the context where you need to make this additional charge? Could you re-use the Checkout page or do you not want to bring the Customer back on-session?
obtuse pasture
This is a case where the customer may not be online or logged in at the time of charging. It's a sms text usage charge, and when their balance gets to a certain point, we re-bill them. It's a notification text, so could happen when the user is away from our app.
vague egret
That makes sense. Would I be correct in assuming you configured the Payment Method to be saved for future use?
obtuse pasture
yes
plus the first time the sign up for the notifications, it is through the checkout
vague egret
Okay. So in this case I think the Payment Intent approach using the amount and description fields is likely the best approach.
obtuse pasture
Thanks. We may need to alter how we re-charge those accounts, but wanted to be sure I just wasn't missing something.
vague egret
You could perhaps create an Invoice which supports using Price and Product IDs and use the Customer and Payment Method to pay for it. But Invoices are a bit more complex than Payment Intents so that may not be worth it.