Connect receipt validation user with server notifications

[Iamscaredofcode]

Hello @imdhemy! I am experimenting with this package and i like the way it is build - very professional!

I am wondering why not more people are using it because this seems to be the best on the market.

Altough I have one question:

Which property on the receipt should I associate with the user, so that I can fetch the user again in the server notification listeners.

In the readme i see the use of getUniqueIdentifier(), but how to I first store this value when validating the receipt?

$notification = $event->getServerNotification();
$subscription = $notification->getSubscription();
$uniqueIdentifier = $subscription->getUniqueIdentifier();
$user = $this->findUserBySubscriptionId($uniqueIdentifier);

I hope I could describe it clearly.

Thank you

[imdhemy]

Hello, @Iamscaredofcode
I'm really happy to read your nice words. Thank you! ❤

I faced the same problem during the development of one of our apps. Google Play allows the developer to attach a developer payload, but the App Store does not.

As a workaround, I implemented an endpoint that allows the mobile application to inform the backend about the purchased subscriptions.

1. Once the subscription is purchased on the mobile application, it receives receipt data from the provider.
2. The mobile application sends the data to your backend through the previously mentioned endpoint.
3. You can find the user through your authentication process, and connect the receipt data with the authenticated user.

It's something like, hey backend, I just purchased this subscription from the IAP! 😅

[michavie]

@imdhemy this seems to be the problem - the token is probably not invalidated correctly.

Subscription upgrades, downgrades, and other subscription purchase flows generate purchase tokens that must replace a previous purchase token. You must invalidate the purchase tokens that appear in the linkedPurchaseToken field of the Google Play Developer API.

Still trying to figure out the best way to invalidate old tokens. do you maybe have an example for this that we can document?

[imdhemy]

@michavie, check this topic #38

[michavie]

@imdhemy is it generally recommended to use the purchaseToken for purchase attribution, correct? (developer payload seems to become deprecated soon)

[imdhemy]

@michavie I think so!

[Iamscaredofcode]

@michavie No I didn't release my app until this day