#bruno_api
wooden cipherBOT
👋 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/1313198657922797638
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- brunei_api, 3 hours ago, 9 messages
tawdry lake
Hi 👋
The error message is correct. We do not support collecting application fees from Connect Accounts outside your region
ornate hound
Hey!!
Is there any other alternative? Using Standard Connect Accounts?
Everything I've tried resulted in an error. Last time I was told about cross-border payouts but found out that they are not available for Standard Accounts integration 😢
tawdry lake
Hmmm... let me test something
ornate hound
Sure.. thank you!
tawdry lake
I was able to create Destination Charges by specifying on_behalf_of https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted&lang=python#settlement-merchant
ornate hound
Should I inform the application_fee and the on_behalf_of property?
tawdry lake
I don't know what that means
ornate hound
I'd like to charge an application fee to the payment intent (charge) when creating it.
When I use on_behalf_of, should I sent it when creating a payment intent?
I'm talking about the application_fee_amount prop in:
https://docs.stripe.com/api/payment_intents/object
tawdry lake
We specify two ways to collect fees with Destination charges here: https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted&lang=python#collect-fees
ornate hound
I tried like this... Am I wrong?
When I try to confirm this payment intent:
Stripe doesn't currently support application fees for platforms in US with connected accounts in MX.
wooden cipherBOT
river blaze
Hello, apologies for the delay. It looks like you are running in to the restriciton that we don't support OBO for cross-border transfers:
The platform must be the business of record. Consequently, destination charges with on_behalf_of (OBO) aren’t supported.
https://docs.stripe.com/connect/cross-border-payouts#restrictions-and-requirements
So if you remove the on_behalf_of parameter that should get rid of the error.
@ornate hound in case you stepped away
ornate hound
Hello @river blaze Thanks for reaching me out...
When I remove the on behalf of parameter and then try to pay the payment intent, i have the same error...
When confirming it
river blaze
Can you send me the ID for the error when OBO isn't involved? That is surprising
ornate hound
Maybe i'm doing something wrong. Let me clarify:
- Create a payment intent with: amount, currency, automatic_payment_methods[enabled], transfer_data[destination] and transfer_data[amount].
This is the payment intent id i just generated: pi_3QRefbG9OPFEDv4k1t6htoW1
- When trying to confirm it:
https://api.stripe.com/v1/payment_intents/pi_3QRefbG9OPFEDv4k1t6htoW1/confirm
It gives the error:
"error": {
"code": "charge_invalid_parameter",
"doc_url": "https://stripe.com/docs/error-codes/charge-invalid-parameter",
"message": "Stripe doesn't currently support application fees for platforms in US with connected accounts in MX.",
Where do I get the Id for the error?
river blaze
Just found one https://dashboard.stripe.com/test/logs/req_gY2dHqwCwOh8XQ
Your dashboard logs are a good place to look: https://dashboard.stripe.com/test/logs
I am not sure what is happening here. I will consult my colleagues and get back to you
ornate hound
Sure!! Thank you so much!
river blaze
Ah it looks like the conflict here is that you are creating Standard stripe accounts with a full service agreement. We only support destination charges for accounts with a recipient service agreement. https://docs.stripe.com/connect/service-agreement-types#recipient
I have not been able to test whether you can create an account with standard dashboard access + a recipient service agreement but that may work for you here.
ornate hound
I couldn't... already tried something in this way. It gives me the error:
Maybe this is only possible for Express and Custom connected accounts?
river blaze
I don't think you can do this while setting type='standard' but we recently released more granular connect settings where dashboard type is separate from some of the other things that standard accounts come packaged with. One sec, finding what the equivalent of a standard connect account looks like here
https://docs.stripe.com/connect/service-agreement-types?connect-account-creation-pattern=typeless#choosing-type-with-api
Here is what the equivalent controller settings are for a standard account. https://docs.stripe.com/connect/migrate-to-controller-properties#standard
ornate hound
Is there any way to know if a standard account can have the "recipient" dashboard type? Cause I can't set it to "recipient" right now
river blaze
Standard accounts cannot have recipient agreement types. I am not sure what specifically that restriction is tied to controller-settings wise, but it may be possible to allow a standard dashboard with a recipient agreement. I will try to test this in a minute
ornate hound
Thank you
river blaze
Ah, unfortunately it looks like having full dashboard access is not compatible with a recipient agreement type. So to do this destination charge flow cross border, you will need to set them to have only express dashboard access or no dashboard access
ornate hound
That's sad news to us 😢
Thank you so much for your effort and Snufkin's.
river blaze
No worries, sorry to hear, though I guess it is good to have a sure answer at least. And thanks for your patience!