#hiroshi nishio

1 messages · Page 1 of 1 (latest)

wet grailBOT
fleet horizon
#

Hi 👋 Payment Links are a good option, as long as you don't need to customize the Subscription that you're selling or your checkout experience on a per-customer basis.

This is our guide for building a Payment Link:
https://stripe.com/docs/payments/payment-links

Share payment links

Accept payments without building a digital storefront.

near robin
#

Thanks. While I understand that it depends on business requirements, if you were me, which one would you use to create a paid Slack bot? I'm just curious about some sort of best practices.

fleet horizon
#

I'm not sure off-hand. That's not a use-case I've worked with before so I'm not familiar with what limitations exist in that tech stack, or what inherit advantages it can offer.

#

If you don't have a dedicated site, then I would be looking into approaches that allow you to provide your customers with a URL to a hosted page (as you suggested). So I'd look to Payment Links for a more low-code, one-size-fits-all approach, but if I wanted something where I had more granular control then Checkout Sessions are what I'd be looking into:
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout

Accept a payment

Securely accept payments online.

near robin
#

I see! So, I guess I'll start by understanding the difference between Payment Links and Checkout and knowing what I can do with specific customizations.... Or maybe I should try using Payment Links once and hit what I can't do, and then see if Checkout can solve it.