Scott-payments

[dense eagle]

looks like you have a 404 to confirm the PaymentIntent. That usually means you mixed up your Stripe API keys(like you use the publishable key pk_test_xxx from a different account than the one you used the secret key sk_test_xxx from to create the PaymentIntent on the backend).

[next mountain]

Okay cool, I will double check this now

I just cross checked and everything is correct in relation to the keys

When I click the google pay button and the dialog pops up, the pay intent is not created at this point.

Only when I click "Pay" the intent is created

[dense eagle]

do you have the PaymentIntent ID pi_xxx?

[next mountain]

After debugging, when I click this button the payment intent should be created at that point, correct?

[dense eagle]

not necessarily, it depends how you built things.

can you share the PaymentIntent pi_xxx where you got this 404 error?

you can copy the ID from the URL in that error you posted

[next mountain]

This is the latest error: pi_3KRECRPeO7UcWR5r0iavcFxt

/v1/payment_intents/pi_3KRECRPeO7UcWR5r0iavcFxt/confirm

[dense eagle]

ok so you use Connect and create this on a connected account

[next mountain]

It's like it's processing the payment before creating the intent

[dense eagle]

so the problem (99%) is that you didn't pass the connected account ID on the frontend.

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

[next mountain]

I have the connect ID on the front end

I can also see the payment intent showing up in the connect account

[dense eagle]

are you sure?

[next mountain]

Yes

[dense eagle]

can you check?

[dense eagle]

add a print statement and check that you actually pass Stripe(key, {stripeAccount :"acct_1KQtI1PeO7UcWR5r "} and not like a variable that is null

[dense eagle]

that means nothing, what is set in the code

also you seem to be doing Direct Charges on an Express account, which is not recommended by the way

[next mountain]

I was onto support about this as well, i'm not too sure of the best practice

[next mountain]

I have tried passing the connect account ID from the backend rather than that way I had it and that seems to work

Just going to continue testing that

[dense eagle]

ok, that is how you fix it anyway!

[next mountain]

In relation to the Direct Charges, what would be the best way to do this?

[next mountain]

Thank you 🙂

[dense eagle]

Destination charges with Express or Custom accounts, Direct charges with Standard accounts

https://stripe.com/docs/connect/charges#types

[next mountain]

I will have a proper read into this, thank you for pointing this out to me as well

With the way the charges are right now, would that be okay given that connect users for what I am building are responsible for them charges?

[pallid hedge]

Hey, taking over from @dense eagle – just catching up!

[pallid hedge]

Can you clarify the question?

[next mountain]

So right now the charges of stripe fees go to the connect account and taken away from the amount sent to them.

Would this be okay if they're agreeing to these charges and fees?

[pallid hedge]

I guess it depends on your agreement with your customers/users! But that's how direct charges work yes

But as my colleague explained, you shouldn't really use direct charges with Express connected accounts

[next mountain]

Would there be another way of them picking up the fees?

As the platform I am developing is free to use, with no subscriptions, the direct charges was so they can handle the fees for the service

If that makes sense

[pallid hedge]

The Stripe fees? No. But instead you could calculate your application fee to cover the Stripe fee is you wished

[next mountain]

Okay cool, thank you for the ideas in relation to all this 🙂

[pallid hedge]

Np!