Secpay users - are you getting a lot of card declineds?

[netmotiv8]

Hello,

 

Recently we seem to be getting a lot of card declineds on recurring payments using SecPay (Paypoint).

 

We when look in our transaction report at Secpay no transactions are recorded for the card declineds when normally you would expect to see a failed transaction as a red line item on the reports.

 

We have logged a support ticket with Secpay, in meantime has anyone any clues?

 

 

Cheers

 

Neil

[netmotiv8]

Secpay have said this:

 

"Looking in our logs, I see that several of your transactions have been rejected with error P:V or P:E.

 

P:E means that the expiry date is invalid; in the past for example.

 

P:V refers to the lack of CV2 in the transaction request. Subsequent to the recent CSC Mandate from Visa, there is now a default requirement for this parameter (the 3 digit security code from the back of the card) to be included; I recommend that you make it a required field on your payment card details capture page."

 

Does this mean now that using the SecPay module no longer allows us to capture recurring payments? I was under the impression that recurring payments were exempt from the new Visa CSC mandate.

 

I read this about the new mandate:

####

With a new VISA mandate coming into effect from 1st June 2009 that requires that the CSC* be provided with all Visa eCommerce transactions (online only), it's time to make sure your e-commerce is up to date and coplies with any legal requirements. By doing this you will enhance security to your customers and reduce the risk of being fined.

 

*CSC - Card security code, also referred to as CV2, CVV and CAVV - these are the three digits on the rear of the card (four digits if Amex)

 

 

There are a number of exemptions to the new VISA mandate, these are listed below:

 

* - Recurring and Instalment Payments (scheduled transactions)

* - Hotels/Lodging

* - Car Hire

* - Delayed or Amended T&E Charges

* - Travel and Entertainment deferred or amended charges

* - Health Care Incidental Expenses

* - Account on file CNP transactions (repeat transactions)

* - Split Sales

* - Business Travel Agents

* - Mail Order Transactions

######

[netmotiv8]

I have now had a further response from Secpay:

 

 

###

Hello Neil,

 

Repeat transactions created by calls to our repeatCardFull methods are indeed exempt from this requirement; or rather, they will assume that the CV2 check from the original transaction still holds good.

 

If you are making repeat transactions by calling our validateCardFull methods, you will need to flag them as repeats in order that we can exempt them. The necessary flags are;

 

usage_type=R,repeat=true

 

These should be added to the comma separated options string (the last parameter in calls to validateCardFull).

 

Regards,

Simon.

####

 

 

I have sent a support ticket to WHMCS requesting an update to the Secpay module in some way.

 

 

Cheers

 

Neil

[netmotiv8]

Matt made the necessary changes to the Secpay module as suggested by Secpay and recurring payments are working fine once again

 

Thanks to Matt for great support once again!

[suhailc]

Hi Neil,

 

Are you using the "FastTrack" solution from PayPoint(SecPay), or do you have your own internet merchant account?

 

I'm trying to figure out if WHMCS is compatible with PayPoint's FastTrack solution.

[netmotiv8]

Hi Suhail,

 

We have our own internet merchant account, so I am not in position to say whether the module is FastTrack compatible or not.

 

Send an email to WHMCS support and they will let you know.

 

Be interested to know the answer, so when you get one, post the reply here.

 

Cheers

Neil