#mathon-bankaccount-tokens
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- mathon4266, 4 hours ago, 12 messages
- mathon4266, 19 hours ago, 5 messages
- matheus-ach-business, 22 hours ago, 3 messages
Hi 👋
Which API specifically are you referring to?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
We have a legacy Stripe JS v2 with Charges and Sources integration
Ouch.
So you are saying that the account_holder_type is defaulting to company when unspecified
But I don't really get your question
My question is: if we send "account_holder_type" as "company" to the create token function, is it somehow validated? What if the customer inputs an individual account number and routing number, but says that the holder type is "company"? Will the token creation fail?
Have you tested this?
Nope, I don't have a US bank account, but my next option is to try to find one.
THese bank account tokens, are they being created with Customer objects?
No, the tokens just need the bank account data. We create customers in another step on the back end and then we create a source for that customer with the token from the frontend.
Okay so you don't have knowledge of what kind of account will be created beforehand?
Wait...why don't you? If you are collecting account and routing numbers?
mathon-buy-button