ScottWrkout | Stripe Developers | Page 1

tardy viperBOT Dec 23, 2022, 7:38 PM

#

median seal Dec 23, 2022, 7:38 PM

#

👋

boreal shell Dec 23, 2022, 7:38 PM

#

Hi there

#

We are having issues integrating Stripe with Connected accounts. When we create a PaymentIntent using a Connected AccountId, we are unable to load Stripe Elements in order to complete the payment. We get a 404 from the Stripe API trying to retrieve the PaymentIntent. We have confirmed that we are sending the client_secret, and can see that it is part of the request, however we are getting 404's retrieving the object. It seems like maybe an ownership issue of the PaymentIntent? This is being done in test mode.

median seal Dec 23, 2022, 7:41 PM

#

Sounds like you may not be initializing client-side as the Connected Account

#

Take a look at https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application

#

Are you initializing stripe using the Connected Account ID and your platform publishable key?

boreal shell Dec 23, 2022, 7:42 PM

#

We are passing the Client ID to the 'loadStripe' javascript function, but I'll have a look at the document.

#

Yes, we are.

median seal Dec 23, 2022, 7:42 PM

#

Ah okay

#

Can you provide a request ID for one of these 404s?

boreal shell Dec 23, 2022, 7:42 PM

#

Sure thing. One moment.

#

pi_3MHuCt4QsoQHum8C0ibtwLEa

median seal Dec 23, 2022, 7:43 PM

#

Thanks, looking

boreal shell Dec 23, 2022, 7:44 PM

#

That's the request ID for the PI itself, let me find one for the 404

median seal Dec 23, 2022, 7:45 PM

#

I found one

#

No worries

boreal shell Dec 23, 2022, 7:45 PM

#

Ok, excellent. The 404's appear to have disappeared from the dashboard on my end.

median seal Dec 23, 2022, 7:45 PM

#

You have to filter for GET requests

#

We don't display GET requests by default

#

That said, it does look like an issue with the key initialization

boreal shell Dec 23, 2022, 7:46 PM

#

Interesting. They were showing live yesterday for us.

#

They don't appear when I filter to GET now, either.

median seal Dec 23, 2022, 7:47 PM

#

I see the error on your platform account. Example: https://dashboard.stripe.com/test/logs/req_lIKjESaMjmO4UT

boreal shell Dec 23, 2022, 7:47 PM

#

Not a big concern since you've found one.

#

Yes, that's one of the requests.

median seal Dec 23, 2022, 7:47 PM

#

Which tries to retrieve pi_3MHu4W4QsoQHum8C0tUydjcY but that PaymentIntent exists on your Connected Account (acct_1MFlc44QsoQHum8C)

boreal shell Dec 23, 2022, 7:47 PM

#

Right

median seal Dec 23, 2022, 7:47 PM

#

That said, the retrieval here is happening server-side

#

Not client-side

#

So you need to pass the Stripe Account header server-side to retrieve that

boreal shell Dec 23, 2022, 7:48 PM

#

We are trying to set it up such that the money is transacted through the Connected account.

median seal Dec 23, 2022, 7:48 PM

#

So as we show here: https://stripe.com/docs/connect/authentication#stripe-account-header

#

Do you have the code for your server-side PaymentIntent retrieval?

boreal shell Dec 23, 2022, 7:48 PM

#

Yes -- and we are passing it as such. One moment, I'll paste the code I shared with stripe support.

median seal Dec 23, 2022, 7:49 PM

#

Sounds good. I have to step away but my colleague will jump in to help!

boreal shell Dec 23, 2022, 7:49 PM

#

cyan bane Dec 23, 2022, 7:50 PM

#

boreal shell We are trying to set it up such that the money is transacted through the Connect...

Your current setup will do this. You are creating the payment intent on the connected account so the funds will go to that account. I actually see you don't have an application fee on these payments so your platform won't get any funds from these payments unless you add them

boreal shell Dec 23, 2022, 7:50 PM

#

Understood with respect to the application fee. We are doing this in test mode, so that is not currently a concern.

cyan bane Dec 23, 2022, 7:51 PM

#

Awesome, just making sure

#

Do you do a similar thing with requestOptions when retrieving the payment intent as well? From the call bismark found, it looks like that didn't happen which is why that request returned a 404

boreal shell Dec 23, 2022, 7:53 PM

#

We are not requesting the PaymentIntent from our API-side. We are using Stripe Elements, which is where the call is failing.

cyan bane Dec 23, 2022, 7:53 PM

#

Do you have a public test page I might be able to look at here?

boreal shell Dec 23, 2022, 7:54 PM

#

@waxen atlas -- Can you link Pompey to a test page on staging for this?

#

https://wrkout-st.live/scottistest/packages

#

That should work

cyan bane Dec 23, 2022, 7:58 PM

#

Thank you. Checking out that page

boreal shell Dec 23, 2022, 7:59 PM

#

Hang on, Stripe isn't connected on that one

cyan bane Dec 23, 2022, 7:59 PM

#

What do pre and post stripe mean there?

boreal shell Dec 23, 2022, 7:59 PM

#

Give me a moment!

cyan bane Dec 23, 2022, 7:59 PM

#

Gotcha

boreal shell Dec 23, 2022, 8:06 PM

#

I think our server is configured to have payments pass through us at the moment; it is working in that capacity. I'll have to update the server to the connected account. One moment.

#

I created this PI which transacted, however the payment goes through our main account rather than the connected account: pi_3MIHSvGIgUExgoNw0xNiHJqG

#

That PaymentIntent has the connected account ID attached to it, but the front end loadStripe call is not using the account ID

cyan bane Dec 23, 2022, 8:10 PM

#

It looks like you created the payment intent on your platform account rather than the connected account https://dashboard.stripe.com/test/logs/req_E0w5rvM9zkZnJD

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

boreal shell Dec 23, 2022, 8:10 PM

#

Yes, you are correct.

cyan bane Dec 23, 2022, 8:11 PM

#

So whatever code ran may not have used that StripeAccount argument

boreal shell Dec 23, 2022, 8:11 PM

#

Main branch was out of date for me locally, updating it. We are mid-deploy however, so need to hold off before I can make the change. Are you available for the next bit?

cyan bane Dec 23, 2022, 8:13 PM

#

Yeah I'm here for a bit and after that a colleague will swap in who can also help.

boreal shell Dec 23, 2022, 8:14 PM

#

Coordinating on our end. Shouldn't take long.

cyan bane Dec 23, 2022, 8:15 PM

#

Also to be clear, the call that bismark found earlier was definitely server side, so it looks like somewhere in your code there is a PaymentIntentService().Get() call that does not use this Stripe-Account header either https://dashboard.stripe.com/test/logs/req_lIKjESaMjmO4UT

boreal shell Dec 23, 2022, 8:20 PM

#

Can you see the call source? I believe the call is coming from wrkout-st.live which is our front-end.

#

Oh, that call was made by insomnia -- that was an attempt to retrieve it manually.

cyan bane Dec 23, 2022, 8:22 PM

#

Ah okay that makes sense as well, I just saw it came from a .NET call and was just calling that out in case your server-side code had that somewhere

boreal shell Dec 23, 2022, 8:22 PM

#

Our internal API only ever calls CreateAsync with respect to payment intents

boreal shell Dec 23, 2022, 8:43 PM

#

Ok. Our staging server is updated to use the Account ID, and is returning 404 errors again.

#

https://wrkout-st.live/scottistest/packages

#

If you select an item, you'll see that Stripe Elements flashes briefly on screen, then disappears and the networking console shows the 404 trying to retrieve the PaymentIntent.

cyan bane Dec 23, 2022, 8:45 PM

#

I assume I should try the "post-stripe" option?

boreal shell Dec 23, 2022, 8:46 PM

#

Either is fine, the naming is related to internal pricing as opposed to functionality.

cyan bane Dec 23, 2022, 8:46 PM

#

Do you have credentials for a test account? It is asking me for a login

#

If you can DM them to me I can use them

boreal shell Dec 23, 2022, 8:46 PM

#

One moment, I'll get you some.

#

Sent

cyan bane Dec 23, 2022, 8:54 PM

#

Thank you, it actually turns out @median seal is stepping back in so I passed the credentials back along to them.

boreal shell Dec 23, 2022, 8:54 PM

#

Ok

median seal Dec 23, 2022, 8:54 PM

#

👋

#

Taking a look

boreal shell Dec 23, 2022, 8:55 PM

#

Thanks

median seal Dec 23, 2022, 8:57 PM

#

K here is the request your frontend is making: https://dashboard.stripe.com/test/logs/req_dNTXXTloZcAgWU

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

So yeah, that request is coming from your platform account

#

And trying to retrieve a PaymentIntent on the Connected Account

#

So the issue really is the initialization of Stripe on your frontend

#

However, why are you retrieving the PaymentIntent via a GET request to begin with?

#

Why not just pass the client secret from server --> client

boreal shell Dec 23, 2022, 8:59 PM

#

We are using the JS library and initializing with `loadStripe( [publishable key], { stripeAccount: [client_accountId] });

#

We are passing the client secret from our API to our front end

#

The documentation indicates to use the client secret to initialize Stripe Elements, which we are doing. Is there another way we should be loading this?

median seal Dec 23, 2022, 9:01 PM

#

Can you share your full relevant client-side code here?

boreal shell Dec 23, 2022, 9:01 PM

#

@waxen atlas ^

median seal Dec 23, 2022, 9:01 PM

#

boreal shell The documentation indicates to use the client secret to initialize Stripe Elemen...

Yes but generally what you do is fetch your server to create the PaymentIntent and then respond to that fetch request with the client-secret

#

Wait... you must already be doing that

boreal shell Dec 23, 2022, 9:02 PM

#

Yes -- our internal API creates the PaymentIntent and returns the Account ID and client secret.

median seal Dec 23, 2022, 9:03 PM

#

Yeah so where does the GET request come into play here? Like why are you retrieving the PaymentIntent at this point at all?

boreal shell Dec 23, 2022, 9:03 PM

#

We are not issuing the GET request anywhere directly -- I believe it is happening when we call Stripe Elements.

#

Wait, I see something in our code where perhaps we are doing so -- let me investigate. Thank you for pointing that out.

median seal Dec 23, 2022, 9:06 PM

#

Yeah your code is doing that and it is worth looking into why, however you are still going to run into the same issue when attempting to render Payment Element since you aren't initializing as the Connected Account for some reason. Can you try hard-coding the Connected Account ID into { stripeAccount: [client_accountId] }

boreal shell Dec 23, 2022, 9:06 PM

#

We were trying exactly that yesterday. Happy to try it again, though.

#

Hmm. The point where we attempt a GET is after the return URL, so we aren't reaching that point in our code.

median seal Dec 23, 2022, 9:13 PM

#

Yeah that can't really be the case... we see the GET request occurring on page load.

#

Looking at your page more to see if anything jumps out

#

But if you can share client-side code that would help

boreal shell Dec 23, 2022, 9:27 PM

#

Our FE is written in vue/typescript, so we're debugging the generated JS now..

median seal Dec 23, 2022, 9:30 PM

#

Gotcha. Yeah I'm not able to inspect your frontend code via the Web Dev Console so I can't help too much from here.

#

The issue really does come down to something preventing the front-end from initializing Stripe as the Connected Account

#

Will just be figuring out why that isn't happening

boreal shell Dec 23, 2022, 9:47 PM

#

I believe the GET request in question is being generated by Stripe Elements when we load it; is there a way for us to pass the Account ID to Stripe Elements when we create the element?

median seal Dec 23, 2022, 9:47 PM

#

So there are two GET requests, one is generated by Payment Element attempting to be rendered, the other is your code attempting to retrieve the PaymentIntent

#

Both hit the 404 since Stripe is initialized as the platform but the PaymentIntent is on the Connected Account

#

That's why I said above that it didn't actually fully matter if you found the source of your own PaymentIntent retrieval, because this other GET request would still fail.

boreal shell Dec 23, 2022, 9:49 PM

#

We are currently confirming that we're calling loadStripe with the Connected Account ID

median seal Dec 23, 2022, 9:49 PM

#

To answer your question, you pass the Account ID when you initialize stripe, not Stripe Elements

boreal shell Dec 23, 2022, 9:49 PM

#

And it shows that we are.

median seal Dec 23, 2022, 9:49 PM

#

Are you willing to share the relevant code?

waxen atlas Dec 23, 2022, 9:50 PM

#

  console.log(stripeAccountId.value); // ''
  await generatePaymentIntent(selectedPackage.value, studioUserName.value);
  console.log(stripeAccountId.value); // 'acct_1MFlc44QsoQHum8C'
  await loadStripe(pubKey, { stripeAccount: stripeAccountId.value });
  stripeLoaded.value = true;

median seal Dec 23, 2022, 9:50 PM

#

And can I see your Elements Provider Component code

waxen atlas Dec 23, 2022, 9:51 PM

#

      <div v-if="stripeLoaded && stripeOptions.clientSecret">
        <StripeElements
          v-slot="{ elements }"
          ref="stripeCheckout"
          :test-mode="isStripeTestModeEnabled"
          :stripe-key="pubKey"
          :elements-options="stripeOptions"
          :confirm-params="confirmParams"
        >
          <StripeElement
            ref="payment"
            type="payment"
            :elements="elements"
            :element-options="elementOptions"
          />
        </StripeElements>
      </div>

median seal Dec 23, 2022, 9:52 PM

#

Hmm okay what is StripeElements?

#

That isn't our component

#

https://stripe.com/docs/stripe-js/react#elements-provider

#

Like you want to be using <Elements />

#

Above you are awaiting loadStripe but you never actually set that to a variable to pass to your Elements provider stripe prop

#

So yeah I think there is just an issue here with how you are using our Stripe React.JS library unless I'm missing something?

waxen atlas Dec 23, 2022, 9:55 PM

#

We are using

"vue-stripe-js": "^1.0.1",

https://www.npmjs.com/package/vue-stripe-js

npm

vue-stripe-js

Vue 3 components for Stripe.js: Elements & Checkout. Latest version: 1.0.1, last published: 7 months ago. Start using vue-stripe-js in your project by running npm i vue-stripe-js. There is 1 other project in the npm registry using vue-stripe-js.

#

We have a vue3 app, not react

median seal Dec 23, 2022, 9:55 PM

#

Ahhh doh you mentioned that above

#

Sorry

#

Okay interesting. I'm not very familiar with Vue but let me take a look

#

Okay so here: const stripeKey = ref('pk_test_xxx') can you try doing const stripeKey = ref('pk_test', { stripeAccount: 'acct_123'})

waxen atlas Dec 23, 2022, 9:58 PM

#

trying it now

#

do you mean using the litteral hardcoded 'pk_test' and 'acct_123'?

median seal Dec 23, 2022, 10:01 PM

#

No I mean with your key/account. But actually I don't think that is going to work.

#

Let's do a test actually

boreal shell Dec 23, 2022, 10:01 PM

#

No -- looking through the github for this VUE component, it reinitializes Stripe in the Elements code they created.

#

export const initStripe = (key: string, options?: StripeConstructorOptions) => {
  try {
    if (!window.Stripe) {
      throw new Error(ERRORS.STRIPE_NOT_LOADED)
    }
    const stripeInstance: Stripe = window.Stripe(key, options)
    return stripeInstance
  } catch (error) {
    console.error(error)
    return error
  }
}

median seal Dec 23, 2022, 10:03 PM

#

That snippet is in your code or something you are seeing on github?

boreal shell Dec 23, 2022, 10:03 PM

#

That's from the component's github -- https://github.com/ectoflow/vue-stripe-js/blob/main/src/stripe-elements.ts

median seal Dec 23, 2022, 10:03 PM

#

Ah gotcha

#

Can you do a test with:

console.log("testLog: ", testLog);
  stripeLoaded.value = true;```

#

And lets see what that logs

waxen atlas Dec 23, 2022, 10:04 PM

#

will do

#

📎 stripeTestLog.txt

median seal Dec 23, 2022, 10:12 PM

#

Okay that's good. We do see _stripeAccount there

#

Hmm in the Github for Vue I see: ```<StripeElements
v-if="stripeLoaded"
v-slot="{ elements, instance }" // attention: important part!
ref="elms"
:stripe-key="stripeKey"
:instance-options="instanceOptions"
:elements-options="elementsOptions"

#

I don't see instance in your code?

#

Not sure what that is, but is there a reason that is missing?

boreal shell Dec 23, 2022, 10:14 PM

#

We're literally looking at that on our end right now as well 😉

#

Looking like we have a winner

median seal Dec 23, 2022, 10:18 PM

#

That fixed it?

boreal shell Dec 23, 2022, 10:18 PM

#

Looking like the payment was made -- our subsequent get to the PI may be failing, but we know why if that's the case.

waxen atlas Dec 23, 2022, 10:19 PM

#

Thank you so much for your help @median seal , I think this is an us issue now 👍

median seal Dec 23, 2022, 10:19 PM

#

Glad to hear that you are unblocked!

#

Don't hesitate to let us know if we can help any further

boreal shell Dec 23, 2022, 10:19 PM

#

If you come across other customers using the vue-stripe-js component, you can let them know that StripeElements in that package creates it's own Stripe instance and needs to be configured within the Element initialization!

median seal Dec 23, 2022, 10:20 PM

#

That's good to know! Might be worth leaving an issue on the github repo suggesting they update the ReadME (or submitting a quick PR to do so).

#

We don't maintain Vue-stripe-js otherwise I would be more proactive 🙂

boreal shell Dec 23, 2022, 10:25 PM

#

No worries. We can reach out and let them know about it. I haven't delved their documentation myself to see if it's documented, but either way it's good to have resolved.

Thanks for the great support. Much appreciated from yourself and Pompey.

#ScottWrkout