#dani_api

1 messages ¡ Page 1 of 1 (latest)

viral salmonBOT
#

👋 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/1216685163732537364

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

coral eagleBOT
#

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.

ripe hatch
#

Hey there!

coral eagleBOT
ripe hatch
#

I have the following platform profile for connect:

image.png
#

And the following per-country settings:

image.png
hasty cove
ripe hatch
#

I thought that was the case (via a StackOverflow answer), but this doesn't seem to be the case, see:

dani@skynet ~> stripe accounts create --type=express --email="dani@brandties.com"                                                                                                         (base) 
{
  "id": "acct_1Ot5ZHEDYsGgYrA5",
  "object": "account",
  "business_profile": {
    "annual_revenue": null,
    "estimated_worker_count": null,
    "mcc": null,
    "name": null,
    "product_description": null,
    "support_address": null,
    "support_email": null,
    "support_phone": null,
    "support_url": null,
    "url": null
  },
  "business_type": null,
  "capabilities": {},
  "charges_enabled": false,
  "country": "US",
  "created": 1710150891,
...
hasty cove
ripe hatch
#

You mean this for cross-border payouts right?

hasty cove
#

yes

ripe hatch
#

super, thanks

#

we won't have all of these, likely EU+US for starters, yet to be set up

#

but in any case, for now, I'd like to figure out how to let people select their countries, any idea why it'd default to US?

hasty cove
#

the easiest solution is building a simple landing page on your site and then pass the correct country and tos_acceptance to the API based on what the user picks there.

ripe hatch
#

hmm

#

that'd convolute things a bit on our end, so contrary to what this and you above are saying, there is no way to let people choose their countries on Stripe's hosted page?

#

(convolute meaning mainly the flow for "oops I've selected the wrong country" and so on and so forth, but I'd really prefer to let you guys take care of this stuff, if it's already there)

hasty cove
#

it mostly works but the answer is also from two years ago before the receipient agreement existed

#

AFAIK what happens is if you don't pass it, we default to full , so then the user can only pick countries where the full agreement can apply, and that might only be a list of one (the US)

#

overall if I was building this I'd build a landing page

ripe hatch
#

that's weird, this would be the point of all that configuration business for Connect, no? (to limit the options for people onboarding and pick the right thing)

#

if I try w/ recipient-only tos, it throws an error (guess: due to defaulting to US):

dani@skynet ~> stripe accounts create --type=express --email="dani@brandties.com" -d "tos_acceptance[service_agreement]"=recipient                                                        (base) 
{
  "error": {
    "message": "The recipient ToS agreement is not supported for platforms in US creating accounts in US. See https://stripe.com/docs/connect/cross-border-payouts for more details.",
    "param": "tos_acceptance[service_agreement]",
    "request_log_url": "https://dashboard.stripe.com/test/logs/req_cKbtOHEy8UR1Mw?t=1710151422",
    "type": "invalid_request_error"
  }
}
hasty cove
#

well for example for me in the EU it works perfectly

image.png
hasty cove
#

again, the landing page

ripe hatch
#

well for example for me in the EU it works perfectly
as in platform account within EU?

hasty cove
ripe hatch
#

we're us-based thankfully

hasty cove
#

I'm just explaining what I said earlier "so then the user can only pick countries where the full agreement can apply, and that might only be a list of one (the US)"

#

whereas for me since all countries I support have the full agreement I can pick them in the onboarding

#

anyway, I don't want to debate the product much, neither of us can change it. The best option here is a simple landing page where the user picks their country and you pass the appropriate params to the API, I agree it's not ideal but I don't see another solution

ripe hatch
#

+1 on pragmatism

#

whereas for me since all countries I support have the full agreement I can pick them in the onboarding
this makes somewhat of a sense

#

we have a proper saas product built out, so asking for country of residence is not a big deal at all, however, how would you handle people coming back and selecting a different country?

#

Example:

  1. User promoted to onboard to connect.
  2. Selects Finland as country, a new account is created, stops onboarding
  3. Goes back to settings, selects Netherlands as a country, a new account is created, and starts over again
#

In this case, what would I do with the act created in 2)? Is it ok to delete it, or should I reject it, or take any other steps?

hasty cove
#

deleting it seems fine

ripe hatch
#

ok, that's cool