IDentiWall Non-repudiation – For card-not-present e-commerce

 Target market

               Any e-commerce merchant.

Product description

IDentiWall Non-repudiation is a powerful new tool for card-not-present businesses which totally eliminates Merchant liability for chargebacks and fraudulent transactions. It also inhibits consumer abuse of the chargeback system. 

IDentiWall Non-repudiation validates that the online or phone transaction is the legitimate cardholder's intention in a card-not-present transaction, thereby providing the level of security and confidence equivalent to a signed sales receipt. 

IDentiWall Non-repudiation provides Merchants with liability protection against chargebacks classified as fraud and also against cardholders claiming that they do not recognize a purchase on their monthly statement, which typically represents about 70% of all chargebacks received by card-not-present Merchants.

 IDentiWall Non-repudiation offers Merchants chargeback protection for those disputes and prevents the disputes from being submitted to their Merchant acquiring bank. In addition, these chargebacks are not factored into the overall monthly chargeback ratio.

Typical workflow 

• User initiates online transaction and pays by credit card.
• IDentiWall verifies the transaction via its built-in transaction verification workflow:
  • The transaction is suspended before the Merchant's web server processing.
  • An authorization window opens, requesting the customer to input a code, saying that it will be delivered by SMS to the customer's phone.
  • IDentiWall extracts a transaction summary that includes the important data such as ‘items ordered’, ‘shipment address’, ‘amount to be paid’, etc.
  • The transaction summary is sent to the customer’s mobile phone, via SMS, accompanied by a ‘one-time authorization code’.
  • The customer is then asked to copy the authorization code onto their order authorization window, sent to their desktop by IDentiWall.
  • When the authorization code arrives at the e-commerce site, it gets checked by IDentiWall and if found to be identical to the original authorization code, the customer’s original, suspended,  transaction is handed over to the web site for final processing.

Implementation issues

IDentiWall implementation doesn’t require code changes in any of the e-commerce applications.

IDentiWall can distinguish between those customers who are protected by it and those who are not, so there is no requirement to implement it for all of them. The IDentiWall protection is typically positioned as a VIP extra service.

Before implementing IDentiWall, the merchant has to make sure he has the mobile phone numbers of those customers who are intended to be protected by IDentiWall.

 If you wish to implement IDentiWall but have a problem with getting verified mobile numbers from your customers, please contact us to learn about the IDentiWall’s Simplified User Verification Process (SUAP). It’s easy and gets done solely by the customer without any merchant intervention.

More IDentiWall Authentication Security Products