4 ms·
I created a similar project about a year ago that never got much traction: https://paysly.io/ https://paysly.io/ Its similar in principal, but it also creates
by si1entstill 6y ago
I created a similar project about a year ago that never got much traction: https://paysly.io/ https://paysly.io/
Its similar in principal, but it also creates a signed version of the stripe response [1], so you can hand it off to a backend and validate it without an additional stripe call.
Instead of requiring users to input auth keys, it uses stripe connect [2] to securely authenticate and act on behalf of users.
[1] https://docs.paysly.io/guides/verifying-a-payment.html https://docs.paysly.io/guides/verifying-a-payment.html
[2] https://stripe.com/connect https://stripe.com/connect
- yashmaistry 6y agoYour product looks good! Using Stripe Connect is something we are going to add.
- justsomeuser 6y agoBut if I already have a backend, why would I use Paysly (instead of the default for a Stripe integration)?
- si1entstill 6y agoIf you have an app with a traditional backend, you likely wouldn't. I saw the need when I had a couple of simple apps where I didn't really have a web server where I could create payments/subscriptions via stripe's server-side libraries. I also didn't want to use stripe's Checkout. I had to spin up a simple service just to confirm the payments and I figured I could abstract it. The signed jwt response can be helpful because now you just need paysly on the frontend and your backend can be dependency free - all it needs to do is parse the token.