Skip to main content

Stripe gems: Koudoku or Payola

Rails • Asked by Mark Radford

Has anyone used either https://github.com/andrewculver/koudoku or https://github.com/payolapayments/payola ? If yes, are you able to give any feedback regarding ease of use, ability to customise, etc? Did you stick with the gem or did you end up implementing the Stripe code yourself?

Thanks.


Hey Mark,

I've personally always found it easiest to just build the Stripe integration myself. I've tried a couple of these gems and often found I was boxed into the way they do things which I could break out of, but at that point I'd basically not be using their gem that much.

You can always try the gems in a sample app and see how the integration goes before you put it in your real project.


Tried Payola over a year ago. But looking into how they want me to add thing's, I've found it's faster to use the API. I also think it adds even more to the "magic" (so you do not 100% know how things work).


I agree with Chris and Jack. I've found that integrating Stripe directly with the api is best. One less dependency for your app to rely on.


Thanks all for taking the time to give feedback. Looks like vanilla Stripe API is the way to go.

Off topic:

I've tried a couple of these gems and often found I was boxed into the way they do things which I could break out of, but at that point I'd basically not be using their gem that much.

I applied similar logic to avoiding Devise. In hindsight this may have been a mistake as Devise seems extemely poplular.


Yeah I think a lot of people do the same thing with Devise, however, it's got a great design so you can dive into the guts of it and make changes really easily. It also doesn't enforce much of anything upon your application, but it's easy to misunderstand that when you're new to the gem.


Login or Create An Account to join the conversation.

Subscribe to the newsletter

Join 27,623+ developers who get early access to new screencasts, articles, guides, updates, and more.

    By clicking this button, you agree to the GoRails Terms of Service and Privacy Policy.

    More of a social being? We're also on Twitter and YouTube.