e-commerce

One-Time CVV2

<A new set of product options, separately licensed>

Now you can make e-commerce transactions more secure for cards that don’t have static CVV2. Typically, it would be virtual cards or private-label closed-loop cards. They are not eligible for 3-D Secure, but our new functionality reuses standard authorization channels to guarantee these cards a similar level of fraud protection. 

To make an online purchase, your customer begins with providing the card number and expiration date on the e-store checkout page. WAY4 generates a one-time CVV2 for this card and sends it via SMS or alternative delivery channels. After the cardholder enters the received value on the e-commerce page, the payment is confirmed.

Account Updater Service

<New set of product options, separately licensed>

The Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (MABU) services help merchants to process account-on-file transactions and recurring payments on renewed or replaced cards without interruption, and to get earlier notifications concerning the card closures. Now our system supports this feature for both issuers and acquirers.

After issuing, reissuing or closing a card, WAY4 generates VAU/MABU files. They are sent to the IPS network for the benefit of other scheme members.

Mobile Authentication Application

<Product under development>

OpenWay has developed a special mobile app to improve the cardholder e-commerce payment experience. The app uses biometrics and other user-friendly authentication methods, instead of OTP from SMS. It saves cardholder time and issuer's money usually spent on the SMS service. 

To complete an e-commerce transaction, buyers are usually redirected from merchant websites to the issuer’s portal (ACS). At this point you can offer authentication via mobile. The cardholder receives a push notification from the app, opens it and confirms the payment by fingerprint (or passcode).

 The solution includes:

  • Mobile application for Android and iOS

  • SDK for embedding the authentication functionality into 3rd party apps (e.g. mobile banking app)

  • Application management tools (solution back-office)

  • Interface between the app and ACS