Subscription model not properly linking foreign key to account model

[DeeeeLAN]

I don't know exactly why it doesn't work, but subscriptions are created with the account field set to null. I would guess it has something to do with using a function to retrieve the model, although I don't know why that would cause it to fail. However, since you already have the string, maybe it would be easier to just lazy load the model by passing the string in directly to the foreign key field.

I can successfully access the subscription by going user.customers.first().subscriptions.all().

[bgervan]

Can you give example what doesn't work that should?

[DeeeeLAN]

I think I misunderstood the account model idea. Are we supposed to create a custom account model separate from any other models? What role is this model expected to play in a typical use-case? For some reason I was thinking that the account model could be set to my user model, but reviewing the code I now see that was incorrect.

[bgervan]

In the Subscription model

account = models.ForeignKey(
        to=get_account_model(),
        null=True,
        on_delete=models.SET_NULL,
        related_name="subscriptions",
    )
customer = models.ForeignKey(Customer, on_delete=models.CASCADE, related_name="subscriptions")

What is your account model? It can be the user or it can be anything else, but after the migration done, cannot be changed.
The idea behind it, is to give option to create custom account model, for example if your create a SAAS, you would have multiple workspace for a user, each workspace has a separate subscription, so you need to attach the subscription to the owner Member model in order to check subscription. Or you can attach to the Workspace model. Depends on the business logic you need.

If you set the User model as Account model, the user.subscriptions.all() should work

[DeeeeLAN]

I have it set to my user model, however every subscription just shows null for the field. I saw something about checking the primary key when syncing the subscriptions and I assumed the primary keys of my user model wouldn't match the account ID fetched from Paddle, like I would need to create my user based on the paddle account for it to connect.

Edit:
I see in the model that subscriptions look in the custom data for an account id:

django-paddle-billing/src/django_paddle_billing/models.py

Lines 543 to 552 in 9206154

	account_id = None
	try:
	account_id = data.custom_data["account_id"]
	except (KeyError, TypeError):
	pass
	if account_id is not None:
	if not get_account_model().objects.filter(pk=account_id).exists():
	error = f"Subscription: Account with id: {account_id} does not exist"
	return None, False, error

[bgervan]

Yes, the account_id connection for the subscription comes from the custom data

function openCheckout() {
  const items = [
    { priceId: 'pri_01j71q71396s7pfbxasdfzpnrz', quantity: 1 },
  ]
  const checkoutData: CheckoutOpenOptions = {
    customer: {
      email: 'admin@admin.com',
    },
    customData: {
      account_id: '93e9dc69-e6c4-4709-a0ad-107ac92c2e56',
    },
    settings: {
      displayMode: 'inline',
      theme: 'light',
      locale: 'en',
      frameTarget: 'paddleContainer',
      frameStyle: 'width: 100%; min-width: 312px; background-color: transparent; border: none;',
      allowLogout: false,
    },
  }

  if (paddleStore.checkoutEventData?.transaction_id)
    checkoutData.transactionId = paddleStore.checkoutEventData?.transaction_id

  else
    checkoutData.items = items

  paddle.value?.Checkout.open(checkoutData)
}

In vue for example, you can do this like that. The account_id in my case is a uuid, but you can just add your user id.

I thought this information is in the readme, I will create some documentation in the upcoming weeks.