theprophet_75927

[fair ridge]

Can you share an example of where the problem surfaces? Dashboard, an API request?

[chrome agate]

See this connected account that has a card : https://dashboard.stripe.com/acct_1OjmF1QeI8IqJLrm/test/issuing/cards/ic_1OjmF8QeI8IqJLrmLkKosVXt

On this one for example, we were not enable to create a card : https://dashboard.stripe.com/acct_1OkPJMQV9jPPYjFv/test/dashboard

[fair ridge]

we were not enable to create a card
Is there an error? The UI broken?

[chrome agate]

No, we are executing automated tests to create cards.

Through the API

[fair ridge]

OK, so share an API request ID that failed please (req_xxx)

[chrome agate]

req_dI3NChFAsO8QGZ

[fair ridge]

Checking

Seems like acct_1OkPJMQV9jPPYjFv doesn't have the necessary capabilities in this instance as it hasn't been onboarded

There's a ton a of outstanding requirements before the account is verified and can use that kind of fucntionality

[chrome agate]

Well that's weird, we did not change anything to the code of the KYB in test mode and we have account that have cards with the same specific code.

See req_2FWi0Q80gPuvq7 for example

[fair ridge]

Are you onboarding the accounts?

(doesn't seem like it)

If you onboard the accounts using the test data (https://docs.stripe.com/connect/testing) then they will be verified and able to use the APIs as you need

[chrome agate]

Those accounts are "fake" automated accounts that we use to valide our integration in CI test

[fair ridge]

Using other data will likely trigger an actual manual verification and as such will be unverified

[chrome agate]

Why were we able to create cards before ?

[fair ridge]

Yeah I mean you just can't do that really. We don't recommend end-to-end testing at all for a number of reasons

You should be stubbing/mocking responses

[chrome agate]

Understood, but that still not answer my question 🙂 Why were we able to create cards before?

[fair ridge]

I don't know. I guess those accounts were verified somehow?

But unless you build that verification/onboarding part into your CI (which you shouldn't) then you'll face this predicament

[chrome agate]

We are using the same code for almost 2 years now

And it suddenly broke, without any change

[fair ridge]

Not sure what to tell you I'm afraid

[chrome agate]

Can I contact someone to have more information about what could have changed internally ?

[fair ridge]

Sure: https://support.stripe.com/contact