Contracts
The contract is a set of rules which is defined for every organization type. The contract determines transaction-based commissions and limits for organizations.
Organization types are:
- Individual
- Merchant
Contract type
For each organization type, there are several contract types.
By default the following contract types are available:
- base
- standard
- gold
- vip
By default, while an organization is created a “base” contract type is assigned.
Each contract type may have a set of commissions and limits, manageable by the system user with relevant permission, that’s how you can offer different terms of service for the different customers.
Example:
Preconditions
- Commission for internal p2p-transfer may have different values for Base, Standard and Gold contracts:
- 2% OUT for Base
- 1% OUT for Standard
- 0% for Gold
- 0% for VIP
- Customer decided to transfer 100 USD to another Customer within the system
Calculations:
Total p2p-transfer amount(including system commission) will be different for different Customer contract types:
- Base:
- 100USD + 2%*100USD = 102 USD
- Standard:
- 100USD + 1%*100USD = 101 USD
- Gold:
- 100 USD (zero commission)
- Vip:
- 100 USD (zero commission)
It is also possible to create the new custom contract type by copying it from the existing contract and setting up the required commissions and limits.
Contract changing flow
Contracts for organizations can be changed when the organization is already approved by compliance.
For Example, Business User is created with contract type Base. Once client’s profile is approved by compliance he will be switched to Standard contract type.
The contract doesn’t need additional actions for activation and can be linked to the customer right after creation.
Any contract change action is being saved to logs and can be monitored if required.
This behaviour can be changed in the system configuration by updating newPersonType from standard to base for the required organisationType (individual or merchant) for compliance.approval parameter.
The default configuration is:
compliance: approval: - organizationType: 'individual' newPersonType: 'standard' - organizationType: 'merchant' newPersonType: 'standard'
To keep base person type after approval, configuration should be:
compliance: approval: - organizationType: 'individual' newPersonType: 'base' - organizationType: 'merchant' newPersonType: 'base'
Through contract management the service user with appropriate permission (CFO) can set available operations, commissions and limits for the particular Contract type. By default all operations within a Base Contract are allowed.
To allow/prohibit certain operations, the service user should activate/deactivate the commission profile for such specific operation.
A contract consists of:
Commission profiles – determines transaction types for applying commission and if operation is allowed or not
Commission rules – are linked to the commission profile and determine period of commission validity
Commission conditions – are linked to the commission rule and determine commission ranges and values
Limit rules – are linked to the commission profile and determine limit settings for particular operation types.
Check the Back Office manual for Contracts Management Functionality
APIs: Contract Management – commission profiles
APIs: Contract Management – commission rules conditions