#josh-cli-issuing-connect
deft notch
digital siren
Hi 👋 can you share the full commands that you're using for the listening to and triggering of those test events?
covert eagle
Sure!
Sorry my wifi went out
Here you go:
stripe listen --forward-to=localhost:8000/authorization --events=issuing_authorization.request
for test events im just manually using the dashboard to create test authorizations on the card
i couldn't figure out how to trigger an event on a connected account via the cli
but i am using this form to create authorizations
digital siren
I believe you're seeing that because issuing_authorization.request is a type of event that must be subscribed to for them to be generated. Could you set up a webhook endpoint that is specifically listening for this event (it doesn't have to actually work), restart the listen command, and then run through your test steps again?
covert eagle
To confirm i would make the endpoint on connected accounts not on the platform right (as seen in photo)
left out the URL of my backend for the screenshot
Referring to the "listen to" section in the screenshot
digital siren
Correct, if the event is being triggered on Connected Account(s). Sorry for overlooking the Connect detail initially, in that case I think you'll also need to use the forward-connect-to parameter as well as forward-to
https://stripe.com/docs/cli/listen#listen-forward-connect-to
covert eagle
im going to omit the forwarding all together and just use stripe listen --events=issuing_authorization.request for now. Once i get the events to show up im confident i can forward them.
Actually you are correct i do need to forward it
evt_1MBmr52HYio6TkGSLNvzwkTo did not get forwarded when listening using the following command:
stripe listen --forward-to=localhost:8000/api/public/stripe/authorization --forward-connect-to=localhost:8000/api/public/stripe/authorization --events=issuing_authorization.request
did not show up in the listener either
it was sent to the webhook url in the dashboard only
nova jewel
@covert eagle let's chat here! I'm taking over the conversation and am catching up
covert eagle
Thanks no problem i just saw he went offline for 10 min and want to get this resolved, let me know if you have any ideas
nova jewel
hm, since you're forwarding all events to the same endpoint, could you try:
stripe listen --forward-to=localhost:8000/api/public/stripe/authorization --events=issuing_authorization.request
covert eagle
Same issue. I actually had that before and toby told me to add the other one
But docs say its redundant if its the same
even just running stripe trigger --stripe-account acct_1LS4gj2HYio6TkGS issuing_authorization.request in another tab through the CLI does not show the event in the listening tab
evt_1MBn282HYio6TkGSFIb0vVGz
any idea here @nova jewel
nova jewel
Hm, are you able to see that event in the other tab if you use stripe listen only? I wonder if we can dig through this piece by piece
covert eagle
Nope, i only get issuing_authorization.created
Are you able to get it to forward on a test connected account? Or is that a pain to set up
nova jewel
out of curiosity, if you use stripe trigger issuing_authorization.request, i assume this shows up in your listen window, correct?
nova jewel
got it
covert eagle
Are we potentially looking at a bug in the cli?
nova jewel
Not necessarily. Going to test this on my end but it may take me a bit
covert eagle
No problem i really appreciate it since im like 4 hours deep into this lol
covert eagle
Hey no rush just checking if theres an update
nova jewel
sorry, still digging!
I think I'll need to check with a colleague. While I do this, could you retry with the following?
stripe listen --connect-headers "Stripe-Account:acct_1LS4gj2HYio6TkGS" --forward-to=localhost:8000/api/public/stripe/authorization --events=issuing_authorization.request
covert eagle
yes sir one moment
nova jewel
and your trigger command:
stripe trigger --stripe-account acct_1LS4gj2HYio6TkGS issuing_authorization.request
covert eagle
upgrading the cli so give me one minute
did not forward
On Stripe API Version [2020-08-27], could I need to update?
Trying to brainstorm
Did that combination of commands work for you?
nova jewel
I have issuing set up in my test environment but not with Connect, so while I was able to use the CLI to listen for Issuing-related events, it's not a 1:1 comparison
I was digging through docs in case I missed something and landed on this flag: https://stripe.com/docs/cli/listen#listen-connect-headers
covert eagle
Yeah cause I can get platform issuing events on my account as well, just not with connect
glass magnet
josh-cli-issuing-connect
I'd recommend contacting support otherwise and they can help you debug this directly
What I do when the CLI doesn't fit my purpose is trigger the Event with my own actions/code otherwise, such as creating a payment on that account with one of its issued Cards
covert eagle
The issue isnt getting stripe trigger to work
its forwarding the issuing_authorization.request event to my localhost so I can create rules to actually accept or decline the authorization
which is like an extremely integral part of the issuing process
the events also DO send, they just only send to my real server and wont forward to localhost so i can do any sort of testing without pushing every commit to a real server and then waiting for it to build
glass magnet
you can always use ngrok or similar otherwise
(I'm looking into it separately but sadly CLI + Test mode + Issuing + Connect is really painful to test)
covert eagle
Totally get it
I definitely can't be the only one with this issue if its a bug but i feel like i've tried everything at this point so im unsure why it doesnt forward
Ill ngrok for now, just thought stripe would have some tools for this
glass magnet
So just to clarify you can forward the normal Event just not the Connect one?
covert eagle
yes exactly
glass magnet
Do you have an example Event I can look at that you successfully triggered it the problem is just the forward bit?
covert eagle
evt_1MBn282HYio6TkGSFIb0vVGz
i sent 2 in here
let me double check thats the right one
evt_1MBo8K2HYio6TkGS24jyZruc
thats the last oen
Theres a bunch to this webhook: we_1MBmncC7t6MTuEUX977bxdtm
glass magnet
https://stripe.com/docs/cli/listen#listen-forward-connect-to did you use this?
(sorry I'm guessing because my own Test accounts can't use Issuing + Connect right now adn neither do my 2 colleagues' currently around 😦 )
covert eagle
stripe listen --forward-to=localhost:8000/api/public/stripe/authorization --forward-connect-to=localhost:8000/api/public/stripe/authorization --events=issuing_authorization.request
that was from the first person helping me
no luck
i tried pretty much every combination of commands and headers involving connect
glass magnet
yeah I see that this Event was never sent to the CLI, I'm just unclear why right now but looking
Can you create a Customer on that connected account and see if you get the customer.created Event?
glass magnet
yeah that one went straight to the CLI
covert eagle
its literally only issuing_authorization.request events on connect
everything else works
glass magnet
so clearly it's missing some weird configuration about that Event. So for now, I'd recommend ngrok. But I'll see if I can figure out what's causing it
covert eagle
im a sole developer full stack for like 200 connected accounts on a custom payments integration i've used a lot of stripe but this one just doesnt seem like it has a solution for me lol
Thank you for looking into it
glass magnet
what did you configure here https://dashboard.stripe.com/settings/issuing/authorizations at the bottom?
Do you have a real URL?
glass magnet
no I was just confirming since my other account has nothing there. So it really feels like a bug on our end at this point. I'd recommend flagging to our support team, but I'll also report it internally