#haltetothewood - issuing card

1 messages · Page 1 of 1 (latest)

swift zenith
#

Do you have a specific request ID i can inspect?

pulsar sail
#

Hey, thank you. What would be the request ID? I have the card id?

#

The stripe event id is: ipi_1KK2zLQaFntjgR7RCXyPrppG

#

I should also mention the card is issued within a connected account if that makes a difference.

swift zenith
#

When querying for a card id using issuing.card.retrieve

#

This should be an API request, and if you get an error I can inspect that

#

like a. req_123

pulsar sail
#

Hmm. I was using the node SDK.

#

Hmm I checked out the developer logs and I see that the requests aren't being associated with the connected account

#

Even though when creating the client we pass that in 🤷‍♂️ . There doesn't seem to be an option to pass in a connected account to the retrieve card request according to the docs.

swift zenith
#

Can you share a snippet of code for this retrieve request?

pulsar sail
#

const {
metadata: { requestId },
} = await stripe.issuing.cards.retrieve(cardId,
{
stripeAccount: getStripeConnectedAccountId(),
});

#

That's terrible formatting sorry

#

getStripeConnectedAccountId() basically returns our test connected account

#

I also tried: const card = await stripe.issuing.cards.retrieve(cardId) and got the same error

#

I think everything is fine

swift zenith
#

Hmm I'm not seeing error in your logs related to this

#

oh?

pulsar sail
#

I see the 200 response

#

I'm just an idiot

swift zenith
#

OK thats a good start, and makes sense why i don't see errors fitting this pattern (i was filtering only to API error responses)

pulsar sail
#

The error message comes from an internal service

swift zenith
#

Something validation the response locally?

#

👍

pulsar sail
#

😵‍💫

#

Thanks for your time

swift zenith
#

NP!

#

Glad you got it figured out!

#

I am but a humble rubber duck, a giant one though

pulsar sail
#

⭐