#Durrell
1 messages ยท Page 1 of 1 (latest)
Hi, this, https://dashboard.stripe.com/settings/issuing/authorizations is what it's referring to. You can set your authorization endpoint directly there.
Thank you for that. The bottom of that page has this section. "Connect authorization webhook endpoint"
That section is pre-filled with, "https://stripe-cli-internal-placeholder.stripe.com"
Can we pre-fill that with something that will let us trigger the issuing_authorization.request event via the Stripe CLI?
currently stripe trigger issuing_authorization.request
sends us: issuing_cardholder.created, issuing_cardholder.updated, issuing_card.created, and issuing_authorization.created
but not the issuing_authorization.request
when you trigger issuing_authorization.request via the CLI, you are not seeing this event?
Correct. We are not seeing it. We are seeing the others listed above though.
Let me try to reproduce this on my end.
thank you
I was unable to reproduce this on my end, I'm getting issuing_authorization.request event
Can you share an example event id here so I can further investigate this? It should start with evt_1111hjkhf
evt_1LzpxJJRbJh8dLdCF10mAySj
evt_1LzpxKJRbJh8dLdCWiFCCzZ1
evt_1LzpxKJRbJh8dLdCh8nMn5YE
evt_1LzpxMJRbJh8dLdC4rAuYqpb
Can you add this, https://example.com/my/webhook/authorize test endpoint here, https://dashboard.stripe.com/settings/issuing/authorizations?
Then, once saved try triggering the CLI again?
that should go in the "connect authorization webhook endpoint" section correct?
You can add to both for testing purposes
If I remove that test webhook endpoint, I do not receive that event which I think is expected.
we are only using Issuing with connected accounts.
For testing purposes, I just want to rule things out.
i think there is a flag we need to add to our request in the CLI to specify this is for a connected account right?
yeah, the flag is: --stripe-account=acct_abc123
I added the url you specified above to both places.
Great, I can look on my end once you have confirmed that you've triggered the event: stripe trigger issuing_authorization.request
I can confirm that I triggered the above event.
evt_1LzqP0R8qpTsTbw80P7T37AU
I'm getting help from a teammate now, thank you for your patience.
Hi @ivory quiver I'm taking over, give me a sec to catch up.
Have you added a authorisation webhook endpoint at https://dashboard.stripe.com/settings/issuing/authorizations ?
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
pgskc told me to add https://example.com/my/webhook/authorize to both the connect and the regular options there.
so i added that in test mode. strange when I visit that page again the url seems to not have saved.
hmmmm. whenever I refresh the page it seems get erased.
even though I clicked the "save" button.
The issuing authorsation webhook endpoint is to be configured in a separate page.
what page?
Use the link that I posted earlier https://dashboard.stripe.com/settings/issuing/authorizations
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
yeah, that's the page I visited. There are two input fields in that page. One for "Authorization webhook endpoint" and another for "Connect authorization webhook endpoint"
pgskc asked me to enter https://example.com/my/webhook/authorize into those input fields on the link you posted earlier.
It looks like for test mode the default for the "Connect authorization webhook endpoint" is https://stripe-cli-internal-placeholder.stripe.com/
OK, I took a closer look at evt_1LzqP1R8qpTsTbw80goXB05N it says issuing authorization was created and declined due to insufficient funds
You current issuing balance is 0, can you top up some and try again?
I topped up a connected account and ran: stripe trigger issuing_authorization.request --stripe-account=acct_1LsqXMR8qpTsTbw8
You should top up your issuing balance
I still don't see the issuing_authorization.request
here is one of the events from that trigger: evt_1LzsWaR8qpTsTbw8rUOVIczl
Why would the platform account need an issuing balance?
This is supposed to be an authorization request for a connected account.
...so I topped up the issuing balance on the connected account.
here is the issuing_authorization.created event id: evt_1LzsWdR8qpTsTbw8TbW5yaL5
it says approved: true this time.
I also got a issuing_authorization.updated event: evt_1LzsWdR8qpTsTbw8IZUJD2rl
which was also approved now that the issuing balance on that account is greater than 0.
Let me check again. one sec
I've checked your account and your Connect authorisation endpoint is still empty.
in live mode it is empty. in test mode it is set to the default which is: https://stripe-cli-internal-placeholder.stripe.com/
Do we need to point live mode to something?
for the Stripe CLI which we logged into using our sk_test_ key?
You are right, the URL is set in test mode.
When you run the Stripe CLI command, did you use the --stripe-account flag?
yes
i pasted the exact command above
I'm Durrell. I'm just on a different computer right now that is using a different discord user
OK. I can see that you did pass the flag.
Hmm. I can't figure out why it doesn't send the event. Can I suggest you to create a issue in https://github.com/stripe/stripe-cli so that Stripe CLI team can look into it?
ok
I wonder why pgskc was getting the event earlier. It seems like I must have something configured differently.
are you able to get the event from the CLI?
I didn't because my test account is disabled. Let me try with another account.
If you just use the issuing card to test a charge, do you get the issuing_authorization.request event?
how would I use a card in test mode? Is there an API call I can make or another CLI trigger?
It doesn't look like we can do that with cards issued to connected accounts.
...oh wait. I wasn't in test mode.
You can, but you need to write some code
what code would I write? The docs linked above show a link to this page https://dashboard.stripe.com/test/issuing/cards
but that page only shows cards issued to the platform account.
https://stripe.com/docs/issuing/testing?testing-method=with-code this shows you the code, remember to specify the Stripe-Account header so that you can make API call on behalf of your connected account.
ok. I'm going to bed. thank you for your help
I suspect the bug with the CLI is it doesn't trigger this event for connected accounts. I'm going to topup the platform account to check my theory.
The code you reccommended did not trigger the issuing_authorization.request event. Here are the events that were triggered:
[evt_1LzuDXR8qpTsTbw8r3fk4fdz]
[evt_3LzuDVR8qpTsTbw801YB2C4e]
[evt_1LzuDYR8qpTsTbw8TgbzpUp9]
[evt_3LzuDVR8qpTsTbw80NYyqNbE]
[evt_3LzuDVR8qpTsTbw80SsG6S7I]
I'm going to bed for real this time ๐ Hopefully someone will have an idea ๐