#ParkerMurray

1 messages · Page 1 of 1 (latest)

jagged prismBOT
quartz summit
#

How do you test authorisation in the dashboard?

viral sorrel
#

in test mode Connect -> selecting a connected account -> viewing from their dashboard -> issued cards -> overview -> create test Authorization

quartz summit
#

Can you share the connected account ID (acct_xxx)?

viral sorrel
#

acct_1MPI4SQ9Ow3CBOAj

quartz summit
#

Which issuing card did your dashboard test run on in this connected account? I couldn't find the test authorisations in your screenshot

viral sorrel
#

cardholder name is parker murray under PB

#

acct_1MPI4SQ9Ow3CBOAj

quartz summit
#

Got you! Seeing the transactions now

#

Working on it

viral sorrel
#

👍

#

Let me know what you find

quartz summit
#

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 see issuing_authorization.request in this flow, so that I can have a comparison between these two?

viral sorrel
#

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

quartz summit
viral sorrel
#

is there a way to set up a webhook for local testing for that connected account?

quartz summit
viral sorrel
#

oh wow okay let me see if that works.

#

I still only got the issuing_authorization.created webhook

quartz summit
#

Could you share the authorisation request ID (iauth_xxx)?

viral sorrel
#

iauth_1McK9NQ9Ow3CBOAjGBRY5voc

quartz summit
#

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

viral sorrel
#

awesome thankyou

viral sorrel
#

any updates?

quartz summit
#

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

viral sorrel
#

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?

quartz summit
#

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

viral sorrel
#

how do I go about creating an webhook listening for that?

quartz summit
#

Are you listening to Webhook locally or setting up in the Dashboard?

viral sorrel
#

i am forwarding all webhooks to my local server

#

I get webhooks for things done in the dashboard and handle them locally

quartz summit
#

Do you use Stripe CLI or setting up an endpoint in Dashboard for forwarding the events to local server?

viral sorrel
#

yes

#

stripe listen --forward-to localhost:3000/webhooks/stripe

quartz summit
viral sorrel
#

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

quartz summit
#

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

viral sorrel
#

okay, thank you

viral sorrel
#

any word