#videovillain_api

1 messages · Page 1 of 1 (latest)

tacit fiberBOT
#

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

📝 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.

fathom galleon
#

Also, it seems that our Connect Users are being asked to fill out some pretty strange forms that don't seem like they are relevant.

#

Are we using the right service for Customer to Customer connections?

upper glen
#

Hi! Can I check what are these forms they're being asked to fill up?

fathom galleon
#

just a sec please

#

btw, do you have any Japanese speaking staff?

#

I have to make make a new account to get the form request to pop back up, please wait.

upper glen
fathom galleon
#

No worries, like this is fine then.

While I make the next account to show you the form, can you tell me if this correct to have the shortest, quickest onboarding experience?

accountOnboarding.setCollectionOptions({
  fields: 'currently_due',
  futureRequirements: 'include',
})

And are there any steps I can catch and bypass here?

accountOnboarding.setOnStepChange((stepChange) => {
  console.log(`User entered: ${stepChange.step}`);
});
upper glen
#

If you only want to collect the information that is due immediately, you can just indicate 'currently_due' and not collect those that are eventually due and future requirements.

#

And are there any steps I can catch and bypass here?
What do you mean by above?

fathom galleon
#

I mean, things like the form asking if they use encription and such for handling payments, etc. I'm trying to get back to the request forma gain but it is taking time.

#

It is questions that are completely unrealated to the Connected Account, something I feel like we (PwR) is supposed to be answering, but only once

#

not every new connected account

upper glen
#

I’ve shared an update regarding the Climate Change section above. What would help is to provide details / steps of how you are onboarding the connected accounts and screenshots of the fields that you would like to check on. I understand this may take some time, so please feel free to update this thread whenever you have the information.

fathom galleon
#

I'm putting that together now

#

thanks for the help

#

Okay, so I've started the process. and the first part that we get to that I am concerned about is here:

image.png
#

our connected accounts are going to be coaches, they will connect over VC with the other users and teach them a skill

#

they will not have a website

#

at least, not for the most part

#

in such a case, first, what industry should we suggest to them to select (in our user manual for example)

#

Consulting Services? Other Digital Goods?

#

can we have them put in OUR business web address?

#

and then we hit this:

image.png
#

but this is handled by stripe

#

why are they required to answer this?

upper glen
fathom galleon
#

they won't collect anything, neither will we, it goes through you

upper glen
#

in such a case, first, what industry should we suggest to them to select (in our user manual for example)
We will not be able to advise on this. You will need to determine the most appropriate industry based on the services provided.

fathom galleon
#

This part specifically makes me feel like we are maybe not using the right stripe service to connect customers to customers
#1326361867270230027 message

#

right now they are "standard" type, is that the wrong selection?

#

then we have the final page to submit:

image.png
#

but after it is done, it isn't finished

#

we get the thanks, i redirect the user to allow them to continue using the app

#

but when they try, they get this;

image.png
#

but then, if they try once more

#

then they finally refresh to this page:

image.png
#

which is the form i'm most concerned about

#

it has nothing to do with them IMO

upper glen
#

Lets look at the account type first. I will need your help to describe your business case and how you plan to use Connect.

fathom galleon
#

so we may need to change from "standard" to "express" or "custom"?

upper glen
#

Have you had a chance to go through it?

fathom galleon
#

we did it from the begining yes

#

and we decided Standard at the time

#

so that liability stays with stripe for negative accounts, etc.

#

since they don't store any information, and we don't either (though we do use encryption) but in the end, it is still Stripe handling it all...

#

which is why something like that ISA form is completely unnecessary, or so we thought by choosing to have Stripe be the liable party.

#

The questions on that form really do seem to be directed only to us (PwR) and not connected accounts

#

things like database storage and SQL injection protection, etc.

upper glen
#

This appears outside the scope of an integration issue and I wouldn't be able to advise when and why are these questions asked. I recommend reaching out to Stripe support for assistance with onboarding-related queries. You can contact them here: https://support.stripe.com/contact.

fathom galleon
#

Okay, we have done that and are waiting for a response.

#

However, there are some futher things I think you could help with

upper glen
#

What are the further queries?

fathom galleon
#

the transition that starts up here: #1326361867270230027 message

from Review -> we redirect to the part of the app the user should now be able to use
However, when they attempt to use it, our backend sees there is more to be done so we redirect back to onboarding
But then it just says submitted and sits there
only if they go back or refresh, does it change to the new set of things necessary

#

There must be a better way to handle this flow. and based on the responses from Stripe as well as the embedded responses during the onboarding process, I don't know when they are "finished" and in a proper review state or complete state.

#

For example, we have a live account that has completed everything, but is still considered restricted so we keep redirecting them to the onboarding page, but since everything is complete and in review, it just asks for them to review and submit over and over

#

I have no way of knowing they are "in review" by Stripe still

#

so I can't send them a message that states that, I can only keep redirecting them to the onboarding in and infitinte loop of reviewing and submitting the info we already have

upper glen
fathom galleon
#

oh good, requirements.disabled_reason is what we need.

the top is talking about accounts made with the API though, but will that work in the webhooks for any type of account, even made through embedding or stripe hosted?

upper glen
#

Yes, it will be for all account types.

fathom galleon
#

but also, we don't get requirements.disabled_reason when we retrieve a connected account

#

so there is a separate way to get there it seems that we need to implement?

#

the KYC?

upper glen
#

Not all accounts might be disabled. They may just not be verified but are pending requirements. Hence why you don't get requirements.disabled_reason for all accounts.

#

I am not sure what do you mean by: so there is a separate way to get there it seems that we need to implement?