UniPay Properties Definition

Property Locations:

Type	File Path / Table Name
Build	build.properties
Build	gradle.properties
Database	iapp_settings
File	camel-config.properties
File	config.properties
File	ibilling-client.properties
File	unibroker.properties
File	unipay-build.properties

Property Location Types:

Database	run-time property used by the application and stored within a database
File	run-time property used by the application and stored within a file
Build	build-time property used by the application and stored within a file

Available Properties for ibilling-client.properties:

connection.type
debug

payment-option.verification-amount
processor.host

Property Definitions for ibilling-client.properties:

connection.type

Added On: 04/06/12

Legacy Name:

Group:

Status: Active

Attributes: Required Default ( xml )

Indicates which communication protocol should be used for communication between a client and UniBill server.

Possible values:

xml - communication is done using XML over HTTP/HTTPs;
rmi - communication is done over Java RMI.

debug

Added On: 04/06/12

Legacy Name:

Group:

Status: Active

Attributes: Default ( false )

Indicates whether debug mode is turned on. When set to true, request and response information will be traced in debug log. When set to false, no additional debug info is provided.

payment-option.verification-amount

Added On: 04/06/12

Legacy Name:

Group:

Status: Active

Attributes: Default ( 99 )

Amount in cents that should be used to run verification transactions. A verification transaction is an authorization on a credit card, which is never settled. The purpose of the authorization is to verify that the card is valid and thus could be subsequently used for recurring billing.

Note: verification process doesn't verify (and can't really verify) that the card has sufficient balance to cover future charges.

processor.host

Added On: 04/06/12

Legacy Name:

Group:

Status: Active

Attributes: Default ( http://localhost/ibilling/xmlhttps )

Host (URL) of the connection gates (XML or RMI) that should be used to communicate with UniBill API.

Note: URLs for XML and RMI communication are different even when underlying physical server is the same.