#nanorepublica_webhooks
1 messages · Page 1 of 1 (latest)
👋 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/1395345916977741986
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
What does creating a test purchase in the Dashboard look like? Specifically which event types are you expecting?
If you have the CLI configured and running correctly then it should also forward events fired from Dashboard activity
This is the test authorization in the dashboard. I'm expecting the "issuing_authorization.created" to be triggered from creating a test purchase.
Please just paste IDs, it's easier for us to debug than screenshots
Paste that iauth_xxx please
Apologies!
The id is iauth_1RloQUC5gkDKgkZhsY2A5Ozq
OK, so I see the .created event: https://dashboard.stripe.com/test/events/evt_1RloQVC5gkDKgkZh0QS4Pxmp
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Is it not being forwarded by the CLI? What command(s) are you running with the CLI?
Should have stripe listen --forward-to=xxx at the least
Strange so that URL gives me "No event deliveries found" and I am getting nothing in the CLI which is setup as you describe
I would guess that you're authenticated in the CLI on a different account
acct_1RLkyKC5gkDKgkZh is the account that event fired on
Run stripe login again
I am running it via the environment variables inside docker so I will check my keys
It has to be related to that I would suspect. If you can share the evt_xx ID of an event you triggered via the CLI I can confirm
It's a different key... 🤦 thanks for the help I will double check which key I currently have configured etc