#ParkerMurray
1 messages · Page 1 of 1 (latest)
How do you test authorisation in the dashboard?
in test mode Connect -> selecting a connected account -> viewing from their dashboard -> issued cards -> overview -> create test Authorization
Can you share the connected account ID (acct_xxx)?
acct_1MPI4SQ9Ow3CBOAj
Which issuing card did your dashboard test run on in this connected account? I couldn't find the test authorisations in your screenshot
If I trigger an event I do see this webhook and am able to handle it.
Could you also share the event ID where you seeissuing_authorization.requestin this flow, so that I can have a comparison between these two?
thats the issue, I can trigger the issuing_authorization.request through my local terminal and handle it, but when I create the authorizations on the dashboard the only webhook that is triggered is the issuing_authorization.created.
oh sorry I didn't realize you were replying to my earlier message. one moment.
Event Id: iauth_1McJn9LTMGrur7WEw3hwrw1h
Thanks for sharing! In iauth_1McJn9LTMGrur7WEw3hwrw1h, the issuing request was processed on the platform acct_1M2KKALTMGrur7WE (not connected account): https://dashboard.stripe.com/test/issuing/authorizations/iauth_1McJn9LTMGrur7WEw3hwrw1h
In the authorisation iauth_1McIvTQ9Ow3CBOAjTWmjA3aK on connected account acct_1MPI4SQ9Ow3CBOAj as an example, there's no webhook setup for listening to connect webhook events
is there a way to set up a webhook for local testing for that connected account?
If you wish to listen to connect webhook event locally, I'd recommend setting up stripe listen with --forward-connect-to: https://stripe.com/docs/cli/listen#listen-forward-connect-to
oh wow okay let me see if that works.
I still only got the issuing_authorization.created webhook
Could you share the authorisation request ID (iauth_xxx)?
iauth_1McK9NQ9Ow3CBOAjGBRY5voc
In evt_1McK9OQ9Ow3CBOAjN6QeDPNP (issuing_authorization.created event) of iauth_1McK9NQ9Ow3CBOAjGBRY5voc, I can see that the authorisation was approved, so issuing_authorization.request wasn't sent for authorisation approval
Checking why the authorisation was approved upon creation in iauth_1McK9NQ9Ow3CBOAjGBRY5voc
awesome thankyou
any updates?
I'm still checking with the team. From the behaviour, it looks like AutoPilot (https://stripe.com/docs/issuing/controls/real-time-authorizations#autopilot) might be in place, but still confirming whether this is the case
Could you share how you listen to test mode event connected event currently? Did you receive evt_1McK9OQ9Ow3CBOAjN6QeDPNP in your webhook server, or simply check the dashboard?
From our records, you only listen to connect webhook events in live mode, but not in test mode
So when I create a authorization on the dashboard I receive the Issuing_authorization.created on my local server
is there a way to change that setting and see if it makes a difference?
issuing_authorisation.request is a blocking event and will only be generated if your webhook endpoint subscribes listening to it. From what we see here is that there is no connect webhook endpoint listening to issuing_authorisation.request, so it was not created
how do I go about creating an webhook listening for that?
Are you listening to Webhook locally or setting up in the Dashboard?
i am forwarding all webhooks to my local server
I get webhooks for things done in the dashboard and handle them locally
Do you use Stripe CLI or setting up an endpoint in Dashboard for forwarding the events to local server?
--forward-to only listens to platform event
For connected account event, it should include --forward-connect-to flag: https://stripe.com/docs/cli/listen#listen-forward-connect-to
I also tried that, but let me try that again.
if that was the case how would I be getting the issuing_authorization.created event for a connected account card holder?
the result is the same, my server only received the issuing_authorixation.created webhook
Let me check your webhook setup now
issuing_authorization.created is not a blocking event that requires actions from you, so it will be created
okay, thank you
any word