HomeHome Product Discus... Product Discus...SmithCartSmithCartElavon and Elavon and 'ssl_customer_code'
Previous
 
Next
New Post
2/10/2012 7:57 AM
 

I've recently installed Smith Cart and I'm using Elavon as my merchant.  On check-out customers are receiving an error that the 'ssl_customer_code' parameter is not being provided to the merchant provider.  A little research online indicates that this parameter should get passed and probably should be set to '1111'. 

How do I get Smith Cart to pass this value to the merchant?

 
New Post
2/10/2012 7:10 PM
 
Hi Christopher,

Which version of the Cart and DNN are you currently running?

Which Elavon gateway do you have configured in your Payment Gateway Setup?

According to their Developer's Guide the "ssl_customer_code" field is not required. Are you sure it's not checked as required at the gateway? I tried to take a look at the admin but our test account is already locked unfortunately.

Thanks,

 
New Post
2/13/2012 6:45 AM
 

Kevin,

Here are the versions:

DNN Version: 06.01.02 (98)
SmithCart version: 4.87.0

I'm using Elavon Virtual Merchant as the gateway.

I see that the developer's guide lists it as not required, but I also see that other cart providers seem to have the same issue with this field being missing.  I can't tell if the field should just be the customer number from the cart system (I think that would work) or something else.

Strangely it doesn't appear that it is always a problem.  I have a few customers who always get the error (tried multiple times with multiple cards), but I have had two customers that did successfully purchase (and never saw the error at all).  I'm not certain that there's a correlation (not enough purchases yet to say it's significant), but it appears that the failures are always with non-US based customers.

I just verified your super-user account is still set up.

 
New Post
2/13/2012 3:41 PM
 
Hi Chris,

I believe it is optional, so you must be able to enable/disable the field from being required in your gateway admin section. Seems that if it is used, the transaction fees may be reduced as indicated by the following specified in the dev guide:

2. The more card holder information passed during authorization, the better.....
- AVS Data
- CVV2 / CVC / CID Value
- Invoice Number
- Card present indicator

3. Commercial cards and purchasing cards require additional data to receive lower processing fees. The basic "Level II" data that should be passed at time of authorization is as follows:
- Customer Code
- Sales Tax

Seems that if the Customer Code field is passed, the transaction fees may be reduced. Since the "ssl_customer_code" reduces fees, I'll definitely add it to our Dev. Roadmap. As far as I understand it's our Cart Customer ID used to identify returning customers, correct?

Thanks,
 
New Post
2/13/2012 4:51 PM
 

Kevin,

I'l take a look again, but didn't see any way to disable it.    I did receive another failure this afternoon, this time from an in-country buyer, so that appears to have been a red-herring.  It may be the card type is what is requiring it.

Any feeling on when the "ssl_customer_code" might get added into Smith Cart (even if I get the check turned off, lowering fees is always good)?

 
New Post
2/14/2012 2:26 PM
 

Hi Chris,

I will add sending "ssl_customer_code" when processing transactions through the Elavon Virtual Merchant gateway to our Dev Roadmap to be included in one of the next release. If you would like to prioritize this item into development, please do one of the following:

1. Submit a Quote Request here: http://www.smith-consulting.com/Servi...
2. Email sales@smith-consulting.com

We quote all feature enhancements below cost since it is enhancing the module and in most cases we can start work within a week.

Thanks,

 
Previous
 
Next
HomeHome Product Discus... Product Discus...SmithCartSmithCartElavon and Elavon and 'ssl_customer_code'