Implementing CVV Security Code Checking - Revision history

Sichen at 22:05, 16 July 2008

2008-07-16T22:05:42Z

Sichen: Protected "Implementing CVV Security Code Checking": Sysop page [edit=sysop:move=sysop]

2007-09-21T21:29:46Z

Protected "Implementing CVV Security Code Checking": Sysop page [edit=sysop:move=sysop]

Sichen: New page: The CVV/security code should be set from your screen to the ShoppingCart.CartPaymentInfo securityCode field. It will then be stored by the shopping cart in the OrderPaymentPreference enti...

2007-09-21T21:29:46Z

New page: The CVV/security code should be set from your screen to the ShoppingCart.CartPaymentInfo securityCode field. It will then be stored by the shopping cart in the OrderPaymentPreference enti...

New page

The CVV/security code should be set from your screen to the ShoppingCart.CartPaymentInfo securityCode field. It will then be stored by the shopping cart in the OrderPaymentPreference entity as the "securityCode" field, and after the PaymentGatewayServices (line 1741) performs an authorization, it will clear the securityCode field so that it is not stored long term, in accordance with [http://www.chasepaymentech.com/solfraprocarnotpredatsecreq.do#prohibited prohibited data requirements]. The credit card payment processor should then pass OrderPaymentPreference.securityCode to the gateway as the security code.

For an example, see [http://sourceforge.net/mailarchive/forum.php?thread_name=200709201942.l8KJgcd9015378%40earth.opentaps.org&forum_name=opentaps-crmcommits opentaps commit r 5102], which implemented the front end and the card processing for authorize.net

← Older revision		Revision as of 22:05, 16 July 2008
Line 1:		Line 1:
		+	''This has been fully implemented in opentaps 1.0, so this document serves as a reference only.''
		+
	The CVV/security code should be set from your screen to the ShoppingCart.CartPaymentInfo securityCode field. It will then be stored by the shopping cart in the OrderPaymentPreference entity as the "securityCode" field, and after the PaymentGatewayServices (line 1741) performs an authorization, it will clear the securityCode field so that it is not stored long term, in accordance with [http://www.chasepaymentech.com/solfraprocarnotpredatsecreq.do#prohibited prohibited data requirements]. The credit card payment processor should then pass OrderPaymentPreference.securityCode to the gateway as the security code.		The CVV/security code should be set from your screen to the ShoppingCart.CartPaymentInfo securityCode field. It will then be stored by the shopping cart in the OrderPaymentPreference entity as the "securityCode" field, and after the PaymentGatewayServices (line 1741) performs an authorization, it will clear the securityCode field so that it is not stored long term, in accordance with [http://www.chasepaymentech.com/solfraprocarnotpredatsecreq.do#prohibited prohibited data requirements]. The credit card payment processor should then pass OrderPaymentPreference.securityCode to the gateway as the security code.

	For an example, see [http://sourceforge.net/mailarchive/forum.php?thread_name=200709201942.l8KJgcd9015378%40earth.opentaps.org&forum_name=opentaps-crmcommits opentaps commit r 5102], which implemented the front end and the card processing for authorize.net		For an example, see [http://sourceforge.net/mailarchive/forum.php?thread_name=200709201942.l8KJgcd9015378%40earth.opentaps.org&forum_name=opentaps-crmcommits opentaps commit r 5102], which implemented the front end and the card processing for authorize.net

← Older revision	Revision as of 21:29, 21 September 2007
(No difference)