Free and open-source payments orchestrator/system, Hyperswitch #11091
-
Weblate uses a proprietary bi-language website: https://www.thepay.eu/, found in https://weblate.org/donate/ Hyperswitch is built with Rust and is now fully free and open source (app server, card vault, web client SDK & dashboard). It is optimized for sub 30ms overhead with 50+ processor integrations. There's also multiple self-hosting options Reddit Questions and Answers with one of the devs
Source Code: 9.2k stars, 730 forks, 158 contributors |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
AFAIK, any credit card processing will be done by a proprietary website. Having an open-source middleman doesn't really change much. Furthermore, having a middleman without an official Python bindings is not really helpful for us. Any abstraction layer for payments I've seen so far sucks in recurring payments. The reason is simple - each processor handles this very differently, and building abstraction here is tricky. https://docs.hyperswitch.io/features/payment-flows-and-management/mandates-and-recurring-payments really doesn't explain this much into detail. PS: We will most likely switch to some other processor this year for various reasons. |
Beta Was this translation helpful? Give feedback.
AFAIK, any credit card processing will be done by a proprietary website. Having an open-source middleman doesn't really change much. Furthermore, having a middleman without an official Python bindings is not really helpful for us.
Any abstraction layer for payments I've seen so far sucks in recurring payments. The reason is simple - each processor handles this very differently, and building abstraction here is tricky. https://docs.hyperswitch.io/features/payment-flows-and-management/mandates-and-recurring-payments really doesn't explain this much into detail.
PS: We will most likely switch to some other processor this year for various reasons.