a1dminaaa

[tight bridge]

Hi there!

I'm not sure I understand the question.

source_transaction is an optional parameter, so you don't have to set it. But we recommend setting it to avoid getting errors because of not enough balance.

[woeful monolith]

Stripe transfer error：For Transfers involving Brazil, the source_transaction parameter is mandatory. See https://stripe.com/docs/connect/separate-charges-and-transfers for more information. If you have any question, please contact us via https://support.stripe.com/contact.; code: transfers_not_allowed; request-id: req_D2JTnHcAsO7Opr

When I called the transfer API, I did not specify the source_transaction parameter, and the API responded with an error

[tight bridge]

Well then the error is pretty clear. What's your question?

[woeful monolith]

When transferring funds in the Brazil region, it is necessary to specify the source_transaction parameter, which means only one payment record can be specified. But our withdrawal business may have to withdraw from multiple payment records

Is there any other way to achieve this

[tight bridge]

No sorry, you'll need to set a single source_transaction for this to work.

[woeful monolith]

ok

Is there any other solution that can achieve this function

[tight bridge]

If you want to do a transfer in Brazil, you have to set source_transaction. And source_transaction can only include one payment.

[woeful monolith]

Okay, I understand. Thank you

There's another question

We encountered an error while using the connect function in express mode: Cannot onboard via express oauth due to gated access

[tight bridge]

Can you share the request ID (req_xxx)? You can find it here https://dashboard.stripe.com/test/logs

[woeful monolith]

I didn't see the corresponding log

[tight bridge]

Then can you clarify exactly what you are doing and where you see that error?

[woeful monolith]

But you can try accessing this URL for testing：https://connect.stripe.com/express/oauth/v2/authorize?redirect_uri=https://express.qwqer.com/api/pay/stripe/transferRedirect&client_id=ca_OlmEZLiikkfU2FnmVgBLl6zCdO9Z0zZL&state=1729705249888927744&stripe_user[business_type]=individual

These are our connect configurations

I can use Standard now to function normally

[tight bridge]

Thanks! Give me a few minutes to look into this.

[woeful monolith]

I don't know if this is caused by an account permission issue, but the account in our Stripe backend is [e-mail]

[woeful monolith]

👀

[barren juniper]

Yeah funfortunately I'm not sure. We generally discourage using OAuth to onboard Express accounts – you should be using Account Links

[woeful monolith]

We use a connect account for transfer operations

[barren juniper]

Yup, but you should be onboarding via: https://stripe.com/docs/connect/express-accounts#create-link

Not the OAuth URL

[woeful monolith]

We integrate within the app

[barren juniper]

Not sure what you're describing, but not sure how that prevents you from using an Account Link

[woeful monolith]

Okay, I'm researching this