#jrfr23

1 messages · Page 1 of 1 (latest)

warped pecanBOT
bitter thorn
bright linden
#

oh sure let me take a look at how to do that, stand by

#

the request id is => req_SgTxEdvWwLvsxF

#

I apologize I provided the wrong request id

bitter thorn
#

Ok. This source was created on your connected account

#

You should specify a stripe_account in the request.

By specifying a stripe_account, you are telling Stripe that you want to make an API call on behalf of a connected account. You can refer to this doc to learn more about making API request for connected account (https://stripe.com/docs/connect/authentication)

Learn how to add the right information to your API calls so you can make calls for your connected accounts.

bright linden
#

i was able to pull every other aspect related to connected accounts without using that header

#

or I should say the source api requires doing something different than issuing refunds, cancellations, obtaining payment intent details, get charges and getting connect account details?

bitter thorn
#

I don't think you can make API calls on connected account without stripe_account header

bright linden
#

but otherwise do you believe a source id included in a top up event should be a source that I can retrieve info on?

#

ill try the header now

#

nice that worked, thanks for the help. I'm not sure if theres any way I can tell when I should use the stripe header or not for some connect account related api resources and not others

bitter thorn
#

I just checked your logs. You also use the stripe_account header when creating a top up on the connected account.

bright linden
#

roger

#

The reason I was curious about the source id listed in a previous topup event is that in the stripe docs that outline how to setup funding for issuing

#

theres a caution box that says:

#

is the source token it refers to the "source id" ?

bitter thorn
#

That doc is for refunding issuing balances, are you using Issuing?

bright linden
#

I'm understanding that the doc is about how to fund the Issuing balance for connect accounts using the Issuing product

#

(sorry went afk here)

#

its the mechanism to setup a bank account that will be used to fund the connect accounts issuing balance that virtual credit cards will debit against

bitter thorn
#

So are you using Issuing?

bright linden
#

yes we are using Issuing

bitter thorn
#

OK. Yes the source token is the source ID

bright linden
#

so the "Caution" box screenshot above from the docs above while you cant list or retrive sources directly it seems like you can get the source id from a topup if the source was used for a topup? And then can get the details of a source via that ID ?

#

Basically I'm just trying to understand what that caution box is trying to impart to the reader

bitter thorn
#

OK. for most of Stripe resources (i.e., PaymentIntents, PaymentMethods) there's a List API to retrieve the list of resources,

#

But there's no List Sources API to retrieve sources.

bright linden
#

ok got it

#

theres more to our scenario where this id seems to be needed to issue payouts or topups when wanting to specify a destination directly - im still a bit confused if it will work in all cases

#

but we didnt have the source id and wasnt sure how to get it - we'll start saving it going forward if it ends up being something we can use for topups and payouts for issuing

#

its a more extreme scenario where the crux of all this is wanting to change the original source/bankaccount to a different bank account after the connect account with issuing is setup

#

and its posing some issues

#

i dont have a specific question now based on what you've mentioned but thank you that clears up some aspects of the source object I was struggling with

#

thanks for the help