#Zen-testing
1 messages Β· Page 1 of 1 (latest)
hi! well for the individual you have to use specific values like 1901/01/01 DOB and address_full_match,SF,USA to verify.
can't I do it with FR as the country ?
you can yes
I was just giving an example. It's any address but the line1 has to be that magic value address_full_match
for the external_account, as implied it means you need to call https://stripe.com/docs/api/external_account_bank_accounts/create for example to create the bank account with the test payout numbers (from my earlier link, they should be there too). Same as you probably do in the actual code where you onboard users.
if you think it would help and have specific questions about it then sure
thx a lot π gimme 10s
const stripe = new Stripe(
'sk_test_XXXXXXXXXX',
{
apiVersion: '2020-08-27',
}
);
const accountResult = await stripe.tokens.create({
account: {
business_type: 'individual',
individual: {
first_name: 'First',
last_name: 'Last',
address: {
line1: 'address_full_matchβ',
city: 'NANTES',
state: 'Loire-Atlantique',
postal_code: '44200',
country: 'FR'
},
dob: {
day: 1,
month: 1,
year: 1901
},
id_number: '1234567890000',
email: 'email@test.fr',
phone: '000 000 0000'
},
company: {
name: 'KampoyTest',
tax_id: '000000000',
address: {
line1: 'address_full_match',
city: 'NANTES',
state: 'Loire-Atlantique',
postal_code: '44200 ',
},
},
tos_shown_and_accepted: true,
},
});
exec(
`stripe accounts create \
-d type=custom \
-d email="email@test.fr" \
-d country="FR" \
-d "business_profile[mcc]"=5734 \
-d "business_profile[url]"="www.fakeurl.com" \
-d "capabilities[card_payments][requested]"="true" \
-d "capabilities[transfers][requested]"="true" \
-d account_token=${accountResult.id}`,
(err, stdout) => {
if (err) console.error('EXEC ERROR', err);
console.log('STDOUT', stdout);
result = stdout;
}
);
so that's how i'm trying to do it
first, about the person issue, i tried different id_number, 000000000, 0000 and now 1234567890000, but I'm always ending with Provided identity information could not be verified
is there something you can spot i'm missing ?
just in case, the exec(blabla) at the end uses the stripe.exe that is at the root of my project π
And for you to have all the data, here is what is being created :
sorry for the mega post... π¦
that's here that I can see my issues :
- on the individual : verification_failed_keyed_identity
- in currently_due : external_account
000000000 is the correct value for the ID number
ok, i'm replacing and let you know π
you also have a space at the end of the postal_code which might matter
wooow good eyes π€
overall the way it works is if we can't verify the account from the supplied information we need to ask for a document, which is happening here. So in general you must use the exact testing information we expect
yes sorry... that's what i'm trying but new dev here ^^ everything is complicated xD
can I ask overall what you're trying to do? Custom Connect is probably the most difficult thing you can do in Stripe
yeah of course !
I want to code an E2E test with Cypress, which does the following ;
- Cypress goes to my localhosted website (which sells vegetables mostly)
- Cypress asks node to create an test account that can receive payments => that's why I need a custom I believe
- After that, I link this account to my seller in my database (firebase emulator here)
- Cypress simulates an order on the app, using testing data for the payment by card (iframe in the app)
- In the end, I want to check the balance of the newly created account
Ok, I've launched it again, with the new id_number and corrected postal code, still verification_failed_keyed_identity π¦
that's fair, but will you be using Custom accounts for your actual business? Putting aside the testing side of things. Custom is the most complicated option and requires you to build a large onboarding experience yourself. Unless you have a large development team experienced with KYC and marketplaces you should not use Custom. I usually suggest using this guide : https://stripe.com/docs/connect/collect-then-transfer-guide as a fully worked example of creating and onboarding Express accounts and splitting a payment with them for payouts.
do you have the account ID acct_xxx where that happened?
sure π
acct_1Legxu2QtycoqJca
oh, the team is smalled and not experienced in KYC ^^
is there a way to do the flow expressed above with created express accounts ?
as far as I can tell it's the address that our system doesn't like
not sure why though. Maybe use Nantes instead of NANTES
well no , with Express you can't do this sort of automated test since you need to manually onboard through the Express hosted onboarding pages and can't upload KYC through the API
that's what i thought after some research yup... so custom is the only way for testing ?
I personally just test by creating Express accounts manually. There's no great answer here
tried with Nantes, same ^^
ok that's interesting, so you're doing test yourself ? Could you share your test flow with me ? π
so you start by creating a test account manually in stripe.com ? and then you do all your tests on this one, never deleting it ?
no, I create an account whenever I need to debug something
unfortunately I have no idea why your account is not passing the programatic testmode verification, I don't see what's wrong
try removing the company: {.... } hash entirely from your requests
you shouldn't need that since you say business_type: "individual"
so you don't need to be passing details on a company, since you say you are onboarding a single person. That might be it(I think our internal systems are complaining about the company business address for some reason, that's probably a symptom)