Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stripe CLI

stripe.com

Post reply on HN
Print view View original

41–50 of 149 posts

Re: Stripe CLI

#41

Post by jchw »

pc wrote: post #25
knubie wrote: post #15

Stripe is by far the best developer experience I’ve had in my career working with third party APIs/services. The attention to detail is just second to none, and documentation is a big part of this.

Thanks! We still have a lot of work to do. (Making our integration experience simpler -- now that Stripe's functionality has grown so much -- is an area of current focus. If any HN readers happen to have specific suggestions on this front, feel free to email sebas@stripe.com.)

Honestly, the only problem I ran into with Stripe ever was administrating subscriptions. IIRC even via the API there were a lot of limitations with what state you could put a subscription in, limiting our ability to seamlessly transition from Recurly to Stripe; we ended up duplicating a lot of the subscription logic in the end.

I know subscriptions have been significantly rehauled since then, but this was my only gripe. Stripe was absolutely excellent back when I used it.

Re: Stripe CLI

#42

Post by nickjj »

sumukh1 wrote: post #33
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.

I still prefer to setup ngrok because it allows me to view and replay requests. If the stripe cli supported that, then I'd move to use the cli entirely

Yeah that's true, another upside to ngrok is it works for not just Stripe. Sometimes you need to link up with multiple payment gateways and listen for webhooks from 1 of them at a time.

Re: Stripe CLI

#43

Post by zehtomer »

sumukh1 wrote: post #33
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.

I still prefer to setup ngrok because it allows me to view and replay requests. If the stripe cli supported that, then I'd move to use the cli entirely

On the listen side, you can run `stripe listen --print-json` which will output the entire object.

You can also resend events by doing `stripe events resend `.

We'll see about documenting both better!

Re: Stripe CLI

#45

Post by Reedx »

knubie wrote: post #15

Stripe is by far the best developer experience I’ve had in my career working with third party APIs/services. The attention to detail is just second to none, and documentation is a big part of this.

100%. They're an excellent example of how impactful attention to detail and simplicity can be.

Thinking back to implementing Stripe for the first time, I remember being surprised by how painless it was. Prior to that integrating payments was something that filled me with the same kind of dread I get from dealing with legal paperwork.

I love that they've been so successful.

Re: Stripe CLI

#47

Post by twunde »

ceejayoz wrote: post #21
MuffinFlavored wrote: post #12

Earlier quoted context omitted.

Really? It's like... 3 API calls. Create a customer, store a card, create a charge.

There's quite a bit more complexity in some use cases. Some payments are now asynchronous due to https://en.wikipedia.org/wiki/Strong_customer_authentication ; handling failed payments for things like subscriptions takes some effort (and managing webhooks). My experience with Stripe has been great, but payments can still get into the weeds through no fault of Stripe's.

Some other examples of complex use cases: connected accounts, reconciliation reports, dunning reports, non-traditional ecommerce workflows. From a security perspective, I'd love the ability to enforce 2FA instead of having to audit the users table every month. To be fair I think the number of clients with 50+ connected accounts is fairly low

Re: Stripe CLI

#48

Post by sealthedeal »

Love this! We Strive everyday at Routefusion.co to model our developer experience and attention to detail off of what Stripe has done. They turned credit card payments sexy, not an easy thing to do, but when you have great experiences like this and focus on a the builders of tomorrow I guess it works!

Re: Stripe CLI

#49

Post by rsync »

In the Twilio world, I can do something like this, via the command line and their API:

- activate new phone number

- send SMS from that number

- deactivate number

I have not ever done that particular workflow, but I could.

Who is the Twilio of payments/fintech wherein I could perform a workflow like this:

- generate new CC number in my name

- set transaction limit(s) and expiry 10 days from now

- (go use that CC in real life)

- deactivate the CC

or maybe:

- disable existing card

- reenable existing card

I know I could do this if I wrote the API myself and had a big, complicated, sticky relationship with a bank ... but does someone let me do things like this if I am just an end-user (like Twilio does) ?

Re: Stripe CLI

#50

Post by mLuby »

rsync wrote: post #49

In the Twilio world, I can do something like this, via the command line and their API: - activate new phone number - send SMS from that number - deactivate number I have not ever done that particular workflow , but I could. Who is the Twilio of payments/fintech wherein I could perform a workflow like this: - generate new CC number in my name - set transaction limit(s) and expiry 10 days from now - (go use that CC in…

Sounds like something Privacy.com could do without much trouble, though I don't think they actually have a CLI (yet).
Post reply on HN