REST API Reference

Business Definitions

User Verification Status:

User can be unverified, Limited, Confirmed, Trusted with a trust score of 1-10 Program manager can setup the verification requirements in the system based on the program user security preference.

User Verification Requirements:

User Verification Setup

The default user verification setup is as follows:

User Trust Level

The User Trust score is as follows:

Transaction Limits:

Program manager can define transaction limits based on the User Trust Level that includes Daily, Monthly, and Yearly; transaction limits for funds deposits, withdrawals, and transfers; higher Trust Level means the user can more transactions.

Accounts

Accounts belong to Users and the system supports the following account types:

1. E-Wallet: General account that can be used for mobile or online transactions.

2. Points: Reward account that can accumulate points.

3. Debit Card (Visa/MasterCard): Accounts issued on Visa/MasterCard network with the following subtypes:

4. Accounts funding: all account regardless of type can be configured for one time fund load or reloadable.

5. Account expiry: All account must have expiry date, usually E-wallet and Points account expiry is set to 5-10 years and Debit Card accounts is set to 1-2 years from the date of creation.


Account creation and activation requirements:

Accounts must be first created and then activated; this can also be done in a single process depending on the account type and the program configuration.


Account creation:

In order to create accounts in the system, the following Account creation requirements must be met:


Account activation:

In order to activate accounts in the system, the following are Account activation scenarios:

1. Auto activate account setting: The system will auto create and activate an account upon the successful creation of a User and the Account creation requirements are met; the Auto activate accounts only work for new User account creation; this option can only Create one Account for each type and currency configured for the program.

2. Account creation and activation: Program credential can create an activate accounts in one request by calling the Account end point; this is usually used for adding new Accounts to Users after the User creation.

3. Physical Debit Card activation by User credential: If the card requires activation by the user after receiving the card by the User, the User must enter the card activation code to activate the card.


Number of Accounts per User:

There is a setting to the number of allowed accounts for each type and currency that can be created per User in the system. (program configuration and can be modified).