#frijolay
torpid comet
rotund sundial
thank you. going thru the docs, i came to the same understanding but i just wanted to verify.
just a follow up... where im coming from is that i have an app where I want to allow users to share reusable payment link. initially i figured i could just generate a reusable payment link. but i learned that there are consequences to this when the user updates/changes their automatic tax support. if that changes for the user, then my understanding is that the payment link would need to be updated...
that lead me down to the idea that i have a link that i control, but when its accessed i generate a new PL that has its current tax config for that user
i know it sounds hacky
but i was wondering if there was a better approach
main slate
If you have any automatic use case, it's better to use Stripe Checkout. Payment Links are mostly for no-code users.
In your case it's best to instead generate a link to your own app and share it with your customers, and when cusomers click on the link, your app will generate a fresh Checkout Session URL that would have all the configs that you need.
rotund sundial
got it. thank you!
main slate
Happy to help.