#V Buck Bandit
1 messages · Page 1 of 1 (latest)
hello! I'm afraid I don't quite understand, can you illustrate with an example?
hi, when im upgrading a users subscription with stripe, im subscribing them to the premium plus plan
but when the webhook is returns the update, the subscription is stored in the database under the name default
i am using laravel spark with stripe also
im not sure if this helps
is there a way, instead of it saving under the name column as default
to save it as eg. premium, premium plus
purely for conditionally rendering in my vuejs for a users active subscription
which parameter are you pulling from the webhook event to save as the name?
i haven't updated any configuration from the webhook
when subscribing to a new subscription level
this is the default behaviour
is it something that i need to set in my stripe products?
can you paste the subscription id here, it starts with sub_
yep, you would probably want to check where you're passing in the metadata and update that accordingly
your code is passing in that information : https://dashboard.stripe.com/test/logs/req_P5lG4Qv2vIJAbS when creating the Checkout Session
would updating the product name metadata solve this issue?
have you checked your code to see where you're passing in that metadata and what's the logic used for it?
That's your own code, so I can't tell you what's the logic used to derive the metadata being passed in when creating the Checkout Session
its using laravel/spark package so its not code that ive written
so im currently diving into it to understand how its setting the name
The metadata parameter are definitely being defined somewhere in the code and should be able to be updated. You need to track down where the Checkout Session is being created. From there, you will be able to figure out how the metadata name is being passed in