Updating Your Game
Once a purchase is complete, we'll send you a purchase.completed
event in near-real time to start the fulfillment process. See Webhooks and Callbacks for more on how our webhooks work, and how you can set up a server to listen for events.
Broadly, we use two pieces of information to help you fulfill the purchase:
accountId
, which is an ID that uniquely corresponds to the in-game account that needs to be credited- For Neon-managed storefronts, we collect this from the authorization process.
- For standalone checkouts, you pass this in when you create the checkout via API.
sku
, which is a unique code for the item(s) being purchased- For Neon-managed storefronts, this is the
sku
you pass in when creating your offers. - For standalone checkouts, you pass this in when you create the checkout via API.
- For Neon-managed storefronts, this is the
We'll also provide you with other data relevant to the purchase, like a purchase ID, as well as subtotal, tax, and total amounts. We'll also provide you with the purchase order number, which is the code shown to the user in their confirmation email, and in the success page (for Neon-managed storefront integrations). (The purchase ID is also unique to the purchase, but is used for API operations only.) This code can be used for communicating with the user about their purchase.
We highly recommend storing the purchase ID you receive from the webhook in your system for future reference.
Updated over 1 year ago