Wallet mode can be any of the following:
On classic mode, wallet is treated as a simple running transaction. Everytime a user is credited or debited, a transaction is inserted to the database.
On fixed liability mode, wallet transactions are always linked to a Master ID. Everytime a user is credited, the Master ID is debited, each time a user is debited, the Master ID is credited. This creates a security making the liability of the company fixed based on the initial amount infused to the Master ID.
Wallet Mode can only be changed by the server administrator via VirtualHosts configuration usually through a properly documented and signed request. Consult your website service provider for details.
If the wallet mode is in Fixed Liability Mode, all transactions are always linked to Master ID. Master ID doesn't serve any purpose on Classic mode.
ID Type can be any of the following:
INTEGER type can have a maximum of 2,147,483,647 IDs
while INT64 type can have a maximum of 9,223,372,036,854,775,807 IDs
Only server administrator can change this through a properly documented and signed request. Due to extra resource required when using INT64, extra charge may apply depending on the service provider.
Every time a transaction is generated, an ID which is an incremental integer is generated to identify the transaction. Current ID is the current numeric unique identifier assigned by the system.
Depending on the ID Type, Maximum ID is the highest unique integer that can be assigned to a transaction.
Over time, generation of unique identifier can consume all the possible ID, this is the estimated time all ID are used up. This is based on the average ID used per day.