License Creation/Renewal/Upgrade Request – Request

2 - Standard implementation is expected.

3 - With reporting implementation with Get License Key
Info Request support is expected.

When this field is absent, Standard (2) must be assumed.

• PURCHASE for the Create new scenarios.
• RENEW for the Renew scenarios.
• UPGRADE for the Upgrade scenarios.

Y means that the order is a test one. The license key
generated must not be accounted towards the billing report; it
could be a fake one though issuing a key that can be
successfully installed into an application is advised.

N or missing this field means that the order is real.

Activation data is a packet of tech data required to obtain a
valid application license. This parameter is specific to every
extension. Some examples of activation data include:

• White IP address
• Domain name
• Hardware ID
• Global unique identifier (GUID)

This parameter is optional. You can omit it if the license does
not require any activation data.

KA license number (without prefix and version).

Example: If the full license number
is EXT.00123456.0012, then only 00123456 will be passed in
this field.

ID/SKU of the product purchased.

The ISV endpoint should be aware of this ID/SKU in order to
distinguish between various products (if multiple products are
offered).

The date of purchase in the format DD/MM/YYYY, e.g.,
12/03/2016.

This date corresponds to the date when the current license key
action has been initiated, with no regard to the license
validity date or initial subscription date.