#dinlashades
half helm
sand cave
Hello! Can you share a screenshot of what you see after you press this button?
azure flint
Sure
one sec
First, Uset test document button changes to loading state, than button disappears and shows Saving...
sand cave
Did the Use test document show up when you clicked on Edit for Professional details or for Personal details?
azure flint
On the final screen like on screenshot I get "Verifying"
Personal
After clicking on Edit in Personal details
Use test document > Saving... > Verifying... > Information needed
sand cave
So no matter how many times you go in there and press that button it still says Information required?
azure flint
Yep
sand cave
Are you sure there's not other information needed that's not the test document?
azure flint
Yes, that's the only part
For everything else I use test data
01/01/1901
address_full_match
Valid state and postal code
And valid city
all zeros for SSN
sand cave
Can you give me the ID of the Custom account so I can take a closer look?
sand cave
Looking...
azure flint
If it helps this is how we setup custom account:
const account = await stripe.accounts.create({
type: 'custom',
country: 'US',
default_currency: 'usd',
capabilities: {
card_payments: { requested: true },
transfers: { requested: true },
us_bank_account_ach_payments: { requested: true },
},
additional_verifications: {
document: {
apply_to: ['representative'],
upfront: [{
disables: 'payouts',
}],
require_matching_selfie: true,
requested: true,
},
},
metadata: {
initiator: 'studio-dashboard',
userId: userId.toString(),
sourceIp: req.getClientIp(),
},
settings: {
payments: {
statement_descriptor: user.companyID.slice(0, 22),
},
payouts: {
debit_negative_balances: true,
},
},
});
Yeah, I was just looking at that... I wonder if it's the require_matching_selfie bit?
azure flint
I'm almost sure that we have started seeing this kind of behavior when we updated onboarding links to prepare for Apr 16th requirements change
sand cave
Can you try without that and see if you see the same issue?
azure flint
const accountLink = await stripe.accountLinks.create({
account: accountId,
type,
return_url: returnURL.toString(),
refresh_url: refreshURL.toString(),
collection_options: {
fields: 'eventually_due',
future_requirements: 'include',
},
});
When we added collection_options
I will try to disable the matching selfie first
Stand by
Removing matching selfie didn't help
Trying without collection_options
The first difference is - only the last four of SSN are needed (which is correct without future requirements)
But no difference even without collection_options
It worked before, for sure
Somewhere around Jan 30 it stopped working
sand cave
I can try to reproduce. In the meantime I recommend you reach out to Stripe support and report it as a potential bug: https://support.stripe.com/contact/email
azure flint
Roger
P.S. our live system has fresh connected accounts
So production is not affected
This is just in test mode
Thanks for assist @sand cave ๐ค
sand cave
I'm guessing the test document doesn't meet some of the requirements.
But it should. ๐
azure flint
Ya ๐
I've also tried downloading the image from the doc
This one
But when I try to upload it "image is too small"
ยฏ_(ใ)_/ยฏ
sand cave
Yeah... I think it wants an actual ID there.
azure flint
Hmm
sand cave
Ultimately you'll need to work with Stripe support on this one, as I think it's related to the additional verifications stuff you're using, which isn't publicly available.
azure flint
Roger
I will try to use test file tokens too
But anyways - ultimately I wanted to make sure that setup is correct
The live onboarding works as expected with all these
sand cave
As far as I can tell you're doing things correctly, especially if things are working in production. I think you're running into a test mode bug.