Custom payment provider? #192
-
How difficult would it be to implement a different provider manually in my repo? From digging around the source a bit, it looks to me like the payments focus is on using pre-made subscription billing solutions, hence the use of Stripe Checkout in particular. So, I just wanted to open the discussion in case there's any tips, pitfalls, limitations, etc. Would be interesting to give it a go for implementing LemonSqueezy (who have their own Cashier-like package too) or Creem. If it can be done successfully, would also be worth PRing to the main repo or making a plugin I think. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey! There was a similar question a couple of days ago here. As of the time being we are not actively working on adding support for LemonSqueezy officially. However, if this is a must for you, you should be able to get that working with some customizations and possibly using the official Laravel package that they now offer: https://www.lemonsqueezy.com/blog/laravel-lemon-squeezy Let me know if you hit any issues while integrating it! Would be great and really appreciated to see a PR for this if you decide to go that route! |
Beta Was this translation helpful? Give feedback.
Hey!
There was a similar question a couple of days ago here.
As of the time being we are not actively working on adding support for LemonSqueezy officially. However, if this is a must for you, you should be able to get that working with some customizations and possibly using the official Laravel package that they now offer:
https://www.lemonsqueezy.com/blog/laravel-lemon-squeezy
Let me know if you hit any issues while integrating it! Would be great and really appreciated to see a PR for this if you decide to go that route!