#SoloGeneral-issuing-card

1 messages · Page 1 of 1 (latest)

prime pagoda
#

Do you have a request ID for the failed request?

blissful stirrup
#

req_nRRuov6PqHjsWM

prime pagoda
#

So it looks like the call is being made on behalf of this account (acct_1KhQkEJcIAKVEIOP) but the iauth actually lives on this account (acct_1LBk2qR3mPNiB0f9 ).

The Stripe::Issuing::Authorization.approve() method doesn't take a Connect ID, so you would have to make the request using the API key of the account that owns that iauth

#

Ah, wait.

#

Are you intending to have the payment made on behalf of the connected account? Or are you wanting the payment made on behalf of the platform?

blissful stirrup
#

on behalf of the connected account

prime pagoda
#

Passing the connected account ID as a header in the request

blissful stirrup
#

That is what I was asking. Since the webhook worked in test mode without it but is failing in prod, I wanted to make sure before pushing changes to our prod server.

Do I need to add stripe_account: '{{CONNECTED_ACCOUNT_ID}}', to the authorization line like this:

Stripe::Issuing::Authorization.approve(auth.id, stripe_account: '{{CONNECTED_ACCOUNT_ID}}')

prime pagoda
#

Stripe::Issuing::Cardholder.create({ name: 'Jenny Rosen', email: 'jenny.rosen@example.com', phone_number: '+18008675309', status: 'active', type: 'individual', billing: { address: { line1: '1234 Main Street', city: 'San Francisco', state: 'CA', postal_code: '94111', country: 'US', }, }, }, { stripe_account: '{{CONNECTED_ACCOUNT_ID}}', })

#

As an example

blissful stirrup
#

Ok. Thank you