feat: support for Account token (only with phone attribute for Company business type) #1386
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
whybtech
force-pushed
the
feat/token_account
branch
from
5f16cc3
to
876c670
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR add partial support for creating Account Token. Only "compagny" is supported as businessType with phone attribute and TOS params.
Motivation
As requested in #842 connected accounts need an Account Token to initiate a Connect OnBoarding form.
Actually it is only a work around to onboard my users with stripe-react-native. I'm not sure I will have time to finish the full implementation with all attributes and Individual business type
Testing
Note: tested with example app for initiate with Individual but not in final version with Company
Documentation
Select one: