#Fran-express
1 messages · Page 1 of 1 (latest)
because you need to have a valid payout account in order to be onboard an Express account. You can't create accounts without it being linked to a valid external account.
and what do you suggest to create a valid external account? Because we have the cvc, expiration date and card number in different inputs, and what I found in the docs is that you only need the card number to create the token id
I was using this to pass the token: https://stripe.com/docs/js/tokens_sources/create_token?type=cardElement
I don't want to transfer sensitive information like the card number or even the cvc to our backend
So you shouldn't be doing that no matter what you collect. The whole point of stripe.js is so for your customer's info to go straight from the client to Stripe.
That being said, I don't understand your question. You can't authorize a card without expiration date and CVC. What are you trying to do?
We were creating an intuitive way for our sellers to register in our site, and only use the stripe setup link for stuff like verification of the account.
The question is basically if there is a way for us to have the form to fill in the bank details or card details and send them to stripe
like using the stripe elements
If you're talking about a client-side-only option, then yes, but it is in beta: https://stripe.com/docs/js/financial_connections
Otherwise, I would recommend just following our docs on whatever type of account (Express, Custom, or Standard) you are onboarding: https://stripe.com/docs/connect/accounts
Hey, I was thinking that in our checkout process we use the same system of stripe elements (https://stripe.com/payments/elements) why it doesn't work here? Because the data we collect is the same, card number, cvc and expiration date, then that's tokenized and the token is sent to the backend...
sorry I didn't point that out, I was focused on solving this issue and I forgot about that xD
but it's basically the same thing we use, and the test cards are correctly charged
Ah, because the product is designed to take payments rather than create payouts. The infra is vastly different when it comes to pushing money to a bank, so we're still building out easier client-side options for that
Since you need a valid payout account to onboard connect accounts, our pay-in products aren't really applicable