Download DEV/Misc/pshome_how_commerce_stores_work.txt from pebxcvi/PSHomeCacheDepot: direct link, hf CLI and curl.
- Browser
- Download file 4.93 kB
-
https://huggingface.co/datasets/pebxcvi/PSHomeCacheDepot/resolve/main/DEV/Misc/pshome_how_commerce_stores_work.txt
- Command line
-
hf download hf://datasets/pebxcvi/PSHomeCacheDepot/DEV/Misc/pshome_how_commerce_stores_work.txt
-
curl -L -o pshome_how_commerce_stores_work.txt https://huggingface.co/datasets/pebxcvi/PSHomeCacheDepot/resolve/main/DEV/Misc/pshome_how_commerce_stores_work.txt
4.93 kB
| My current understanding is that PS Home checks PSN for purchased Product IDs and retrieves the Entitlement IDs associated with those purchases through an NP ticket. | |
| The NP ticket is requested using a Service ID when the game starts. These Service IDs are listed in the corresponding Inventory/*/ServiceIds.xml files. | |
| For example: | |
| Issuing MITM request for domain: UP9000-NPUQ00020-00.auth.np.ac.playstation.net | |
| Inu: Requesting NP ticket for service ID UP9000-NPUQ00020_00... | |
| Inu: NpManagerCallback - event = 255, result = 00000178... Ticket downloaded! | |
| [ENTITLEMENT] 8 entitlements present in ticket. | |
| In this example, UP9000-NPUQ00020_00 is the Service ID used to request the NP ticket. The downloaded ticket contains the Entitlement IDs associated with products owned by the account for that service. | |
| A Product ID identifies a product on the PSN Store. Each Product ID can be associated with one or more Entitlement IDs. A normal product may provide one Entitlement ID, while a bundle may provide multiple Entitlement IDs. | |
| The number of Entitlement IDs that can be returned in a single request depends on the NP ticket version. Ticket version 2.1 can contain up to 500 Entitlement IDs, while ticket version 3.0 can contain up to 2,500 Entitlement IDs. | |
| I do not believe there is a way to make PSN issue an NP ticket containing a Product ID and its corresponding Entitlement IDs without first purchasing that product through the PSN Store. | |
| The Commerce Point uses the Product ID stored in the ODC to display the product information and process the purchase. After the purchase, PS Home uses the Entitlement IDs returned through the NP ticket to determine which UUIDs should be added to the inventory. | |
| For example, I placed the free Product ID UP9000-NPUQ00030_00-VMVDPRSTMSKFMLX3 into the ODC entry for the premium item 14A4F221-4EFD46C1-9CE21EFE-A1DEAB91, which is a pony LMO. | |
| The free Product ID is normally associated with UUID A548BF0A-B55C440D-A75177E0-13ECBB3D. | |
| When I attempted to purchase the pony LMO through the Commerce Point, the PSN Store displayed the name and description associated with Product ID UP9000-NPUQ00030_00-VMVDPRSTMSKFMLX3. | |
| After completing the purchase, the game added UUID A548BF0A-B55C440D-A75177E0-13ECBB3D to my inventory instead of the pony LMO. | |
| I then added the Entitlement ID associated with Product ID UP9000-NPUQ00030_00-VMVDPRSTMSKFMLX3 to the HCDB metadata entry for pony LMO UUID 14A4F221-4EFD46C1-9CE21EFE-A1DEAB91. | |
| After making that change, I rebooted the game. Both UUIDs were then added to my inventory. | |
| The Entitlement ID listed in the ODC had no effect, even after it was changed to LUA_REWARD. | |
| The Product ID stored in the HCDB object catalogue also had no effect. | |
| I then restored the original Product ID in the ODC entry for UUID 14A4F221-4EFD46C1-9CE21EFE-A1DEAB91. Both items remained in my inventory after rebooting the game again. | |
| This suggests that the free Product ID was only required to complete the initial PSN purchase and obtain its associated Entitlement ID. | |
| When the game starts, PS Home requests an NP ticket using the configured Service ID. PSN returns the Entitlement IDs associated with the account's purchased products. | |
| PS Home then adds the returned Entitlement IDs to the premium SQLite database table. It checks the HCDB metadata SQLite table for catalogue entries associated with those Entitlement IDs and uses the objects SQLite table to look up their corresponding UUIDs. | |
| Because the Entitlement ID associated with Product ID UP9000-NPUQ00030_00-VMVDPRSTMSKFMLX3 was assigned to both items in the HCDB metadata table, the game recognized both UUIDs as owned and allowed both items to remain in the inventory. | |
| The process appears to work as follows: | |
| PS Home requests an NP ticket using a Service ID when the game starts. | |
| PSN returns the Entitlement IDs associated with the account's purchased Product IDs. | |
| PS Home adds the returned Entitlement IDs to the premium SQLite database table. | |
| PS Home searches the HCDB metadata SQLite table for catalogue entries containing those Entitlement IDs. | |
| PS Home uses the objects SQLite table to look up the UUIDs associated with the matching catalogue entries. | |
| Every matching UUID is then recognized as owned and added to the inventory. | |
| PS Home boots | |
| | | |
| v | |
| Reads Service IDs from: | |
| Inventory/*/ServiceIds.xml | |
| | | |
| v | |
| Requests an NP ticket from PSN | |
| using the configured Service ID | |
| | | |
| v | |
| PSN checks the account's | |
| purchased Product IDs | |
| | | |
| v | |
| The NP ticket returns the | |
| associated Entitlement IDs | |
| | | |
| v | |
| PS Home adds the Entitlement IDs | |
| to the premium SQLite table | |
| | | |
| v | |
| PS Home searches the HCDB | |
| metadata SQLite table for entries | |
| using those Entitlement IDs | |
| | | |
| v | |
| Matching catalogue entries are | |
| looked up in the objects SQLite table | |
| | | |
| v | |
| The associated UUIDs are found | |
| | | |
| v | |
| Every matching UUID is recognized | |
| as owned and added to the inventory |