Imok

[ocean arrow]

hi! do you have more context on the error like the request ID req_xxx or the exact API call you're making? https://support.stripe.com/questions/finding-the-id-for-an-api-request

[balmy anchor]

Sure, here is the request id: req_yoPfYlnudv3Czu

But I dont understand the issue, because when I try to pay the same stuff, it works. But for the customer, it does not.

I checked, and the price id is valid in our system.

And for example yesterday for one customer, it worked, the whole payment process..

Sorry it was 2 days ago, but still, it worked

[ocean arrow]

doesn't really matter what it says in your system, you can see on https://dashboard.stripe.com/prices/price_1Ls39CFraZIiu8LZmAFR3JO4 the Price is archived

you called the API in https://dashboard.stripe.com/logs/req_75ReoAlNHnvzHu mark it as active:false (which is archiving it).

[balmy anchor]

Ohh and another thing, related to this. Why is it archiving prices, when its the same price amount? I mean, we did not changed the price, and whenever someone wants to pay, it will archive the price and make a new one for the same product.

[balmy anchor]

So what u are saying is that somewhere in our backend, we mark the price as inactive?

[ocean arrow]

yes

[balmy anchor]

I guess here?

[ocean arrow]

seems like it

[balmy anchor]

Hmm, alright, I am gonna debug it, lets see why the devs made the code working like this.

I have another question, related to our stripe account and connected accounts. We have this Stripe account, ThunderWOD. Why are we in minus?

And if we have connected accounts, with account fee setup, do We pay for this fee or the connected account will do?

[ocean arrow]

depends what type of Connect charges you use(Direct charges, the connected account pays, Destination charges, the platform pays)

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

[balmy anchor]

And where can i see what kindo of charges do we use?

[ocean arrow]

it's something you should know from building the integration as it's a core part of your design

looks like you use Destination charges, at least in the example request you shared

[balmy anchor]

Well, here i pass the stripe fee amount , which is set manually from our admin side

[ocean arrow]

indeed

[balmy anchor]

And within this code, i have to say if i want direct chanrges?

Or in the stripe platform i have to setup this thing?

[ocean arrow]

it doesn't really work that way. What is the wider question? Changing from one charge type to another is a huge change and fundamentally changes your business since it changes how refunds and chargebacks and fees and reporting works completely

you should work with your developers and colleagues to understand it

[balmy anchor]

Well, we are all pretty new working with Stripe. We are using it in a while, but our app juts got live a few weeks ago. And we started to connect some accounts , using Connect. We want to charge every Connected account with a custom amount, and we are trying to understand the whole process. Until now, we can see that the amount goes to the connected accounts if a customer buys something, and the application_fee_amount is charged. We just want to make sure that the whole integration is working well, and every amount arrives where it needs to be.

[ocean arrow]

makes sense, do you have any specific questions?

[balmy anchor]

How can we convert this whole integration to use direct charge? After your answer, I am afraid we cant do that...

Do we have to change the connected account settings or we have to make changes in out Main Stripe Account and integration?

[ocean arrow]

best approach would be to read the guide https://stripe.com/docs/connect/enable-payment-acceptance-guide

[ocean arrow]

potentially both. You'd have to change your integration code (a lot) yes. Please read the docs and make sure you understand the difference between the charge types and what implications there are , let us know if anything is unclear!

[balmy anchor]

Alright, thank you for your answers!

Ohhh and one more thing, just to be clear. Our main account have the products and the customers. Do the connected account has to have those customers and products as well? Or its enough if the products and customers are present in our Main Stripe Account?

[steep hound]

Hi! I'm taking over this thread.

If you want to use Direct Charge, then all objects (Customer, PaymentMethod, Product, Price) will have to be on the connected account.

[balmy anchor]

Alright. Its just to much to understand this whole thing. Sorry for my idiot questions.. 😦

[balmy anchor]

Okey, thats usefull info! The only problem is that our backend system is not designed like that. It only knows how to create products in our main stipe account.

[steep hound]

Yes, so like my colleague said earlier, this will require to change your integration.
FYI, to create any object to a connected account, you do the same as if you wanted to create the object on the platform but use the Stripe-Account header and set it to the merchant ID of the connected account. You can learn more about this here: https://stripe.com/docs/connect/authentication

[balmy anchor]

Awesome. This is a very helpful info right now! I will read the docs, maybe this approach is the best, to create objects in the connected accounts. That would solve the issue and meanwhile we can change the integration as well. Thanks again!