pedromcr

[jaunty junco]

hello, hitting the API isn't going to be a problem unless you're expecting 50+ appointment payment page creations each second

so I don't really see a problem unless you're seeing yourself hit the rate limit threshold

[keen bolt]

Ok great, I was afraid of being rate limited at some point. Then would this be acceptable:

1. Doctor schedules appointment naming any price
2. My backend calls the Stripe API to find a price in that product which has that exact amount
   2.a) Finds such a price, uses it to generate the payment link
   2.b) Doesn't find such a price -> Create a new price with said amount and use it to generate the payment link

Thanks for such a quick reply btw

[jaunty junco]

happy to reply quickly

also you can also use Stripe Checkout (which is the same page as Payment Links really) except that you can create a Price in-line with the price_data parameter, so you skip the look up of step 2

and the extra Price creation step of 2b. The only side effect is that you're left with extra duplicate Prices which can be fine, you can just ignore them

[keen bolt]

Oh, I didn't realize I could use the checkout page for my use-case. I'll look into it. Thanks and have a great weekend!