Client account and profile¶
Basic principles¶
Every payment request which is identified with unique parameters considered to be a separate account/profile entity within the system. Accounts and profile data are initially collected from payment request headers and body parameters.
If account already exists in database then decision based on payment flow settings is made and a customer goes through pay-through flow or through wallet funding first process.
Each transaction/payment processing flow is tagged/marked with designated to this flow account.
Each account includes profile date (phone number, name, email, supportive documents, date of birth, etc)
Client due diligence¶
Client requires to perform due diligence within the system once overall turn-over on its wallet exceeds pre-defined threshold
By due diligence we mean verification and validation of customer personal data
Client verification includes: phone number, email, name, date of birth
Client validation includes: person identification (id document), proof of address, proof of funds, proof of card possession.
Client validation is automatically performed using authorized 3d party service providers (Face recognition, MRZ recognition, Address validation services)
Risk management team tracks validation performance using dedicated web interface and have an option manually chang validation statuses for specific customers.
Client due diligence is applied to individuals, business representative and commercial entities
Account types¶
Pale account
Pale account type is assigned to an account in case of pay-through payment mode enabled, where no information for comprehensive verification process is collected
Client due diligence procedure is not applicable to this type of accounts
Pale account profile information depends on payment method choice
(ex. if classic credit/debit card is chosen then cardholder name will be collected and assigned to the profile name field)
Pale account type could be converted to any account type by collecting additional info from the client
Pale account type describes an account as the weakest related to risk and fraud protection of its type
Personal account
Personal account type requires phone number, email and client name verification to be accomplished
Client due diligence procedure is applicable and presented by simplified process of phone number validation with a text code
Personal accounts considered to be verified and partially validated
Personal account type has a pre-defined lifetime turn-over limit, breaching which triggering Green account upgrade process
Green account
Green account is a personal account which has been fully verified and validated
Green account type has a pre-defined lifetime turn-over limit
Business account
Assigned to a commercial clients, traders, merchants
Enhanced due diligence process including beneficiary identification and legitimacy of operations is performed on each account of this type
Business accounts have access to API endpoints to process payments
Business accounts are the subject of merchant fraud prevention system and shall be framed with number of limits (transaction amount, average ticket size, allowed countries, etc)