#jgmorillo_code
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1290645835394187327
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
can you share a link where I can reproduce the issue?
Aporta tu granito de area a El Debate y forma parte de un proyecto que ofrece toda la actualidad y los mejores análisis de la prensa española
sometimes it works just fine, some others, well it doesn't
if the buttons are rendering correctly, you could try to refresh the page, usually this triggers the error when is not occurring at first load
the buttons are accesible even if they do not render properly, but for the client this is very bad
what I mean for this, is that when you click on "gray" space, you are redirected to checkout session page
thanks! give me a few minutes to look into this.
sure!
one more thing
you probably would need to log in in order to take a look to all buttons on different tabs
use this credentials jgmorillo@hiberus.com pass 123123123
I've refreshed the page 10 times, and the button always appear correctly:
sometimes it just renders wrong, as the screenshots provided
it has happend to me very few times, but for the client it happens very often, so i need to fix it anyway, that 's why i was thinking to render the buttons of the seleccted tab only when the tab is clicked
is there any way to do that?
wait, I managed to reproduce the issue.
that's odd, looking into this.
note tat a quick workaround would be to design your own buttons, and when users click on it to send them to the corresponding Payment Link.
noted! that is probably easier than my solution. So the solution i was thinking is not possible'
?*
it should be possible to use multiple Payment Links button on a page. but right now I don't know why it's not working, that's why I suggested the solution above.
great! thank you soma, you rock! have a nice day!
sorry soma
i have another question
is there anyway to send via payment link the current user?
for payment buttons i can use customer secret as a data attribute for the button
oh I see! looking into this.
that's actually different, it's just a reference ID, not the full customer object.
but it links the payment to the customer?
as i can see, the customer email is prefilled in the checkout session
No not quite, it's an ID for you to map in your own system, like an order ID
oohh
You might also be using the prefill_customer_email query parameter
i need this to be linked in order to query afterwards the payment historial
i
that is how i retrieve all payments and subscriptions, if with that parameter, i can retrieve the payment calling those endpoints, it works for me
Only the buy button using the customer session allows a firm reference to an existing customer
any other ideas in order to achieve this?
as we are not storing stripe transactions
we only query them when this view is rendered
If you want to redirect known/existing customers to additional purchases, you will want to look at using checkout sessions directly for that
the only thing i need is that the payment can be retrieve using customer id
retrieved*
and of course, identify user on the payment link like customer secret in buy buttons
I've shared feedback that you'd like to see this functionality, but that's not supported currently outside of the buy button as you showed
and buy buttons instanced programatically can't be achieve neither, right?
What do you mean by that?
look at this screen shot, i have several buttons on each tab, is it possible to instance buttons for each tab when the tab is displayed?
I see the screenshot, but what does your integration actually do here? What do you mean by "instance buttons for each tab when the tab is displayed"?
create the embbed components for the remaining buttons only when the related tab is clicked
these are created by your library which loads with this script <script async
src="https://js.stripe.com/v3/buy-button.js">
</script>
Right, but i mean how are you creating these?
they just create on page load, what i want to know if this process can be interrupted or apply only to some buttons
and after that, render only the buttons of the tab that the users click to display
My understanding is that you can create multiple buttons, I'm not aware of a limit
trying to create 11 (at this moment), some of them break
If some of those buttons are visually hidden in a "tabs" view I don't see why that should be a problem
because this happens, some buttons break and render only "gray"
PM and client are about to cut my head off, so i need to solve this ASAP, any ideas?
I can see it too, but I'm not aware of any limitation with these.
neither did I when i proposed this solution 🥲
Can you please write in to support with this example page + credentials? We'll have to get this investigated more deeply to understand why some of these are intermittently failing.
If you do that right away and let me know, I can make sure it gets escalated to the right team right away
great!