Licensing Instructions

Limited Distribution Licensing

To license the components for distribution first visit the URL below to generate a Runtime License value.

https://www.4dpayments.com/full/DPJHV

After obtaining the Runtime License value assign this to the RuntimeLicense property to license the application for deployment. For instance:

component.setRuntimeLicense("<value from above>");

This provides a license to the component and your application will run without a license prompt on any machine to which it is distributed.

Note that each component instance in your code must be assigned a RuntimeLicense value.

Trial Licensing

To activate a trial version license either run the setup .exe file (Windows only) or follow the instructions below (all other platforms).

Visit the URL below to generate a 30-day Trial Runtime License value.

https://www.4dpayments.com/trial/DPJHV

After obtaining the Runtime License value assign this to the RuntimeLicense property to license the application for deployment. For instance:

component.setRuntimeLicense("<value from above>");

This provides a 30-day trial license to the component and your application will run without a license prompt on any machine to which it is distributed during that time.

Note that each component instance in your code must be assigned a RuntimeLicense value.

Single Server License Installation

To activate a full version license either run the setup .exe file (Windows only) or follow the instructions below (all platforms) to activate a license from the command line.

Navigate to the "lib" directory of the installation and execute the following command:

java -jar inpay.jar

When prompted enter your product key. This will create the file "DPJHV.lic" in the current directory next to the "inpay.jar" file.

The "DPJHV.lic" file must reside next to the "inpay.jar" file or in the ".DPayments" directory under the user's home directory.

License Transfer

If you would like to transfer your license to another system, please complete our license transfer form. This will ensure your installations are not mistaken for license violations.

For additional information about our product activation process, please refer to our product activation FAQ.