paghkman

[exotic jolt]

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.

• paghkman, 16 hours ago, 12 messages
• xpaghkman-customer-email, 1 day ago, 31 messages

[scarlet panther]

return url for that scenario

Recommend testing this out yourself in test mode

[gray ice]

I see, another questions is

return_url: ${YOUR_DOMAIN}/return?session_id={CHECKOUT_SESSION_ID}

For this return url template, is there a way to also use something like this {STATUS}, failed or successfull directly from url params ?

[scarlet panther]

No you'd need logic to retrieve that yourself

But you wouldn't want to rely on customer reaching return url

That's what webhooks are for

Browser crashes, network issues, etc can mean customer won't always reach return url

[gray ice]

I know, since we are using revenuecat together with stripe, we are not using stripes API directly. And we basically call and query for subscription status directly on revenuecat side.

But I guess, it is okay to handle this case quickly to give user correct status