Office Connect - Internet Application Developer

Features and Functionalities

Ready To Go Hosted
Infinitium IMS provides a “ready to go” hosted solution model whereby all the infrastructure are ready for deployment. Minimal time to market and eliminates the need to manage the system and maintenance functions.

Elimination of Static Password
One of the most significant enhancements with IMS is the ability to eliminate the need of Static Password. Card Holder does not need to register and remember any password.The challenges of forgetting and resetting the password is also eliminated.

Mass Enrolment
Enrolment and Registration has always been the Achillies’ heel of the 3D deployment for the Issuer due to it’s complexity and customer participation issues. With IMS, Issuer can proceed with Mass Enrolment without requiring further “action” from cardholder. With these flexibility and simplicity, the 3D secure adoption will be successful.

Expansion to Multi Payment Channel
Issuer can extend IMS’s authentication capabling to handle multiple payment channel such as MOTO, Mobile Commerce, Auto-bill and IVR. This will provide the card holder with a common and seamless authentication methods everytime they used their card regardless of the channel of the merchant.

Transaction Alert
Every time a credit card is been used in CNP scenario, IMS will send an authentication message to the cardholder mobile devices. The cardholder will be able to report a fraudulent transaction in real time if they ever suspect that their card has been compromised. IMS can trigger the bank host to temporarily suspend the card in such event. This will help the bank to further minimize fraud and chargeback.

Full Compliance
Infinitium IMS is designed to be fully compliant with payment standards in mind. IMS supports both Visa’s 3D Secure and Mastercard SPA-UCAF standards. Infinitium IMS is in compliance with PCI-DSS. In addition, Infinitium strong in-house R&D team and innovative support ensures that the product stays relevant in today’s dynamic world.

Enhanced Security with Dynamic Authentication
IMS enhances the standard customer authentication protocols such as Visa’s 3D Secure and MasterCard’s SPA-UCAF with additional processes via the IMS adaptor. The IMS not only offers the capability for 2 Factor “Out of Band” authentication via mobile devices, it also eliminates the threats of Phishing, Trojans, Man-In-Middle attack and keyboard logging.

Infinitium IMS also supports a wide range of authentication methods providing flexibility to Issuer to pick and choose different authentication methods that suits the market demand. Some of the possible authentication methods includes:-

IMS Authentication Processing

1	Shopper browses at merchant site, finalizes a purchase and makes payment. Merchant now has all the necessary data to begin 3D Secure processing, including card number.
2	Merchant Server Plug In (MPI) which may be hosted by the Merchant, the Acquirer or a third party will send card number to Visa/MasterCard Directory Server.
3	If card number is in a participating card range, Visa/MasterCard Directory Server queries appropriate ACS to determine whether authentication is available for the card number. If no appropriate ACS is available, the Visa/ MasterCard Directory Server creates a response for the MPI and processing continue with Step 5.
4	IMS's ACS responds to Visa/MasterCard Directory Server.
	Visa/MasterCard Directory Server forwards ACS response (or its own) to MPI.
5	MPI sends Payer Authentication Request to ACS via shopper’s browser.
6	MPI sends Payer Authentication Request to ACS via shopper’s browser.
7	IMS's ACS receives Payer Authentication Request
8	Cardholder enters password using authentication method which is applicable to the card number. IMS's ACS authenticates shop per for the card number, then formats the Payer Authentication Response message with appropriate values and signs it digitally. The Payer Authentication Response message contains an ECI (Visa)/ UCAF(MasterCard) value indicating the authentication result. The CAVV(Visa)/ AAV(MasterCard) values which serve as a proof that authentication happens.
9	IMS's ACS returns Payer Authentication Response to MPI via shopper’s browser. Meanwhile if this is a Visa card, authentication result will be sent to Visa Authentication History Server (AHS).
10	MPI receives Payer Authentication Response.
11	MPI validate Payer Authentication Response signature. (either by performing the validation itself or by passing the message to a separate Validation Server).
12	Merchant proceeds with authorization exchange with its Acquirer. Acquirer processes authorization with Issuer via Visa/MasterCard Net, then returns the result to Merchant. When issuer bank receives authorization request from acquirer bank, the issuer bank needs to validate the ECI/UCAF and CAVV/AAV value. Issuer bank may opt to reject the authorization in case of the 3D authentication is failed or the CAVV/AAV value is not valid. Customization at issuer bank host is required to read the ECI/UCAF value and validate the CAVV/AAV.
13	Acquirer return the authorization result to Merchant.