Live data from Hacker News

Stripe Payment Links

stripe.com

181–190 of 328 posts

Re: Stripe Payment Links

#181
post #79
post #66

Earlier quoted context omitted.

Gumroad deposits to Paypal, Stripe deposits to bank account. Seems like a big difference, no?

Gumroad deposits to bank accounts, but it might be regional. I have a section for ACH in my setup page. You can optionally also add a PayPal account to accept PayPal.

According to https://help.gumroad.com/article/260-your-payout-settings-pa..., it depends on Stripe's availability for ACH payouts.

Re: Stripe Payment Links

#182
post #41

Earlier quoted context omitted.

Super sleek! A minor feedback for the marketing page. I’m an English speaker currently in Mexico City. The webpage first opened in Spanish based on my location. It only took a few seconds to figure that I could change the language just above the footer, but my UI recommendation would be to put the location/language switcher next to the upper right sandwich (I’m on mobile) in a circle with the flag of my default count…

Good feedback -- thanks. We've long struggled to find the right balance between "convenient/automatically correct" and "non-confusing" in site localization.

Why not just use the Accept-Language header? stripe.com already does this – At least I get redirected to "https://stripe.com/en-de", seemingly based on the combination of header and geolocation

Re: Stripe Payment Links

#183
post #77
post #23

(Stripe cofounder.) While there are lots of antecedents (this is, after all, just a checkout page with a URL), and even though this was substantially inspired by the growth of the no-code ecosystem[0], the thing that's interesting to me about the payment link "space" is that it's a use case that really took off in other markets first -- Nigeria, India, Philippines, etc. I suspect that staying abreast of important new…

Not related to payment links... but I would love to see Stripe take on handling in app purchases. (basically a webhook and management layer over the terrible native APIs) Companies like RevenueCat are halfway there but have nowhere as nice of an API or dashboard as Stripe. I run a cross platform (web/ios/android) app and would love to do payments all under one platform (Stripe, that is). Apple and Google subscription…

[deleted]

Re: Stripe Payment Links

#185
post #23

(Stripe cofounder.) While there are lots of antecedents (this is, after all, just a checkout page with a URL), and even though this was substantially inspired by the growth of the no-code ecosystem[0], the thing that's interesting to me about the payment link "space" is that it's a use case that really took off in other markets first -- Nigeria, India, Philippines, etc. I suspect that staying abreast of important new…

I'm reluctant to hijack this thread, but please support payments in Panama. These payment links would be a big deal there. Panama uses the USD and has the best developed banking and financial services in all Central America. I've been hoping stripe would get here ever since you launched as a company.

When you launched Atlas I've considered it, but the accounting and taxes are complicated and expensive. I believe one even needs to charge state sales taxes in some states.

Re: Stripe Payment Links

#189
post #179

Earlier quoted context omitted.

If it's IAP for digital items then you can't use Stripe for IAP on iOS/Android, it has to go through the respective store's IAP logic.

Yes, which is why I am asking for Stripe to do an IAP wrapper as other companies have tried. Apple and Android’s subscription APIs are terrible, essentially what is needed is an abstraction around them to keep user entitlements in sync without having to deal with the native APIs. The IAP is still handled natively, but the receipts and notifications are used to create a consistent experience.

Ahh, that’s an interesting proposition and the more I think about it, the more I like it. Just pass in some param to the “create payment intent” to indicate it’s a IAP-required purchase and they wrap the internal Apple/Google implementation. You’d still need to handle Apple/Google-specific errors but it’s be in one code-flow (the same way you have to handle secure-3D or whatever it’s called in the current Stripe payment flow).

Really they’d be smart to create an “External Payments” or “Off-platform payments” concept to support more than just Apple/Google. It could be a little odd to not get payouts on a portion of your invoices (like it could cause weird issues if you suck all the Stripe data into another tool/your platform, you’d have to take that into account) but it might be useful to enough people. It sets Stripe up to step in, with small code changes for the developer, if the walls weaken/come down around current IAP policies. Also, it provides only 1 API for a dev who wants to offer CC as well Apple Pay (not IAP) instead of 2 or just skipping CC (using only Apple Pay).

All that said, it will be a hard sell to Stripe execs who will probably see it as a large maintenance burden all to record stuff they don’t make money off of.

I do like the idea though!

Re: Stripe Payment Links

#190

I believe I patented this in 2016: https://patents.justia.com/patent/10664883

Not a lawyer but you didn't patent this. A patent only covers what's described in its claims, and looking at Claim 1 (the only independent claim) there are lots of very specific features that would have to be present for your patent to cover this.

Even if one of these stripe payment links is posted to a public social media channel, presumably neither the person doing the posting or stripe is going to do this because there's no association between the social media channel and the checkout page that stripe creates:

> conducting, by the processor, predictive modeling using the activity information, purchasing likelihood based on a number of visits by the user to the channel, past purchases by the user, and demographic information of the user;

Even if stripe was doing everything else in Claim 1 of your patent, just not doing this one thing means they aren't infringing your patent. (Again, not a lawyer, so don't listen to me).

Also, I may be wrong about this, but I suspect that the way you are using "processor" in your claims actually makes your patent 100% worthless, because it's describing both actions that would take place on the client side and on the server, so it will literally never be the case that the same processor is going to perform all of these steps even if they were all occuring in some implementation.

Post reply on HN