In BILLmanager, fraud protection is implemented through mandatory verification of clients by mobile phone number. Third-party phone number verification systems are used for this purpose. To connect BILLmanager to such a system, add a phone verification gateway.
Clients without a verified number will not be able to order services covered by fraud protection. Clients can verify their phone number:
- On the main page of the client area → click Verify phone number. The button is hidden if the client has a verified number.
- In the cart → the Verify phone number button replaces the Pay button. The mechanism works when a client without a verified number orders a service with a fraud protection system.
Fraud protection
To enable fraud protection, enter Provider → Global settings → Client verification.
- Specify at what point the Phone number confirmation is required:
- before paying for the order;
- after paying for the order;
- after registration.
- Specify the Number of attempts to receive a code and Number of attempts to enter code. Read more in Global settings.
- Click Ok.
After saving the settings, the sections Settings → Fraud protection and Integration → Phone verification gateways will appear in the left menu.
Protection for orders
You can specify product types or specific pricing plans that require the customer to have a verified (verified) phone number to order. To do this:
- Enter Settings → Fraud protection.
- Select the provider → click Product types.
- Select the product type → click Tariffs.
- Set the required values for the selected tariffs with the Enable and Disable buttons.
You can configure the periods which will be covered by the verification when ordered. Click Periods in the relevant section and enable the required periods.
If a larger entity is enabled, fraud protection will apply to all child elements: product types, order periods, tariffs.If fraud protection is enabled for a larger entity, the settings of child elements will not be available. For example, if you enable fraud protection for a product type, the button to go to the individual tariff protection settings will not be available.
SMS gateways
Set up integration of BILLmanager with SMS text messaging service.
To add a new gateway, enter Integration → Phone verification gateways → click Add:
- Creating a gateway. Select the service:
- SMS center (call);
- TeleSign;
- Clickatell;
- Devino Telecom;
- GREENSMS;
- MobilMoney;
- QuickTelecom;
- SMS center
- http-SMS;
- SMS Traffic;
- TurboSMS;
- http-SMS — If the required service is not available, use a universal gateway.
- Gateway parameters. Fill in the data for integration with the messaging service:
- Name — the name of the gateway in BILLmanager;
- Provider — select the provider for which this gateway will be used. Leave the field blank so that the gateway is used for all providers;
-
Notification types — select the types of notifications that will be sent through this gateway. If no sending gateway is configured for the notification, it will be sent through the first gateway suitable in terms of sending method.
Example - Number filter — a number filter set by a regular expression. Only numbers that satisfy the regular expression can be verified through the gateway. If no filter is set, any phone number can be verified through the gateway. Before verification, all characters that are not digits are removed from the number. Example of an expression to validate numbers from Russia: "^[78][0-9]{10}+$".
- Priority — the priority by which the gateways are sorted when the client verifies the phone number. The bigger number has the higher priority;
- Timeout (minutes) — waiting period before sending the code again;
- Code validity period (minutes) — the period after which the code will be considered invalid;
- Activate after creation — activate the option to enable the gateway after creation;
- Message text — message text for users of the specified localization;
- Specify the data for authentication in the messaging service.
Universal gateway
The form of the universal gateway configuration is different, because the provider needs to specify data to connect to the service via API:
Use macros in the API request template:
- {phone} — phone number;
- {message} — message text generated from an EJS template;
- {sender} — sender's signature. The value from the Sender field is used.
All the necessary information for connecting to the SMS service via API can be found at the service provider's website.
Gateway selection algorithm
When multiple security gateways are added to the system, the selection is performed according to the following algorithm:
- The gateway with the highest priority among all active gateways is selected.
- The specified number is checked against the gateway filter. If the phone number does not satisfy the filter, the gateway is skipped.
- When the first suitable gateway is found, the search stops.
Logging
The logs of the connected gateway modules are named as gw<service name>.log or fg<gateway name>.log:
- /usr/local/mgr5/var/fgsmsc.log
- /usr/local/mgr5/var/fgsmsgate.log
- /usr/local/mgr5/var/fgtelesign.log
- /usr/local/mgr5/var/gwclickatell.log
- /usr/local/mgr5/var/gwdevinotele.log
- /usr/local/mgr5/var/gwgreensms.log
- /usr/local/mgr5/var/gwmobilmoney.log
- /usr/local/mgr5/var/gwqtelecom.log
- /usr/local/mgr5/var/gwsmsc.log
- /usr/local/mgr5/var/gwsmscustom.log
- /usr/local/mgr5/var/gwsmstraffic.log
- /usr/local/mgr5/var/gwturbosms.log
Universal gateway
Universal module log file: /usr/local/mgr5/var/gwsmscustom.log.