#fen_god
twilit dockBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- fen-paymentlink-paymentintent, 10 minutes ago, 6 messages
- fen-paymentlink-pricedata, 20 hours ago, 20 messages
- fen_god, 1 day ago, 10 messages
rigid quarry
Hello! Not sure what you mean by "using the payment link object"? Do you mean you have the ID of a Payment Link and now you want to see all the Checkout Sessions associated with it?
echo widget
yes exactly
rigid quarry
Yeah, you can list Checkout Sessions by Payment Link: https://stripe.com/docs/api/checkout/sessions/list#list_checkout_sessions-payment_link
echo widget
thankyou, this is what i wanted. So it's assumed that the external system integrating with Payment Links should deactivate the payment link once the total amount has been paid? I'm wondering if stripe has any 'out of the bx' handling for this?
rigid quarry
What do you mean by "the total amount"?
A Payment Link is designed to be reused by multiple people many, many times.
echo widget
So this feature wouldn't be recommended if i just wanted to use it for a single payment?
rigid quarry
Not generally, no. We do have an option to limit the number of Checkout Sessions that can be completed via a Payment Link, so I guess you could set this to 1, but that would be an atypical use case: https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-restrictions-completed_sessions-limit
What is your use case?
echo widget
Ok useful to know.
So for example, A customer wishes to pay for a have an order. The customer will receive an email which contains a url to direct them to a payment form. Once the payment has been received, our system can mark the order as paid and no further actions can be made to the order.
rigid quarry
Are you trying to do this with no code?
Typically what we recommend in a scenario like this is to have the link in the email point to your server, then when the link is visited your server can check to see if that order has been paid yet or not. If it has, you display an "already paid" message. If it hasn't, you create a Checkout Session and redirect your customer to that Checkout Session's URL. This approach requires you to have a server and run code on it though.
echo widget
Are you trying to do this with no code?
No this is not a no code solution
rigid quarry
Okay, so I would recommend the Checkout Sessions approach described above which does not involve Payment Links at all.
echo widget
I think we will go down the path of using the limiting property because we dont want to self host the payment form
rigid quarry
You don't have to self-host the payment form.
You need to self-host the link in the email, but that can automatically redirect to the Stripe-hosted payment form when payment is required.
The actual payment experience would be the same either way; both approaches use Stripe Checkout.