Verified by Visa y MasterCard Secure Code are the new online Authentication system, which allows Online Purchases with the confidence that exists in the physical world, Quickly and Easily.
	Now the Cardholder can make purchases on the Internet and put your VISA and / or MasterCard at merchants that are participating in 3D SECURE with the guarantee and security that only VISA and MASTERCARD can offer and have the peace of mind that your transaction will be 100 % safe. Learn more by browsing the DEMO or from the menu.

			Cardmember Benefits
			Increased safety of consumers in their shopping online.
			You only need a password to purchase and your card to purchase.
			The system is very simple and easy to use.
			Not require any special software applications to access device of the cardholder.
			It is a global authentication system.
			Use the same card you currently.

			How does Verified by VISA?
			First, the cardholder must register for the service, one-time registration by visiting your issuing bank. During the registration process, you are the cardholder made a number of questions for security purposes, after which, select a password to authenticate yourself, and remember a phrase that is used as a message of personal guarantee for the Bank Issuer can authenticate a transaction.

			3-D Secure: The technology behind Verified by VISA
			The 3-D Secure protocol supports the new VISA payment service designed to enhance and validate payments made through the Internet.3-D Secure is an authentication technology that uses encryption Secure Socket Layer (SSL) and a Plug-in the Trade Server and verifies that informs participants for authentication during an online purchase. It also protects your payment information during transmission card online. 3-D Secure has two main functions: registration and authentication. And the model is based on three domains: Issuer Domain: The cardholder shops online, providing the account holder name, card number, and expiration date, either directly or via software such as a digital wallet, then indicates readiness to finalize the transaction. In response to the Purchase Authentication Page, the cardholder provides information needed for authentication, such as a password. Acquirer Domain: Existing merchant software handles the shopping experience, obtains the card number, then invokes the Merchant Server Plugin to conduct payment authentication. If payment authentication is successful, the merchant software submits an authorization request to the Acquirer. Interoperability Domain: This domain facilitates the exchange of transactions between the two domains using a common protocol and shared services.

			Registration
			Registration is the process by which the cardholder is authorized to use the service. We present a model of a registration procedure: 1. The cardholder visits the website of the issuer and indicate a card number, expiration date, other identifying information specified by the issuer, along with any shared secret is required as a security password or personal message. 2. The issuer validates the information supplied by the cardholder and notifies you that have registered successfully. 3. The registration server provides an update to the Access Control Server, including the number of newly enrolled card and any other information that is required for subsequent authentications purchases, such as password.

			Authentication
			After registration, the cardholder and can be purchased at any participating merchant site where a trade has integrated its Plug-in Commerce Server to 3-D Secure. We present a model of an authentication procedure: 1. The cardholder selects the materials or services and proceed to the checkout page trade. 2. The Server Plug-in Trade Directory VISA consultation on the participation of the cardholder. If the card is in the range of cards involved, the Board requests the Access Control Server for the Issuer to validate the involvement of the cardholder and sends the response to Server Plug-in trade. 3. The Plug-in Trade Server sends an authentication request to the Access Control Server through the cardholder browser. 4. The Access Control Server cardholder requests the password, who admitted to be later verified by the Access Control Server. 5. Access the server by the authentication response back to the Plug-in Commerce Server via the cardholder browser, and then transmits a record of the authentication to the Authentication History Server. 6. The Server Plug-in validates the response Trade. 7. If authentication is successful, proceed to payment authorization.