Here are the features:

1. Vqmod based module. No change on opencart codes.

2. Works just before “any” payment process.

3. Supports phone or sms verification type, which can be set from administration page

4. Automated number format checking

5. Built-in country code prefix adding (no need for country pull down)

6. Phone Verification template (what’s to be said on the phone call) can be customized

7. SMS Verification message can be configured

8. Phone number blacklist

9. IP blacklist

10. Automatically promote customers to a specific group

11. Bypass verification for specific customer groups (like wholesale)

12. Limit #verifications per sale, according to date, time

13. Set retry time between trials

A live demo is at opencart.onverify.com

Contact onverify.com to get the full package. We will announce the public package in near future.

Here are the highlights:

1. Automated number validation
2. Phone and/or SMS Verification (can be set exlusively or can be left to the user)
3. Ability to retry verification in case customer cannot pick up phone
4. #retries limited on panel
5. Time interval between retries can be set
6. SMS message can be changed from panel or language file
7. Phone verification template can be set, managed over onverify.com
8. Option to verify all orders (verified customers is bypassed by default)
9. Number of digits on pin can be selected.

See it in action at http://184.82.94.94 (or whmcs.onverify.com)

We are working on the final bits of the module, we will announce when module goes alpha. Till that time all comments are welcome, we will be happy to add a new feature you like to see in this module

1. Standard SMS Verification. OnVerify delivers in a robust, highly available environment. Only bills, “valid”, “live” phone number verifications. (Why do you pay for wrong mobile numbers?)
2. Reverse SMS Verification. Add a second step to the verification, not only you check the sms deliverability, but also you complete the verification over user’s mobile phone.
3. POP SMS. This is an exciting new service, which pops verification pin on user’s phone. This SMS is not stored on phone. It’s single use, and not stored. Very suitable for otp use. All phones supported. Works over GSM networks.
4. Reverse POP SMS. This service is an extension to POP SMS. Not only it delivers a pop message on the phone, you can also get the pin from the user. Zero cost to the customer. Enhanced and flexible service.

1. Robust infrastructure. System not only fail overs, undeliverable sms are re-routed to alternative providers. Re-routes, re-sends are not billed extra. You are charged per transaction.

2. Automatic number format checking. No worries in case your customers provide a wrong number, we don’t bill it. Instead return error,

3. Worldwide numbering plan checking. Together with number format checking, we also check if country code + prefix is defined. In real time, without an extra cost.

4. We do not bill or try to deliver to a mobile number if the number is not “live”. Ask this especially from your current sms verification provider.

Give it a try at onverify.com. There is online sms verification demo at demo page. Account opening is free. Don’t pay till you test and see it working.

For example, if you see too much fraud from a country that you see safe, add this country to your fraud monitoring/scoring system. If you see too much from from a phone number, add prefix and type of it. Examples dont stop.

Your fraud monitorin/scoring system is a live one.

OnVerify.com provide free number type and number address for all verifications. It’s easy to use and implement

If number of orders are high during the day, or it’s hard to place a staff for this calling operation;  here comes Automated Phone Verification & Confirmation. Automated Phone Verification & Confirmation will help you automate your Order Checking process via phone; no hardware, no special software, and no personnel to run this. OnVerify.com provides a solution.

OnVerify.com helps you to Automate the Phone Verification and Phone Confirmation process. All you need to do is to integrate OnVerify.com API into your existing code and process.

Also, keep in mind that, marking an order for extra check for fraud, depends on your business model. If you target end-users, or let your customers try before buying, your customer may want to try or buy with a free personal e-mail. On the other side, if you explicitly sell to companies, or your products are highly priced, you must watch free e-mails.

AVS provides following common results:

A – The address matched, but the zip code did not. This is for Mastercard, Visa, and AMEX users.
Y – Address matched, but the zip code did not for a Discover card user.
B – The street address was a match, but the postal code was in the wrong format for the international user.
C – The street addresses and postal codes were formatted incorrectly.
D – The street address and postal code match for an international user.
E – There was an error.
G – The service is not supported by a non-US user.
I – Address information was not verified by the international issuer.
M – T street address and postal code match for an international user.
N – There is no match for the zip code or the address.
O – No Response was sent.
P – While the postal codes match, the street addresses cannot be verified due to inconsistencies in the formats.
R – You should retry. The system is temporarily unavailable or has timed out.
S – The server is not supported by the user.
U – The address information is unavailable.
W – The nine digit zip code matches, but the address does not.
X – This is an exact match.
Y – Both the address and the zip code match.
Z – The five-digit zip code matches, but the address does not.
0 – There is no response.

Unless your customer base is not US only, do not use AVS. Just IP to county/city mapping will bring more information.

A BIN database provides the merchant with information about the issuing bank such as the country it is located in, the customer’s billing address and other helpful information. The merchant can use this information as a factor in deciding whether or not to approve a transaction. If a card’s BIN is not found in the database, the merchant can decline the transaction to avoid fraudulent activity.

Many online merchants also use BIN databases to determine what type of card is being used to pay for a transaction, such as a credit, debt, or prepaid card. The reason for this is that prepaid cards have a higher rate of fraud. Many merchants use a prepaid flag that will alert them when the card is prepaid so they can either inspect it more closely or simply reject it to be safe. Putting such practices into place can significantly reduce a merchant’s risk of loss from fraud.

Following information can be cross-checked and can add scoring :

1. Customer’s country and Bank’s country will most probably match. A mismatch may be flagged
2. Prepaid cards can be flagged.

One of the most notable database is available at: www.binbase.com