#koidestroyer

1 messages · Page 1 of 1 (latest)

odd sageBOT
fast slate
#

Hi there!

compact sequoia
#

I will - BTW, I understand those capabilities are added after KYC, but this is a test so I don't mind about KYC

#

req_9Bv3tqqtnvQ7jE

odd sageBOT
low pebble
#

Hey! Taking over for my colleague. Let me catch up.

compact sequoia
#

Actually, looking deeper into the code I see that the capabilities are requested in the test destination account creation process

low pebble
compact sequoia
#

I am, but I still get the errors?

#

That's one test customer

#

Hmmm, I see on the request this:
"capabilities": {
"card_payments": "inactive",
"transfers": "inactive"
},

#

so that should be it

low pebble
#

No the account should have transfers capability

compact sequoia
#

yeah, I mean that should be the problem

low pebble
#

Yes so you need to create an account that has the capability mentioned in the request error response

compact sequoia
#

Ok, got it

#

I am passing the right values

#

but the capabilities get set to "inactive"

#

because the KYC process has not gone through

#

so I need to simulate the KYC process or something

#

so the capabilities are activated

#

is that possible?

low pebble
compact sequoia
#

There is no easy way (single flag or some such) to tell assume this test account is verified automatically?

#

(I'm not really interested in testing the KYC flow, as the KYC is not done by my app, I just want a valid test account to do my integration tests 🙂 )

compact sequoia
#

would using express accounts change anything in this regard?

low pebble
#

Same you need to complete the onboarding of each account type you want to use (even in test mode)

compact sequoia
#

Seems like I can provide all the information on the creation request too, so I don't need to do several steps?

low pebble
#

Yeah you can prefill some fields when creating the Account, but for sure, at the end you need to have an active account at the end.