#_durrell
knotty hull
light adder
Stripe CLI by default doesn't run the issuing authorisation request in connected account: https://github.com/stripe/stripe-cli/blob/master/pkg/fixtures/triggers/issuing_authorization.request.json
You'd need to create a new fixtures for your own use case: https://stripe.com/docs/cli/fixtures, i.e. change it to connected account and create financial account accordingly
Alternatively, you can create the authorisation via Dashboard:
Logging in to the connected account > Go to issuing page> select the card > Click Create test purchase
Or use API to create test authorisation with Stripe-Account header as connected account: https://stripe.com/docs/api/issuing/authorizations/test_mode_create
The last one using API is probably the easiest
lost terrace
We've tried the last one. The request event doesn't come through.
light adder
Can you share the request ID (req_xxx) of the issuing authorisation? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
It might be an issue with your request or configuration of the webhook endpoint
If the API approach doesn't work, CLI or Dashboard likely won't work too because it uses same API under the hood
lost terrace
The request is: req_RmuEw1M6oZcjIW
the authorization is created in the approved state
light adder
Can you try with this set of parameters in the API to see if it works? https://stripe.com/docs/issuing/testing?testing-method=with-code#create-authorization
lost terrace
sure. The ruquest ID with that curl is req_gqKBQ9VOO2Tue4
I had to change the authorization_method to online because it complained about "chip" being invalid for a virtual card.
It's the same thing. It creates the authorization in an "approved" state and the authorization request event doesn't come through.
light adder
This is indeed strange! Checking why issuing authorization is approved immediately
light adder
I'm unable to reproduce the behaviour with the same request with automatic approval
I just noticed that the CLI fixture uses different endpoint for authorisation. Can I suggest you writing to Support https://support.stripe.com/contact with the request ID, req_gqKBQ9VOO2Tue4, so that they can check with the relevant team why issuing_authorization.request wasn't created and ended up with approval immediately?
light adder
If you make the request directly on the platform account, does it work?
lost terrace
I'm trying that right now.
It doesn't look like this is going to be resolved tonight. I'm getting errors regarding how the platform account needs to request access to Issuing and how that can't be done via the API. Can you confirm whether the request you made was for a connected account?