#eddy_issuing-embedded-element

1 messages Β· Page 1 of 1 (latest)

dark sequoiaBOT
#

πŸ‘‹ 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/1405321454962348123

πŸ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

devout latch
#

Hello πŸ‘‹

Can you share some of the request IDs for those request steps you outlined?

warm hamlet
#

Sure give me a moment please πŸ™‚

#

Issuing Physical Card: req_hEmIjzqSUsba07
Update Pin number: req_UJRHRZAemaAaRz
Ephemeral key: req_BmPQ3ykFCjjMwa (stripe JS element)

#

Output will be 0000

devout latch
#

And this is in the display using the Issuing Card Pin Display element we mention here?

warm hamlet
#

yes

#

I can give you an URL if you want to play with the element

#

don't worry it's test env, that's why it's unsecured

devout latch
#

I'm trying to repro since I haven't built this integration yet

#

Damn, I need to be enrolled in Issuing πŸ€¦β€β™‚οΈ

warm hamlet
#

I think when you are on Stripe Sandbox you don't need to but maybe i'm wrong

devout latch
#

I am using a Sandbox account sorry to say

#

Okay let me try again

#

Oof they don't make this easy to test, do they?

warm hamlet
#

Unfortunately no, even when you try they Stripe Elements, they don't provide the PIN management

#

there is no PIN management here, even if you select a Physical Card

devout latch
#

Wow. Now I"m getting the very helpful error message "message": "An error prevented the PIN from being updated.",

warm hamlet
#

Where do you get this message?

devout latch
#

Unfortunately I think this will take longer than is suitable for a Discord thread. I think we'll need to engage the team building/maintaining these elements.

#

Where do you get this message?

Card creation

#

What I can do is send you a link that will allow you to create a support case with us that will get routed directly to our specialized developer support team.

#

So we can do our digging on our side and get back to you

warm hamlet
#

Sure but I think if you submit it it will escalate quicker

#

You might have Slack or something internaly

devout latch
#

What I'm saying is I won't have an answer before we close this thread

#

So we need the support case so we can respond to you

#

It's still my team who will be working that case

warm hamlet
#

Ok no worries and btw I don't have your issue when I create a card with a custom pin

dark sequoiaBOT
#

Hello @warm hamlet, we have sent you a direct message, please check it at https://discord.com/channels/@me/1405332264807563326

  • πŸ”—The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
devout latch
#

Okay I see your message in our queue and we will be digging into this and getting back to you with the resolution

warm hamlet
#

I opened the case, thank you @devout latch

devout latch
#

We're on it! 🫑

dark sequoiaBOT