#morteza_api
jolly stormBOT
đ 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/1282714733878706217
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
little wadi
Hello
Can you provide a lot more details here? What do you mean by "validate" in this case?
jade lintel
yes sure, there is an issuing sample app , in that users register and onboard onthe stripe but in our platform we have our own website and we ourselves register users and create connected account for them on stripe we now need to develop an api to register account ids to created users, I want to make sure that only corect account ids are registered
at least I wanna make sure that account id is acc_...
does account id and card holder it have specified lenght and pattern
little wadi
Our object IDs have static prefixes, yes.
We don't guarantee a static length.
We talk about this here: https://docs.stripe.com/upgrades#what-changes-does-stripe-consider-to-be-backwards-compatible
jade lintel
ook , is this kinda registering users and registering account ids fine with stripe ?
little wadi
I don't know what you mean by that, sorry
jade lintel
ok, thanks Bismarck
little wadi
Sure, if you want to explain more about what you mean then I'm happy to help
jade lintel
ok lemme explain
Imagine you are a restaurant owner and I'm a company providing food ordering platform, you ask me to issue a card for you, I create a user for you with a password, with a two factor passcode, I create a connected account for you on the stripe panel, then I bind userId and accountId from the two steps and I give you user id , paasword and two factor passcode and you login with these data on an app that you can see your cards, transactions, ...
the point is I create user for you not you uourself
little wadi
Sure
little wadi
Yeah that's totally normal
In your own database you would just store the Account ID of your user beside whatever login information you maintain for them
jade lintel
because we show cards on the app, we need to store cardholderIds as well
little wadi
If you want to have a fallback connection then you could even set metadata on the Connected Account with the specific user info when you create that account: https://docs.stripe.com/api/accounts/create#create_account-metadata
Yep cardholders would exist on the Connected Account
Those are objects as well: https://docs.stripe.com/api/issuing/cardholders/object and you can store that in a similar fashion
All of this is normal and is really just up to you to maintain your database with the data you need