Fulfillment callback is used to:
Nexway provides a standard fulfillment client side REST APIs with predefined set of calls/actions and a common payload.
In this documentation, some words refer the same entity: Customer, Publisher and Partner means "you".
A common payload called LicenseRequest Resource will be sent by the Nexway Monetize Platform for all requested actions.
You can use the Swagger Editor to generate api server skeleton code for your language (PHP, java, ...).
Each action is associated to an event on the Nexway Monetize Platform. Some actions are only useful in a subscription context.
|Action||Event on Nexway side||Endpoint called on your side||Usage|
|New||Order is confirmed||http://yourserver.com/licenses/new||Activate or get a license key for a product|
|Cancel||Order is canceled||http://yourserver.com/licenses/cancel||Cancel/Revoke a license key|
|Renew (subscription only)||A subscription product was renewed||http://yourserver.com/licenses/renew||Get a new key or extend key validity|
|Suspend (subscription only)||A subscription product was suspended||http://yourserver.com/licenses/suspend||Suspend/Cancel a license key|
|Reactivate (subscription only)||A subscription product was reactivated||http://yourserver.com/licenses/reactivate||Reactivate a license key or get a new one|
Nexway provides a sample fulfillment server to test the expected behaviour that you have to implement on your side. Documentation is available here