#jgmorillo_code

1 messages · Page 1 of 1 (latest)

void roseBOT
#

👋 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.

sullen stream
golden inlet
#

hi there!

#

do you see any errors in the browser console?

sullen stream
#

sending them

#

Hi soma!

golden inlet
#

can you share a link where I can reproduce the issue?

sullen stream
#

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

sullen stream
golden inlet
#

thanks! give me a few minutes to look into this.

sullen stream
#

sure!

#

one more thing

#

you probably would need to log in in order to take a look to all buttons on different tabs

golden inlet
#

I've refreshed the page 10 times, and the button always appear correctly:

sullen stream
sullen stream
#

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?

golden inlet
#

wait, I managed to reproduce the issue.

sullen stream
#

that's it

golden inlet
#

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.

sullen stream
#

noted! that is probably easier than my solution. So the solution i was thinking is not possible'

#

?*

golden inlet
#

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.

sullen stream
#

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

golden inlet
#

oh I see! looking into this.

sullen stream
void roseBOT
golden inlet
#

that's actually different, it's just a reference ID, not the full customer object.

sullen stream
#

but it links the payment to the customer?

#

as i can see, the customer email is prefilled in the checkout session

rotund cobalt
#

No not quite, it's an ID for you to map in your own system, like an order ID

sullen stream
#

oohh

rotund cobalt
#

You might also be using the prefill_customer_email query parameter

sullen stream
#

i need this to be linked in order to query afterwards the payment historial

#

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

rotund cobalt
#

Only the buy button using the customer session allows a firm reference to an existing customer

sullen stream
#

any other ideas in order to achieve this?

#

as we are not storing stripe transactions

sullen stream
rotund cobalt
#

If you want to redirect known/existing customers to additional purchases, you will want to look at using checkout sessions directly for that

sullen stream
#

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

rotund cobalt
#

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

sullen stream
#

and buy buttons instanced programatically can't be achieve neither, right?

rotund cobalt
#

What do you mean by that?

sullen stream
rotund cobalt
#

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"?

sullen stream
#

create the embbed components for the remaining buttons only when the related tab is clicked

rotund cobalt
#

Right, but i mean how are you creating these?

sullen stream
#

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

rotund cobalt
#

My understanding is that you can create multiple buttons, I'm not aware of a limit

sullen stream
#

trying to create 11 (at this moment), some of them break

rotund cobalt
#

If some of those buttons are visually hidden in a "tabs" view I don't see why that should be a problem

sullen stream
#

PM and client are about to cut my head off, so i need to solve this ASAP, any ideas?

rotund cobalt
#

I can see it too, but I'm not aware of any limitation with these.

sullen stream
#

neither did I when i proposed this solution 🥲

rotund cobalt
#

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

sullen stream
#

great!

sullen stream
#

Hi synthrider this is the case number 16550587

#

thank you for your help, you're the best! 🤘