Lemon Squeezy support

[deanpcmad]

This PR adds support for Lemon Squeezy, a Merchant of Record payment provider. Their site is here > https://www.lemonsqueezy.com/

It uses a Ruby library I built, lemonsqueezy.

This is a rewrite of #898 from what I've learnt with integrating Paddle Billing. The Lemon Squeezy API is quite similar to Paddle's Billing API. I have noticed a few things though:

• Trial Subscriptions have the status of on_trial. Not sure if you want to set it as that or replace the status with trialing when saving?
• They don't support cancelling subscriptions immediately.
• Card expiry dates aren't listed in the API, just the brand and last 4
• Charges cannot be created from the API

This is a WIP.

[harrison-broadbent]

Keen!

[excid3]

trialing would be nice to make it consistent everywhere which is helpful for querying. Although I don't like modifying data from the API if we can help it. I would say we should map it.

We can raise an error for cancel_now if they don't support immediate cancellations.

What else do we need to implement?

[deanpcmad]

Another oddity I've found, is that they don't list card expiry dates in the API, just the brand and last 4 🤔

[excid3]

Another oddity I've found, is that they don't list card expiry dates in the API, just the brand and last 4 🤔

That is very odd.

[deanpcmad]

trialing would be nice to make it consistent everywhere which is helpful for querying. Although I don't like modifying data from the API if we can help it. I would say we should map it.

So when a subscription is a trial, set the status as trialing or keep it as is?

[deanpcmad]

Have just pushed a couple more commits, including initial work on docs. Feel free to give it a go.

I've noticed they don't have an API for creating charges, so I've sent them an email requesting this plus a few other minor details such as card expiry dates.

[deanpcmad]

As for linking a subscription to a LS Customer, it appears that setting the email address in the URL links it, but I've added support for passthroughs just like Paddle Classic. This is another thing I've asked about, seeing if we can just pass the Customer ID to link it.

An example payment link I've been using has been in this format:

https://voupedev.lemonsqueezy.com/checkout/buy/xxx?embed=1&checkout[email]=yyy&checkout[custom][passthrough]=zzz

You should replace xxx with the UUID of the product, which can be viewed when clicking the Share button.

[deanpcmad]

Have just heard back from Lemon Squeezy.

• They don't support charging through the API as all orders/subscriptions must be created through their checkout.
• Passing the email address of a customer links it to a customer created in Lemon Squeezy

This means a passthrough isn't required, but it may be best to keep it for if a customer doesn't exist?
Thoughts @excid3?

[excid3]

1. That's fine, just have the charge method raise an error?
2. I don't think we need the passthrough

[excid3]

LemonSqueezy.js 2.0 is out now. https://github.com/lmsqueezy/lemonsqueezy.js/releases/tag/v2.0.0

[deanpcmad]

Ha, I just received an email from them saying that 😅 I believe that's their official API library, not Lemon.js which is used for checkout overlays.

[deanpcmad]

Yeah 😆 - Lemon.js is the client-slide library - https://docs.lemonsqueezy.com/help/lemonjs/what-is-lemonjs

[excid3]

And to think they could have called the Node SDK "lemonode.js". Such a shame.

Edit: Hah, someone beat me to it: https://www.npmjs.com/package/lemonode

[deanpcmad]

Wow published 11 years ago 😅

[nduplessis]

I would love to help get this over the line, is there anything still outstanding that's required for a merge?

[joshfester]

Does this mean lemon squeezy support will be coming to Jumpstart? 👀

[deanpcmad]

There are still a few tweaks that need to make such as removing the passthrough code, but I'd say it's ready for you to check over @excid3?

[Gary-H9]

👋 Similar to @nduplessis, I'd like to help here if possible/necessary.

[5andu]

Any updates or help needed for this? :)

[deanpcmad]

I believe it's ready for people to test, so feel free to give it a go

[5andu]

Thanks!

[k0va1]

Hi @deanpcmad! Thanks for a great job! I've tested this branch and bumped into one error:

• looks like passthrough related code https://github.com/pay-rails/pay/pull/947/files#diff-b6c834b65694d506d791c25065febbc6b1b2e6cd4e606df61f411ae30278a4e5R41 is broken because Pay::LemonSqueezy.owner_from_passthrough method doesn't exist anymore. Hence it's not possible to create new customer & link a subscription to it.

Could you take a look at it? Ping me if you need help with this PR, I really want to merge it 😀

[deanpcmad]

Ah good spot, will change that

[k0va1]

This means a passthrough isn't required, but it may be best to keep it for if a customer doesn't exist?

@deanpcmad I'm not quite sure if it's a valid approach but I'm looking for a customer like this k0va1@4cae510

Passthrough might be not a bad option tho

[deanpcmad]

Yeah, maybe it would be best to keep the passthrough there

[deanpcmad]

@k0va1 feel free to test it now. I've reverted the commit that removes the passthrough code & docs

[deanpcmad]

@excid3 have you had chance to take a look at this yet? 😄

[excid3]

A little, but need to build an end-to-end implementation to test it.

[k0va1]

what if we don't find any invoice and got 404 error? i suppose this case should be handled

I bumped into an Error 404: No results were found for your request. '[{"status"=>"404", "title"=>"Not Found"}]' (LemonSqueezy::Error) while accidentally sending test webhook to production server

[deanpcmad]

Well, Stripe just acquired Lemon Squeezy - https://www.lemonsqueezy.com/blog/stripe-acquires-lemon-squeezy

[excid3]

Saw that, super exciting!

[nflorentin]

I was wondering why the addition of lemon_squeezy is commenting this line of code which seems to impact all processors.