#ripitried-paymentlink-event

1 messages · Page 1 of 1 (latest)

finite muskBOT
supple depot
#

Hi, what do you mean with 'Is there any way for me to pass in a custom parameter into the redirect url so that I can tell which form submission is related to a completed stripe payment'? Can you add more clarity?

cedar vortex
#

Yeah, so if i use stripe to host a checkout session for subscription payment it has a url right

#

can I pass an argument into that url somehow so that when I monitor the webhook associated with checkout I can recieve that parameter

#

does that make sense or should I explain further

supple depot
cedar vortex
#

im not generating a checkout session via API

#

Like I just have a single saas subscription I am linking to from a form and wanted to see if the checkout url supports passing in a param so I can link a form submission id with a payment

supple depot
#

How are you creatin gthe Checkout Session then? Are you using Payment Links from the Dashboard?

cedar vortex
#

Yeah I am just creating links from the dashboard

supple depot
cedar vortex
#

So can I just add my own custom params and they will get passed through to the checkout session event?

supple depot
cedar vortex
#

Yes I understand, I have read the docs

#

However, I am asking if this can be dynamic

#

for each form that gets filled out, I am not manually going to create a link

#

and does that extend for any parameters not named client reference id?

supple depot
#

There is not, and no.

cedar vortex
#

so how does the client reference id even work then?

#

because in the dashboard you don't specifically enable a link, the tool that shows up is just a link formatting tool

#

Additionally, what is the right event to monitor for if I am using a payment link for a subscription

supple depot
finite muskBOT
supple depot
#

Please reach out there

cedar vortex
#

okay can you handle the developer question though?

#

which is "what is the right event to monitor for if I am using a payment link for a subscription"

visual sinew
#

ripitried-paymentlink-event

cedar vortex
#

thanks, what do you mean by in the future?

visual sinew
#

Subscriptions are for recurring payments, the checkout.session.completed Event is only for the first payment happening through Checkout

cedar vortex
#

So you mean the first time someone pays for a subscription they will trigger a checkout session completed event

#

then for subsequent payments what event is triggered so I can monitor if they are still subscribed?

visual sinew
#

the second link I gave you above

cedar vortex
#

thats a list of a bunch of events

visual sinew
#

Yes, which a clear explanation about each that you can use

cedar vortex
#

my bad

#

would subscription_schedule.completed be the right event to monitor that confirms that a given subscription has cleared its next payment cycle?

#

after the initial checkout.session.completed *

visual sinew
#

no it wouldn't, that Event is about SubscriptionSchedules which is a separate API. Sorry you're going a bit too fast skimming the doc. Carefully read it end to end, and then try the product in Test mode, look at the relevant Events, look at our https://stripe.com/docs/billing/testing/test-clocks feature that lets you advance time to simulate future months, etc.

cedar vortex
#

Sure, I will but can you not just tell me which event is recommended to monitor to denote that a subscription has cleared its next monthly payment?

visual sinew
#

It's right there in that doc, sorry but it is important that you take a few minutes to read and try, we're helping a lot of other developers here and it should take you 2 minutes to look at each event and narrow it down

cedar vortex
#

Okay I read through the docs, I would need to monitor invoice.payment_succeeded for all subsequent succesful payments

visual sinew
#

that's the one Event that does not exist on that doc, so no

#

You should listen to invoice.paid

cedar vortex
#

my b mistyped

#

yeah, sounds good appreciate it

visual sinew
#

sure thing! Definitely a ton of Events, but Subscriptions go through a lot of state changes over time so you'll want to handle more than this one