Question about team subscriptions

[strzibny]

Hi,

I am trying to play with Pay and decided to make teams (Team model) the owner of a subscription. This works only if the emails are different, but one person (with same email) could create two team subscriptions. When a webhook comes in, the subscription is created with the team that already exists (as an existing owner).

How do you design this with Pay? Do you just leave it with a User and then simply work around it when comes to teams?

Thanks a lot for anybody's insight.

[excid3]

If you want to create two subscriptions for the same customer, you just call subscribe twice on the same Pay::Customer.

[strzibny]

Yes, I understood that much. The problem in the Team setup was that Paddle will return the same user_id for the same email. So on Pay end, the subscription ended up with a different team in the end (the one that created the Pay::Customer first).

So now I think I have to model it to be a User model, right? I would have to name the different subscriptions, which means I have to pass some identifier to Paddle.

Originally I went with Team because I though it would be nice that more users could manage the subscription under one company email.

[strzibny]

Yes, but it will be the same ID. Even if it's a new request to subscribe, the webhook will return the same user_id because the email was same.

Basically if Paddle just created a new customer with a new ID (but same email), everything would work.

[excid3]

If Paddle is mapping it to the same User in their system, we want it to match in Pay.

[excid3]

Feel free to fork and try setting it up in a different way and report back. 👍

I'm pretty sure the passthrough is only available in webhooks (like the comment mentions) so you can't always rely on the passthrough to associate with the Customer.

[strzibny]

Yes, so basically I was thinking what could I do, but wanted to make sure I am not missing something obvious. Thanks for the quick replies.

[excid3]

Let me know how it goes. It's always trickier than it seems because these APIs are pretty poorly written (except Stripe's). 😅