ccv - credit card verification number pt2

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   If anyone is interested in our solution.  Sorry about having to create a new post but the original post was closed.

After having to pay for a solution we found out the suggested way is to purchase the new module that will allow for this ccv value to be passed to authorize.net.  WARNING:  Just because you have a textbox for Security Number in payment2.asp doesn't mean its value is getting passed to authorize.net.  If you have an older version of SalesCart PRO (we bought in October 2003) you do get the gateway to authorize it's just that CTp.asp may not include the field x_Card_Code that passes the security number to authorize.  

So if your authorize.net transaction version is 3.1 and you have a old CTp.asp file you have 2 options: 

 1.  Buy the latest and greatest version from salescart ($60). 

 2.  Modify CTp.asp yourself and pass the values (not recommended for beginners).

I also recommend reading the authorize.net document AIM_guide.pdf to see what you need  to be passing or could be passing.

If your interested to know what we did:

1.  In CTp.asp we changed x_version 3.0 to 3.1

(3.0 is the standard version, 3.1 allows the merchant to utilize the Card Code feature)

(This is actually optional.  If no value is specified, the value located in the Transaction Version settings within the Merchant Interface will be used.)

2.  In CTp.asp we added the following line in the appropriate place:

AuthNet = AuthNet & "&x_Card_Code=" & RS("CardSecurity")

Also be aware that these Card Codes (along with credit card numbers) are stored in your database based on original coding.  Will said they do have a fix for the card numbers but not sure if they have the card codes fix yet.  

Note: The information above is not supported by SalesCart.  Follow instructions at your own risk

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
lleemon Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: March/16/04 Location: United States Status: Offline Points: 41	Post Options Post Reply Quote lleemon Report Post Thanks(0) Quote Reply Topic: ccv - credit card verification number pt2 Posted: July/09/04 at 1:45pm
	If anyone is interested in our solution. Sorry about having to create a new post but the original post was closed. After having to pay for a solution we found out the suggested way is to purchase the new module that will allow for this ccv value to be passed to authorize.net. WARNING: Just because you have a textbox for Security Number in payment2.asp doesn't mean its value is getting passed to authorize.net. If you have an older version of SalesCart PRO (we bought in October 2003) you do get the gateway to authorize it's just that CTp.asp may not include the field x_Card_Code that passes the security number to authorize. So if your authorize.net transaction version is 3.1 and you have a old CTp.asp file you have 2 options: 1. Buy the latest and greatest version from salescart ($60). 2. Modify CTp.asp yourself and pass the values (not recommended for beginners). I also recommend reading the authorize.net document AIM_guide.pdf to see what you need to be passing or could be passing. If your interested to know what we did: 1. In CTp.asp we changed x_version 3.0 to 3.1 (3.0 is the standard version, 3.1 allows the merchant to utilize the Card Code feature) (This is actually optional. If no value is specified, the value located in the Transaction Version settings within the Merchant Interface will be used.) 2. In CTp.asp we added the following line in the appropriate place: AuthNet = AuthNet & "&x_Card_Code=" & RS("CardSecurity") Also be aware that these Card Codes (along with credit card numbers) are stored in your database based on original coding. Will said they do have a fix for the card numbers but not sure if they have the card codes fix yet. Note: The information above is not supported by SalesCart. Follow instructions at your own risk