#daimyotoan-account-link
1 messages ยท Page 1 of 1 (latest)
@frank widget the account link is one time use only, after your user clicked it or the link expired, your user will be automatically redirected to refresh_url
The recommendation is that in your refresh_url, you should regenerate the link and redirect your user there
see the comment here https://stripe.com/docs/api/account_links/create?lang=go#create_account_link-refresh_url
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
right after receiving the account link, user click on it (1st time) but still redirect to refresh_url
is the link need to be opened from the same device where we call api to generate it ?
Do you have an example? you can create a link and I can test
Yes, it was redirectly. what is your code to create this?
Let me test it on my own account as well
Yeah, I am not able to reproduce the issue using my testin gaccount
if you need to have the test secret key, i can provide it
what is the expired_at?
can you paste that value here?
i think that might be a timestamp before now
meaning it is possible you are creating an expired link
is it mandatory to input expired time ?
i thought it is optional and Stripe will auto give it a number
it is optional
{
"object": "account_link",
"created": 1631253451,
"expires_at": 1631253751,
"url": "https://connect.stripe.com/setup/s/W2RqGQXvnfQw"
}
this is new response
expires_at is still valid
yeah, strange, let me check. and test again since your account is a standard account acct_1JXMmxRQaJyZM2sF
yes, it's standard account
even more strange if i open it using my web browser (on same machine call api creation link), then it works
but if i send it to you or other devices and open it, then it's error
can you create the link with you account and send here
maybe if i open it (different machine) it will get error
i got redirect to example.com ๐
let try to create the link in 1 device, then open it in another device
i guess you will get the error
Sorry, I was pulled into another thing, Let me check with the team.
yeah, I can reproduce this issue with my phone and with one my teammate, but I could not find the rational or design doc on why we are doing this. and this is new to me too. I will need to check with the owning team which is currently offline
do you mind writing to our support so that you will get a definitely follow up
or you can come back to this channel and my team will follow up with you and you can point them to this thread
:question: Have a non-technical question, account issue, or need one-on-one support?
We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact
^ this is the support link
@frank widget it seem that if you wrap the url in a link like
<a href="https://connect.stripe.com/setup/s/xxxxx"> Click here to onboard</a>
and you click it, it will work regardless of the machine
I guess we have some clever ways to prevent user from using the raw URL
ok. what is xxxx value ?
is it connected account id that we want him/her to go to onboard flow ?
or that is the uRL generated from account link create api,
that is just a place holder
e.g. "url": "https://connect.stripe.com/setup/s/VoqXbsYBwa4X"
i don't get your point
how can we redirect user to open the onboard link and complete their info ?
that's what we want
I mean do you have a website?
you can simply create a page on your site which have a link button allowing your connected account to click on
instead of sending them the URL directly, you send them your web page containing a link instead.
Does that make sense?
no. our user is using mobile app
and from mobile app, we make a button "Complete Stripe info", from that button we will create onboard link then open the web view for them to continue
that's our flow
yup, that should work; i think as long as it is not direct link click, it will work since the link generate and link consumption is on your users' phone which running your application.
You should test it and let me know if that does not work
I think here the only thing it does not work is when you directly message your user the link
i've tried this. let me give you the detail flow
- our user is using app and click the mentioned button
- that calls our BE api, where it will call Stripe api to create account link
- the created onboard link will be returned to our user app.
- user app open a webview with that link
at the step4, we get the error as i mentioned
yeah... sorry, there must be something I am missing here. do you mind writing in and when we can follow up with you once we get an answer for you?
or you can hang out here and I will update you as soon as I have some answers
๐ค strange ...
sure