Stripe CLI

#1

Post by askytb » Tue, Nov 05, 2019, 4:55 PM UTC

Re: Stripe CLI

#2

Post by nickjj » Tue, Nov 05, 2019, 5:43 PM UTC

This looks really good.

It sounds like you won't have to configure tools like ngrok anymore to accept webhooks on a local connection. That's a huge win because with the free version of ngrok your subdomain would change a lot which means having to goto the Stripe dashboard to update it there. It was pretty tedious.

Re: Stripe CLI

#3

Post by kauegimenes » Tue, Nov 05, 2019, 5:48 PM UTC

nickjj wrote: post #2

This looks really good. It sounds like you won't have to configure tools like ngrok anymore to accept webhooks on a local connection. That's a huge win because with the free version of ngrok your subdomain would change a lot which means having to goto the Stripe dashboard to update it there. It was pretty tedious.

That's why i switched from ngrok to localtunnel (global npm package) https://www.npmjs.com/package/localtunnel

You can just run lt -p 8080 --subdomain whateveryouwant ;)

Re: Stripe CLI

#4

Post by deforciant » Tue, Nov 05, 2019, 5:48 PM UTC

that's nice! :) I have found that quite often Stripe's UI would just through errors when trying to open some customers, failed payments or subscriptions. Couldn't really pinpoint why it happens, tried different browsers, disabling extensions and so on.

Hopefully CLI wil work :)

Re: Stripe CLI

#5

Post by benologist » Tue, Nov 05, 2019, 5:49 PM UTC

nickjj wrote: post #2

This looks really good. It sounds like you won't have to configure tools like ngrok anymore to accept webhooks on a local connection. That's a huge win because with the free version of ngrok your subdomain would change a lot which means having to goto the Stripe dashboard to update it there. It was pretty tedious.

This is a free equivalent to ngrok and it only uses SSH - https://serveo.net/ - and it accepts custom subdomains. I spin it up for each project like this with $DOMAIN and $PORT being defined/fixed for each project and the connection kept open permanently using autossh:

     ssh -R $DOMAIN:80:localhost:$PORT serveo.net

There are API endpoints for creating, listing and deleting webhooks in Stripe now too - my test suites and dev instances purge any existing webhooks and create a new one each run.

https://stripe.com/docs/api/webhook_endpoints/create

Re: Stripe CLI

#6

Post by zip1234 » Tue, Nov 05, 2019, 5:50 PM UTC

nickjj wrote: post #2

This looks really good. It sounds like you won't have to configure tools like ngrok anymore to accept webhooks on a local connection. That's a huge win because with the free version of ngrok your subdomain would change a lot which means having to goto the Stripe dashboard to update it there. It was pretty tedious.

Yes setting up all that stuff was one of the most painful things about local development working with Stripe webhooks. This is a good solution.

Re: Stripe CLI

#7

Post by TechTeam12 » Tue, Nov 05, 2019, 5:54 PM UTC

I filled a bug task on your github page, but you've got a deadlink for the linux install in your readme.

Really excited to get to use these tools. Already integrated with stripe for my projects, but this will allow for more cool testing. Thank you stripe team!

Re: Stripe CLI

#8

Post by 18nleung » Tue, Nov 05, 2019, 5:55 PM UTC

How can I get the multiple terminals view in the blog header image?

Re: Stripe CLI

#9

Post by daliusd » Tue, Nov 05, 2019, 6:01 PM UTC

Wow, so I have implemented Stripe integration in my project recently and I was using at least one feature mentioned in this blog. It was breeze to add payments to my project (and I have experience with some other systems that requires days to implement and test properly).

Re: Stripe CLI

#10

Post by chadlavi » Tue, Nov 05, 2019, 6:02 PM UTC

This is a great improvement! Last time I did a stripe integration it was definitely kind of a painful, disjointed experience.