jakel_api

[slow hawk]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1267483354219941981

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[hoary gyro]

Hi there 👋 taking a look

[hoary gyro]

You're seeing that because you're using transfer_data.amount to try to transfer less than the full amount of the payment to the Connected Account, resulting in the Platform keeping part of the payment which is the same as collecting an application fee explicitly and isn't supported for the regions involved.

[civic cloud]

got it. how is that different than what we are doing here?

evt_3PhuTtFpAKNo2Ml21J9g7w5p

we are currently moving from the card element to the payment element and are having the error i mentioned during testing. however, as shown by evt_3PhuTtFpAKNo2Ml21J9g7w5p it is currnently working in our current implementation with teh card element

here is the requestId related to that event i mentioned: req_lEmx39risUp6QW

[rough igloo]

Hmm, likelihood is that there's different gate/configuration on the platform accounts as they're different:

• Error: acct_1Hf5uhBE0qXx3H5l
• Success: acct_1Fi5jPFpAKNo2Ml2
  There are configurations that we can apply to accounts to permit transactions with flow of funds like this, so I suspect the same config needs apply to that test account