#Pol_Lepel -checkout

1 messages · Page 1 of 1 (latest)

fleet surge
modest garden
#

req_jVP1A8ZuYYuncH

fleet surge
#

If you are using application_fee_amount it means you are using Connect, and want to keep a fee on your platform account. Is that what you want to do?

modest garden
#

exactly

fleet surge
#

Well in the request you shared, there's no connected account involved, so it won't work.

modest garden
#

thats odd i will look into that on my side in the test mode it is working

#

only not in live mode

fleet surge
#

Can you share a request ID of this working in test mode?

#

In live mode you are either forgetting to use the Stripe-Account header, or forgetting to pass transfer_data[destination].

modest garden
#

req_3QJiAsJVeC3EAk

fleet surge
#

This request has:

transfer_data: {
   destination: "acct_1KPUgjPR3D7uuulF"
}
modest garden
#

i got another request here
req_Xz27nVWSM7wyoE

#

in this one it gives the right connected account

#

also works on desktop

#

only not on mobile

fleet surge
#

The original request you shared (req_jVP1A8ZuYYuncH) doesn't have a transfer_data.destination, that's why it fails.

modest garden
#

req_Wil3mARfiWdIGB this is a desktop call that does work

#

in live mode

#

req_SVbBBYgoCsMhLB this one setup exactly the same way but returns error 400

#

sorry for the questions 😅

fleet surge
#

Yes, this is the exact same problem I explained before:

  • req_Wil3mARfiWdIGB has transfer_data.destination, so it works
  • req_SVbBBYgoCsMhLB doesn't have transfer_data.destination, so it fails
modest garden
#

i know but the button to initialize the call is the same on phone as on desktop, on phone it isn't passing the transfer_data.destination and on desktop it is, so I thought maybe stripe would know why that is

fleet surge
#

Well from Stripe's point of view, the API calls we receive from you are different.

#

So it looks like your system is doing something different when on Desktop/mobile. That's something that you'll have to investigate on your end.