Relax need for dob with full name connect account params #1539
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
yuki-stripe
approved these changes
Apr 8, 2020
|
No problem, thanks for taking a look and approving! Is this something you could cut a new minor release for? Or is there a planned release coming up this could be included in? |
|
Sorry for the delay! We're planning to release an update very soon, we'll get this into it. |
|
No worries, thank you for getting this merged! I'll keep an eye out for the next release 👍 |
|
It's out as v19.1.0! |
|
🥳 Update works as expected, I just validated by updating the pod to the latest release. Thanks again for the quick turnaround! |
davidme-stripe
pushed a commit
that referenced
this pull request
Oct 29, 2022
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
The required information to enable transfers and payouts for custom connect accounts has been updated. For the first threshold, only the first name and last name are required. Previously date of birth was also required for this first threshold.
https://stripe.com/docs/connect/required-verification-information#individual-transfers-us
The Stripe API and the Stripe Android SDK allow for the relaxed requirements when tokenizing individual account params. iOS has a subtle error which prevents this from working. A STPDateOfBirth object is always constructed when submitting STPConnectAccountIndividualParams. This results in a dob of 00/00/0000 being sent to the Stripe API, which results in a rejected tokenization request.
Motivation
We are updating our KYC flow to only collect the minimum required information for each threshold. The current iOS SDK does not support the updated flow.
Testing
This was tested by providing only first and last name fields to STPConnectAccountIndividualParams and attempting to tokenize. With this change the operation succeeds, without it the operation fails.