#kewn_unexpected

1 messages ¡ Page 1 of 1 (latest)

honest inletBOT
echo lionBOT
#

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.

honest inletBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1250735455847059497

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

noble bluff
#

Hi
Yes when using Stripe hosted onboarding, terms of acceptance should be handled by the flow.

rancid swallow
#

With "the flow" you mean that it's the responsibility of Stripe?

noble bluff
rancid swallow
#

Okay, that's not what we see happening; especially in our Vev Inc (acct_1NmlQHKo27ACZLjH) account we have a lot of users onboarding with Stripe Custom, where they do not have the terms accepted when they complete the onboarding.

#

When we direct them to the onboarding again, they do see the option to accept the terms

noble bluff
#

Okay, that's not what we see happening; especially in our Vev Inc (acct_1NmlQHKo27ACZLjH) account we have a lot of users onboarding with Stripe Custom, where they do not have the terms accepted when they complete the onboarding.
Is this isloated case or this is recurring for multiple accounts ? if so could you please share a more couple of examples ?

rancid swallow
#

It's not an isolated case, it seems to be happening for almost all connected accounts in the before mentioned "main" account

#

I'll look for some examples

noble bluff
#

Could you please share the onboarding flow for these accounts? and if possible what are the key differences ?

rancid swallow
#

It's fairly difficult to share a single onboarding flow; the problem we see is that a lot our customers go through the connected onboarding for a custom account, and then end up with an account for which the terms are not accepted.

feral garden
#

what does your code for onboarding those accounts look like? are you using /v1/account_links or something else? Like for that account I don't see any incoming API requests from the onboarding, (just a couple of requests for setting their payout details).

rancid swallow
#

We use the Java SDK to create an account link;

val params = AccountLinkCreateParams.builder()
            .setAccount(accountId)
            .setRefreshUrl(addAccountLinkRedirectProxy(refreshURL).toString())
            .setReturnUrl(addAccountLinkRedirectProxy(returnURL).toString())
            .setType(type)
            .build()

        return@withContext AccountLink.create(
            params,
            buildRequestOptionsForGateway(null, paymentGateway)
        ).url
#

For the full flow; when a user want to enable payments on our platform we create a payment account, and then create an account link for that account and redirect the user to it

feral garden
#

maybe the user left the account link flow in the middle/closed the tab?

rancid swallow
#

That's probably part of the incomplete accounts, but we've also been able to reproduce this, where we finished the onboarding, were redirect to our application, but the payment account wouldn't be available to use, until going through the onboarding again, where then a checkbox to accept the terms showed up