Difference between revisions of "Implementing CVV Security Code Checking"
(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...) |
|||
| 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 | ||
Latest revision as of 22:05, 16 July 2008
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 prohibited data requirements. The credit card payment processor should then pass OrderPaymentPreference.securityCode to the gateway as the security code.
For an example, see opentaps commit r 5102, which implemented the front end and the card processing for authorize.net
