Family Sharing - Auto Renewing Subscription

At the moment we have an auto renewing subscription and we use the original_transaction_id as a marker in our database.

If we turn on Family Sharing it was mentioned that each family member gets a transaction in the queue on their device.

Will the original_transaction_id be the same for each user or will each user/Apple ID get their own unique receipt and set of transactions? Or is it simply a copy of the primary user?
Each customer will have a unique receipt, and you should treat it as any normal receipt, making no assumptions about the original transaction id.
To clarify,

Ideally we would like each user linked to a Family Sharing transaction to have their own original_transaction_id and susbsequent renewal transactions of their own.

The original Apple recommendations said to rely on this field and so a lot of code hinges around this being unique to a subscription (and with relevant usage limits applied in our code too).

If these get treated as “new” users essentially we are happy for that but ideally some sort of flag saying they are linked to an original in case people run local billing metrics!
Sorry, my reply was being written as you sent that.

Will each Apple ID have a unique original_transaction_id or will it be the same as the primary user?
Since original_transaction_id is used as a primary key for Apple subscriptions, knowing if it is the same for all family member or not has major architectural consequences. For now, our implementation ensure only 1 user can use a given subscription. If original_transaction_id is different for all family members it'll still work fine. If not we have to re-architecture our solution.

However, we also use the transactions to estimate revenues (MRR, ARPU, etc.) If transactions id are different but are not linked together in some way we will count revenues twice, which will mess up our stats.

Thanks for your clarification.
Now that the Family Sharing is up and running for renewable subscriptions, can someone confirm here what are the values received for the original_transaction_id field in receipt.

Our assumption from the doc is that all customers should get the same original_transaction_id value as the original purchaser, while each transaction_id is unique.
Others here are expecting different original_transaction_id for each customers.

And the accepted answer is ?
Now this is live is there any tech guides on how this is implemented?

Specifically around the identifications, is there any links back to the original purchase ID at all?


Family Sharing - Auto Renewing Subscription
 
 
Q