Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> supporting a unified API that can work with redirect-based payment methods

Does this mean that it will be possible to implement Stripe payments that work without JavaScript?



Not yet, but the amount of JavaScript necessary is really small. Essentially:

Essentially:

  window.Stripe('<your key>').redirectToCheckout({sessionId});


Plus 33KB of Stripe's own JS (123KB after ungzipping).

When using server integration, shouldn't the server be able to compute the link itself? Why does the server integration require Stripe JS at all?


I'm gonna go out on a limb here and guess there's some Panopticlick/Recaptcha style human detection / fraud prevention going on in the JS.


Why tho?

It seems odd to require client side code (probably rendered by the server anyway) just to do a redirect, servers are perfectly capable of that. Doesn't the server have the sessionId and public key anyway? Why do you do it this way?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: