#uncultured-swine_api
edgy steppeBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1382088848556818522
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
trail depot
Hi, to ensure I fully understand your question. Can you confirm you're saying that attempting to trigger issuing_authorization.request while using CLI with fixtures is not working but attempting it without the fixures, you can trigger issuing_authorization.request ?
If so, can you share an object id from your attempt please? How are you making that request?
quaint vessel
Sorry no, I have only attempted it with fixtures generated by the CLI. Is there a way to trigger it with an existing cardholder?
So far I am only running via the cli with stripe trigger --stripe-account=<connected_account_id> issuing_authorization.request.
The associated request id should be req_pUKjDwfrTKulJW.
trail depot
It might be possible that we do not support this event with fixtures but let me confirm this.
quaint vessel
If that's the case is there a way to trigger a test event of this type without fixtures? I have some cardholers/cards already setup so I'm not worried about having to use fixtures
trail depot
If you're simply looking to trigger that event, we document this here: https://docs.stripe.com/issuing/controls/real-time-authorizations#testing-webhooks-locally
stripe trigger issuing_authorization.request
quaint vessel
That command doesn't work because it requires the --stripe-account
Setting up fixture for: cardholder
Running fixture for: cardholder
Trigger failed: Request failed, status=400, body={
"error": {
"message": "You can only issue cards for your connected accounts. Please see https://stripe.com/docs/issuing/connect.",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_9ACV8J4SLWv9as?t=1749583997",
"type": "invalid_request_error"
}
}
testing this on my end, hang tight
quaint vessel
👍
trail depot
Can you try stripe trigger issuing_authorization.request --stripe-account= and pass a Connected Account that had issuing capability?
edgy steppeBOT
quaint vessel
Yep so that's something I had already tried, I just ran it again and received this
Running fixture for: cardholder
Setting up fixture for: card
Running fixture for: card
Trigger failed: Request failed, status=400, body={
"error": {
"message": "This cardholder has outstanding requirements preventing them from activating an issued card. Read more at https://stripe.com/docs/issuing/cards",
"request_log_url": "https://dashboard.stripe.com/acct_1RWj8kImh5vrGgbJ/test/logs/req_DLxyapICYjoLur?t=1749589195",
"type": "invalid_request_error"
}
}
Likely because the fixture cardholder has not accepted the bank ToS preventing them from having a card activated. We're using the Stripe SDK in our server and I noticed it is also missing the correct ToS acceptance object; it should have the bank name as a sub-key but does not
trail depot
I asked a teammate who was able to make stripe trigger issuing_authorization.request work. We're looking if an Issuing settings/config on your account and mine is off.
quaint vessel
Thank you!
Not sure if it makes a difference but we are using a sandbox environment for this testing. I know there's some differences between the sandbox and test account setups that have come up before for us
trail depot
My test account was using test account setup and not Sandbox. Since I was able to see what you saw I do not think there is a difference in that. We're looking, thank you for your patience.
quaint vessel
Not a problem, appreciate the assistance
delicate wraith
Hi hi! I’m going to be taking over for my colleague here. A bunch of folks have chatted and it sounds like this might be something specific to the account that can only be properly assessed & addressed by support: https://support.stripe.com/?contact=true
That said, you could also try creating a Sandbox 'from scratch' rather than as a 'copy of your Account' and see if the same issue occurs (per the screenshot)?
quaint vessel
I'll follow up with support then, we already have work and configuration done in this sandbox that I'd like to try and avoid having to recreate
delicate wraith
Totally fair! Sorry we couldn't get to the bottom of this here!
quaint vessel
Not a problem. I'm reaching out to support to see what can be done
delicate wraith
Ok cool. 🙂
quaint vessel
Figured I'd report back that I found a sort of work around. The Stripe CLI builds its fixtures from json files found here in the repo. They also include the url to trigger the event I need and so I was able to use postman to send the event to a test card I had manually created and activated
delicate wraith
Ahh cool, I'll pass that along as well. 🙂
quaint vessel
Actually as a quick additional note, this does not do as expected. It creates an issuing_authorization.created not a issuing_authorization.request as the command and the file name would imply it does
delicate wraith
Ok cool. I'd suggest sharing that with Support in that conversation as well.
quaint vessel
Done. Thanks for all the help today!